All ICR List

Package: Registration ICR List

IA # Name Type Custodial Package Date Created DBIC Approval Status Status Usage File # General Description Remote Procedure Routine Date Activated
IA # Name Type Custodial Package Date Created DBIC Approval Status Status Usage File # General Description Remote Procedure Routine Date Activated
11 DBIA11 File REGISTRATION 1990/03/20 APPROVED Active Private
Use of variable pointers to DPT & REFFERAL File. Uses
following patient nodes:
Address Node .11
Phone node .13
Field 1, Alias subfile
0 Node
13 DBIA13 File REGISTRATION 1990/03/21 APPROVED Active Private 2
PATIENT NODE .35 - DEATH INFO USED TO STUFF ^LR(
GLOBAL.
17 DBIA17-A File REGISTRATION 1990/03/12 APPROVED Active Controlled Subscription 405
PATIENT MOVEMENT FILE (405).
21 DBIA21 File REGISTRATION 1989/12/08 APPROVED Active Private 2
Fields 220 and 220.1 of the Patient Files were
established for Dental use and Dental will begin using them.
23 DBIA23 File REGISTRATION 1990/01/18 Retired Private 2
27 DBIA27 File REGISTRATION 1989/07/17 APPROVED Active Private 45
28 DBIA28 Routine REGISTRATION 1989/03/21 Retired Private
*****TEMPORARY SUPPORTED CALL FOR IFCAP V2 TEST SITES
ONLY*****
call to ZIS^DGUTL		 DGUTL
30 DBIA30-A File REGISTRATION 1989/11/14 Retired Private 2
31 DBIA31-A File REGISTRATION 1989/11/14 APPROVED Active Private 42
32 DBIA32 File REGISTRATION 1989/11/14 Expired Private 2
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
33 DBIA33 File REGISTRATION 1989/11/14 APPROVED Active Private 42
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.
36 DBIA36-A File REGISTRATION 1989/03/22 APPROVED Active Private 42
^DIC(42 Used to get link to file 44 for inpatients
37 DBIA37 File REGISTRATION 1989/03/22 Retired Private 2
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
39 DBIA39 File REGISTRATION 1990/01/23 Expired Private 2
AMIE uses the following:
INP^VADPT to get inpatient information
44 DBIA44 File REGISTRATION 1990/06/26 APPROVED Active Private 43
45 DBIA45 File REGISTRATION 1990/06/26 Retired Private 43
47 DBIA47 File REGISTRATION 1990/07/25 APPROVED Active Private 41.9
76 DBIA76 File REGISTRATION 1990/03/12 Retired Private 2
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.
87 DBIA87-A File REGISTRATION 1991/07/10 APPROVED Active Private 41.1
SCHEDULED ADMISSION FILE: Loops through ARSV x-ref and
looks at
RESERVATION DATE/TIME field. (routine YSCEN)
92 DBIA92 File REGISTRATION 1991/09/11 APPROVED Active Controlled Subscription 45
Amended October 28, 1997. fields DGPT(D0,0) .01 and
DGPT(D0,70) 80 added for CIRN 11/24/98
104 DBIA104-A File REGISTRATION 1991/10/04 Retired Private 2
#2 Patient file
.35 node
111 DBIA111-A Routine REGISTRATION 1991/05/14 APPROVED Active Private DGAINP3
113 DBIA113-A File REGISTRATION 2005/11/09 Retired Private 80.1
114 DBIA114 File REGISTRATION 1991/08/24 Retired Private 2
Checks 1st piece of the .35 node for death
121 DBIA121 File REGISTRATION 1991/09/05 APPROVED Active Private 2
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
130 DBIA130-A File REGISTRATION 1991/12/04 APPROVED Active Private 2
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
132 DBIA132-A Other REGISTRATION 1991/12/05 APPROVED Active Private
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.
133 DBIA133 Other REGISTRATION 1991/12/09 Retired Private
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.
146 DBIA146 File REGISTRATION 1992/03/11 APPROVED Active Private 2
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".
152 DBIA152 Routine REGISTRATION 1992/04/01 Retired Private
A call to WARD^DGPMUTL, to find the ward at discharge,
in the routine QIP1DIS.		 DGPMUTL
154 DBIA154 Routine REGISTRATION 1992/04/27 APPROVED Active Private
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. 		DGYEPRP
156 DBIA156 Other REGISTRATION 1992/05/21 APPROVED Active Private
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.
160 DBIA160-A File REGISTRATION 1992/06/08 APPROVED Active Private 2
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
173 DBIA173 Other REGISTRATION 1992/06/17 APPROVED Active Private
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.
174 DBIA174 File REGISTRATION 1992/06/18 APPROVED Active Controlled Subscription 2
Direct global access to patient file, Field
.3721--Rated Disabilities (VA).
175 DBIA175 Other REGISTRATION 1992/06/18 APPROVED Active Private
PDX routines will be exported with MAS 5.2.
176 DBIA176 File REGISTRATION 1992/06/18 APPROVED Active Private
PDX uses direct access to ^DG global.
186 DBIA186-A Routine REGISTRATION 1992/07/22 APPROVED Active Private
Means Test Billing Conversion.		 DGINPW
187 DBIA187-A File REGISTRATION 1992/07/22 APPROVED Active Controlled Subscription 2
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.
189 DBIA189 Routine REGISTRATION 1992/08/03 Retired Private
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.		 DGPMDDCF
218 DBIA218-A File REGISTRATION 1993/03/04 APPROVED Active Controlled Subscription 45.3
220 DBIA220 File REGISTRATION 1993/03/24 APPROVED Active Private 2
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.
226 DBIA226-A Routine REGISTRATION 1993/05/03 Retired Private DGPTFCR
244 AMIE Access to Patient File Fields File REGISTRATION 1993/06/15 APPROVED Active Private 2
ALL FIELDS ACCESSIBLE TO AMIE THROUGH THIS AGREEMENT ARE BASED ON FILEMAN
CALLS ONLY.
AMIE has permission from PIMS to make the following calls:
GLOBAL REF. NODE;PIECE USAGE
^DPT( .11;1 Street address line 1
.11;2 Street address line 2
.11;3 Street address line 3
.11;4 City
.11;5 State
.11;6 Zip Code
.11;7 County
.11;8 Province
.11;9 Postal Code
.11;10 Country
.11;12 Zip+4
.13;1 Residence PhoneNumber
.13;2 Work Phone Number
.29;1 Date Ruled Incompetent (VA)
.29;2 Date Ruled Incompetent(CIVIL)
.29;12 Rated Incompetent
.3;1 Service Connected
.31;2 Claim Folder Location
.31;3 Claim Number
.32;4 Service Discharge Type [LAST]
.32;5 Service Branch [LAST]
.32;6 Service Entry Date [LAST]
.32;7 Service Separation Date [LAST]
.36;1 Primary Eligibility Code
.36;2 Eligibility Status Date
.361;1 Eligibility Status
.362;12 Receiving A&A Benefits
.372;1 Rated Disabilities VA
.372;2 Disability Percentage
.372;3 Service Connected
"DIS"; Disposition Log-in Date
"S";1 Appointment Clinic
"S";16 Appointment Type
Directly edits the following fields in the Patient file:
.02 SEX
.03 DOB
.09 SSN
.111 Street Address 1
.1112 ZIP+4
.112 Street Address 2
.113 Street Address 3
.114 City
.115 State
.116 Zip Code
.117 County
.1171 Province
.1172 Postal Code
.1173 Country
.131 Phone Number Res.
.132 Phone Number Work
.301 Service Connected
.302 Ser. Con. Percentage
.313 Claim Number
.312 Claim Folder Location
.323 Period of Service
.324 Service Discharge Type [LAST]
.325 Service Branch [LAST]
.326 Service Entry Date [LAST]
.327 Service Separation Date [LAST]
.3611 Eligibility Status
.361 Primary Eligibility Code
.525 POW Status Indicated
.3612 Elig. Status Dat
1901 Veterab Yes/No
-Editing of the permanent address information
.111;.1112;.112;.113;.114;.115;.116; .1112;.117;.1171;.1172; .1173;.131; .132;
- Fields .1171, .1172, .1173 (Province, Postal Code, Country) will be set
using FM input template(s)
-AMIE also has LAYGO access to the Patient file per agreement with the MAS
SIUG.
Following release of patch DG*5.3*797, AMIE/CAPRI will use FileMan to edit the
following fields of File 2, Subfile .3216, Military Service Episode multiple:
.01 Service Entry Date .02 Service Separation Date .03
Service Branch .06 Service Discharge Type		 2010/12/08
260 DBIA260 File REGISTRATION 1993/08/09 APPROVED Active Private 2
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.
263 DBIA263-A Routine REGISTRATION 1993/08/10 APPROVED Active Supported VAFHLPID
268 DBIA268-A File REGISTRATION 1993/08/25 APPROVED Active Private 2
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
277 DBIA277-A File REGISTRATION 1993/09/13 APPROVED Active Private 13
File #13 - Religion
Field #.01 - Name - ^DIC(13,D0,0) piece 1
294 DBIA294 File REGISTRATION 1993/10/21 APPROVED Active Private 2
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.
311 DBIA311-A File REGISTRATION 1993/11/01 APPROVED Active Private 45.7
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".
312 DBIA312-A File REGISTRATION 1993/11/01 APPROVED Active Private 45
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.
313 DBIA313 File REGISTRATION 1993/11/01 APPROVED Active Controlled Subscription 393
Discharge Summary has permission to reference the
Incomplete Records File (#393), from the GMR REPORTS FILE (#128), IRT RECORD
field (#.13).
322 DBIA322 File REGISTRATION 1993/12/07 APPROVED Active Controlled Subscription 45.7
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
325 DBIA325-A Routine REGISTRATION 1993/12/23 APPROVED Active Controlled Subscription VADPT2
348 DBIA348 File REGISTRATION 1994/02/11 APPROVED Active Private 2
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.
350 DBIA350 File REGISTRATION 1994/02/28 APPROVED Active Private 2
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
357 DBIA357 File REGISTRATION 1994/03/03 APPROVED Active Private 2
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
358 DBIA358 File REGISTRATION 1994/03/03 APPROVED Active Controlled Subscription 405
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
359 DBIA359 File REGISTRATION 1994/03/03 APPROVED Active Private 45
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
360 DBIA360 File REGISTRATION 1994/03/03 APPROVED Active Private 405.3
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
361 DBIA361 File REGISTRATION 1994/03/03 APPROVED Active Private 37
Read access to the following fields:
FIELDS:
ELEMENT FILE
DD LEVEL FIELD # DD NUMBER
NAME DISPOSITION
1 .01 37
362 DBIA362 File REGISTRATION 1994/03/03 APPROVED Active Controlled Subscription 45.7
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
363 DBIA363 File REGISTRATION 1994/03/03 APPROVED Active Controlled Subscription 405.2
Read access to the following fields:
FIELDS:
ELEMENT FILE
DD LEVEL FIELD # DD NUMBER
NAME MAS MOVEMENT TYPE
1 .01 405.2
366 DBIA366 File REGISTRATION 1994/03/03 APPROVED Active Private 80.1
Read access to the following Fields:
FIELDS:
ELEMENT FILE
DD LEVEL FIELD # DD NUMBER
CODE NUMBER ICD OPERATION/PROCEDURE
1 .01 80.1
413 DBIA413 Routine REGISTRATION 1994/04/05 APPROVED Active Controlled Subscription DGRPU1
414 DBIA414 Other REGISTRATION 1994/04/05 APPROVED Active Private
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",).
415 DBIA415 Other REGISTRATION 1994/04/05 APPROVED Active Private
The INSURANCE COMPANY (#36) file will now be released exclusively
by Integrated Billing unless otherwise agreed upon.
416 DBIA416 File REGISTRATION 1994/04/05 APPROVED Active Private 37
417 DBIA417 File REGISTRATION 1994/04/05 APPROVED Active Controlled Subscription 40.8
418 DBIA418 File REGISTRATION 1994/04/05 APPROVED Active Controlled Subscription 45
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.
419 DBIA419 File REGISTRATION 1994/04/05 Under Revision Controlled Subscription 405
420 DBIA420 Routine REGISTRATION 1994/04/05 APPROVED Active Private DGMTU
421 DBIA421 Routine REGISTRATION 1994/04/05 APPROVED Active Private DGUTL2
422 DBIA422 Routine REGISTRATION 1994/04/05 APPROVED Active Private DGPTUTL
423 DGMTCOU1 - Medication Copay Exemption API Routine REGISTRATION 1994/04/05 APPROVED Active Private DGMTCOU1 2011/03/04
424 DBIA424 Routine REGISTRATION 1994/04/05 APPROVED Active Private DGMTU11
425 DBIA425 Routine REGISTRATION 1994/04/05 APPROVED Active Private DGMTU1
426 DBIA426 File REGISTRATION 1994/04/05 APPROVED Active Private 2
427 DBIA427 File REGISTRATION 1994/04/05 APPROVED Active Controlled Subscription 8
428 DBIA428 File REGISTRATION 1994/04/05 APPROVED Active Controlled Subscription 11
429 DBIA429 File REGISTRATION 1994/04/05 APPROVED Active Private 41.1
430 DBIA430 File REGISTRATION 1994/04/05 APPROVED Active Private 42.4
431 DBIA431 File REGISTRATION 1994/04/05 APPROVED Active Private 43 2013/04/09
433 DBIA433 File REGISTRATION 1994/04/05 APPROVED Active Controlled Subscription 405.3
434 DBIA434 File REGISTRATION 1994/04/05 APPROVED Active Controlled Subscription 408.31
476 DBIA476 File REGISTRATION 1994/05/10 Withdrawn Private 2
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.
480 DBIA480 File REGISTRATION 1994/05/02 APPROVED Active Private 8
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.
482 DBIA482 File REGISTRATION 1994/05/02 APPROVED Active Private 405
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
483 DBIA483 File REGISTRATION 1994/05/02 APPROVED Active Controlled Subscription 43
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
484 DBIA484 File REGISTRATION 1994/05/02 APPROVED Active Private 40.8
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
485 DBIA485 File REGISTRATION 1994/05/02 APPROVED Active Private 2
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:
494 DBIA494 File REGISTRATION 1994/06/13 Retired Private 13
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).
512 DBIA17-B Routine REGISTRATION 1990/03/12 APPROVED Active Controlled Subscription DGPMLOS
513 DBIA30-B File REGISTRATION 1994/03/01 APPROVED Active Private 45.7
514 DBIA31-B File REGISTRATION 1989/11/14 APPROVED Active Private 42.5
519 FACILITY TREATING SPECIALTY (#45.7) File Access File REGISTRATION 1989/03/22 APPROVED Active Private 45.7
^DIC(45.7 Used to lookup treating specialty and print name		 2015/07/17
547 DBIA87-B File REGISTRATION 1991/07/10 APPROVED Active Private 45
PTF FILE: Looks at 70 node (Discharge and ICD
diagnosis info) and
M multiple (movement data) and its ICD 1 field. (routine YSCEN32)
548 DBIA87-C File REGISTRATION 1991/07/10 APPROVED Active Controlled Subscription 8
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.
549 DBIA87-D File REGISTRATION 1991/07/10 APPROVED Active Private 37
DISPOSITION FILE: (routine: YSPP4)
550 DBIA87-E File REGISTRATION 1991/07/10 APPROVED Active Private 2
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)
564 DBIA104-B File REGISTRATION 2005/06/20 Retired Controlled Subscription 45
#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.
565 DBIA104-C File REGISTRATION 2005/06/22 APPROVED Active Controlled Subscription 405
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"
581 DBIA111-B Routine REGISTRATION 1991/05/14 APPROVED Active Private DGANHD3
602 DBIA130-B File REGISTRATION 1991/12/04 APPROVED Active Controlled Subscription 8
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
604 DBIA130-D File REGISTRATION 1991/12/04 APPROVED Active Private 35
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
606 DBIA132-B File REGISTRATION 1991/12/05 APPROVED Active Private 2
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.
613 DBIA142-C File REGISTRATION 1992/01/23 APPROVED Active Private 2
625 DBIA160-B File REGISTRATION 1992/06/08 APPROVED Active Private 45
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.
642 DBIA186-B Routine REGISTRATION 1992/07/22 APPROVED Active Controlled Subscription DGMTU
643 DBIA186-C Routine REGISTRATION 1992/07/22 APPROVED Active Controlled Subscription
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".		 DGMTUB 2019/02/15
644 DBIA186-D Routine REGISTRATION 1992/07/22 APPROVED Active Private VADPT
646 DBIA186-F File REGISTRATION 1992/07/22 APPROVED Active Private 40.8
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
649 DBIA186-I File REGISTRATION 1992/07/22 APPROVED Active Controlled Subscription 391
650 DBIA186-J File REGISTRATION 2003/06/10 Retired Private 5
651 DBIA186-K File REGISTRATION 1992/07/22 APPROVED Active Private 41.3
Date of Test multiple Conversion of Month/Year multiple
MT billing data.
652 DBIA186-L File REGISTRATION 1992/07/22 APPROVED Active Private 42
0th node-- Determine ward type, division of ward.
653 DBIA186-M File REGISTRATION 1992/07/22 APPROVED Active Private 45.7
0th node-- Determine billable SPECIALTY, #42.4 0th
node-- bedsection
654 DBIA186-N File REGISTRATION 1992/07/22 APPROVED Active Private 45
101 node-- Determine if admitted VA ADM. REG., #43.4
"D" cross-reference for Observation & SOURCE OF ADM.,#45.1 "B"
cross-reference Examination
655 DBIA186-O File REGISTRATION 1992/07/22 APPROVED Active Private 405
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
656 DBIA186-P File REGISTRATION 1992/07/22 APPROVED Active Private 405.1
FAC. MVMT TYPE, #405.1 0th node-- List movement type
657 DBIA186-Q File REGISTRATION 1992/07/22 APPROVED Active Private 40
IB DIVISION DISPLAY on file 40.-- Displays a division's
billing
fields: .01 NAME-- history
664 VA UTILITY ONE/MANY/ALL Routine REGISTRATION 1992/07/22 APPROVED Active Controlled Subscription VAUTOMA 2009/06/03
688 DBIA218-B Routine REGISTRATION 1993/03/04 APPROVED Active Private
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. 		VACPT
689 DBIA218-C File REGISTRATION 1993/03/04 APPROVED Active Private 2
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.
690 DBIA218-D File REGISTRATION 1993/03/04 APPROVED Active Private 45
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.
691 DBIA218-E File REGISTRATION 1993/03/04 APPROVED Active Private 41.1
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.
699 DBIA226-B Routine REGISTRATION 1993/05/03 APPROVED Active Private DGREG
700 DBIA226-C Routine REGISTRATION 1993/05/03 APPROVED Active Controlled Subscription DGRPDB
701 DBIA226-D Routine REGISTRATION 1993/05/03 APPROVED Active Controlled Subscription DGMTU
702 DBIA226-E File REGISTRATION 1993/05/03 APPROVED Active Private 21
Point to the following file
PERIOD OF SERVICE - 21
703 DBIA226-F File REGISTRATION 1993/05/03 APPROVED Retired Private 2
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.
719 DBIA243-C File REGISTRATION 1993/06/15 Retired Private 45
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]
720 DBIA243-D File REGISTRATION 1993/06/15 Retired Private 405.2
MAS Movement Type file (#405.2)
^DG(405.2,D0,0) - $D check on zero node
721 DBIA243-E File REGISTRATION 1993/06/15 Retired Private 42.4
Specialty file (#42.4)
^DIC(42.4,D0,0) - $D check on zero node
722 DBIA243-F File REGISTRATION 1993/06/15 Retired Private 405.4
Room-Bed file (#405.4)
^DG(405.4,D0,0)= (#.01) NAME [1F]
723 DBIA243-G File REGISTRATION 1993/06/15 APPROVED Active Controlled Subscription 42
^DIC(42,D0,0)= (#.03) SERVICE [3S] Direct Global
Read
724 DBIA243-H File REGISTRATION 1993/06/15 Retired Private 45.1
Source of Admission file (#45.1)
^DIC(45.1,D0,0)= (#.01) PTF CODE [1F]
725 DBIA243-I File REGISTRATION 1993/06/15 Retired Private 45.7
^DIC(45.7,D0,0)= (#1) SPECIALTY [2P]
726 DBIA243-J File REGISTRATION 1993/06/15 Retired Private 45.6
Place of Disposition file (#45.6)
^DIC(45.6,D0,0)= (#2) CODE [2F]
727 DBIA243-K File REGISTRATION 1993/06/15 Retired Private 80
ICD Diagnosis file (#80)
^ICD9(D0,0)= (#.01) CODE NUMBER [1F]
728 DBIA244-B File REGISTRATION 1993/06/15 APPROVED Active Controlled Subscription 40.8
729 DBIA244-C File REGISTRATION 1993/06/15 APPROVED Active Controlled Subscription 405.2
^DG(405.2, 0;1 MAS Movement Type
730 DBIA244-D File REGISTRATION 1993/06/15 APPROVED Active Private 405
^DGPM( 0;1 Date/Time of Movement
0;2 Transaction
0;17 Discharge/Check out Movement
0;18 MAS Movement Type
^DGPM("AMV1"
^DGPM("APTT1"
^DGPM("APID"
^DGPM("AMV3"
731 DBIA244-E File REGISTRATION 1993/06/15 APPROVED Active Controlled Subscription 8
^DIC(8, 0;6 Print Name of elig. code
^DIC(8,"D"
732 DBIA244-F File REGISTRATION 1993/06/15 APPROVED Active Private 21
^DIC(21, 0;1 Period Service name
^DIC(21,"D"
734 DBIA244-H File REGISTRATION 1993/06/15 APPROVED Active Private 42
^DIC(42, 0;2 Bedsection
740 DBIA244-N Routine REGISTRATION 1993/06/15 APPROVED Active Private DGRPD
741 DBIA244-O Routine REGISTRATION 1993/06/15 APPROVED Active Private
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.		 DGRPE
750 DBIA263-B Routine REGISTRATION 1993/08/10 APPROVED Active Private VAFHLZCT
751 DBIA263-C Routine REGISTRATION 1993/08/10 APPROVED Active Private VAFHLZDP
752 DBIA263-D Routine REGISTRATION 1993/08/10 APPROVED Active Controlled Subscription
Supported calls for building of HL7 ZPD segment (VA
Specific Patient Demographics).		 VAFHLZEL 2010/06/20
753 DBIA263-E Routine REGISTRATION 1993/08/10 APPROVED Active Private VAFHLZEM
754 DBIA263-F Routine REGISTRATION 1993/08/10 APPROVED Active Private VAFHLZGD
755 DBIA263-G Routine REGISTRATION 1993/08/10 APPROVED Active Private VAFHLZIC
756 DBIA263-H Routine REGISTRATION 1993/08/10 APPROVED Active Private VAFHLZMT
757 DBIA263-I Routine REGISTRATION 1993/08/10 Retired Private
duplicate of IA 751		 VAFHLZDP
758 DBIA263-J Routine REGISTRATION 1993/08/10 APPROVED Active Controlled Subscription
This generic extrinsic function returns the HL7
VA-Specific Temporary Address (ZTA) segment.		 VAFHLZTA
759 DBIA263-K Routine REGISTRATION 1993/08/10 Retired Private VASITE
760 DBIA263-L Routine REGISTRATION 1993/08/10 APPROVED Active Private
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		 DGMTSCU1
761 DBIA263-M Routine REGISTRATION 1993/08/10 APPROVED Active Private
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		 DGMTU
762 DBIA263-N Routine REGISTRATION 1993/08/10 APPROVED Other Controlled Subscription
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		 DGMTU21
763 DBIA263-O File REGISTRATION 1993/08/10 APPROVED Active Private 408.31
^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
764 DBIA263-P Other REGISTRATION 1993/08/10 APPROVED Active Private
IVM attaches a protocol to the event driver.
765 DBIA263-Q Other REGISTRATION 1993/08/10 APPROVED Active Private
IVM exports VAFHL* routines
767 DBIA268-C File REGISTRATION 1993/08/25 APPROVED Active Controlled Subscription 38.1
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)
768 DBIA268-D Routine REGISTRATION 1993/08/25 APPROVED Active Private
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		 SEE DESCRIPTION
769 DBIA268-E Routine REGISTRATION 1993/08/25 Retired Private
The PDX development team request permission to use the
$$SITE^VASITE entry point in determining site.		 VASITE
788 DBIA277-B File REGISTRATION 1993/09/13 APPROVED Active Private 22
File #22 - POW Period
Field #.01 - Name - ^DIC(22,D0,0) piece 1
789 DBIA277-C File REGISTRATION 1993/09/13 APPROVED Active Private 23
File #23 - Branch of Service
Field #.01 - Name - ^DIC(23,D0,0) piece 1
790 DBIA277-D File REGISTRATION 1993/09/13 APPROVED Active Private 24
File #24 - Non-Veterans Class
Field #.01 - Name - ^DIC(24,D0,0) piece 1
791 DBIA277-E File REGISTRATION 1993/09/13 APPROVED Active Private 25
File #25 - Type of Discharge
Field #.01 - Name - ^DIC(25,D0,0) piece 1
793 DBIA277-G File REGISTRATION 1993/09/13 APPROVED Active Private 35
File #35 - Other Federal Agency
Field #.01 - Name - ^DIC(35,D0,0) piece 1
795 DBIA277-I File REGISTRATION 1993/09/13 APPROVED Active Private 42.4
File #42.4 - Specialty
Field #.01 - Name - ^DIC(42.4,D0,0) piece 1
796 DBIA277-J File REGISTRATION 1993/09/13 APPROVED Active Private 45.7
File #45.7 - Treating Specialty
Field #.01 - Name - ^DIC(45.7,D0,0) piece 1
828 DBIA311-B File REGISTRATION 1993/11/01 APPROVED Active Private 42
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.
829 DBIA311-C File REGISTRATION 1993/11/01 APPROVED Active Controlled Subscription 40.8
836 DBIA325-B File REGISTRATION 1993/12/23 APPROVED Active Private 405
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.
909 DBIA909-A File REGISTRATION 1994/07/14 APPROVED Active Private 45.7
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
913 DBIA913 File REGISTRATION 1994/07/22 APPROVED Active Controlled Subscription 21
918 DBIA918 File REGISTRATION 1994/07/26 APPROVED Active Private 2
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.
924 DBIA924 File REGISTRATION 1994/07/28 APPROVED Active Private 11
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.		 2010/09/01
925 DBIA925 File REGISTRATION 1994/07/28 APPROVED Active Private 10
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.		 2010/09/02
935 DBIA935 File REGISTRATION 1994/08/09 APPROVED Active Private 22
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, .
955 DBIA955 Other REGISTRATION 1994/08/21 APPROVED Active Private
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.
956 DBIA956 Routine REGISTRATION 1994/08/22 APPROVED Under Revision Private
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.		 VAFHLZIR
957 DBIA957 Routine REGISTRATION 1994/08/22 APPROVED Active Private
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.		 DGMTA
958 DBIA958 Routine REGISTRATION 1994/08/22 APPROVED Active Private
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.		 DGMTEVT
959 DBIA959 Routine REGISTRATION 1994/08/22 APPROVED Active Private
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.		 DGMTSCU
960 DBIA960 Routine REGISTRATION 1994/08/22 APPROVED Active Private
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.		 DGMTSCU2
961 DBIA961 Routine REGISTRATION 1994/08/22 APPROVED Active Private
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.		 DGMTU1
962 DBIA962 Routine REGISTRATION 1994/08/22 APPROVED Other Private
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.		 DGMTU11
963 DBIA963 Routine REGISTRATION 1994/08/22 APPROVED Active Private
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.		 DGMTU2
965 DBIA965 Routine REGISTRATION 1994/08/22 APPROVED Active Private
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.		 DGMTU3
966 DBIA966 File REGISTRATION 1994/08/22 APPROVED Active Controlled Subscription 405
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.
967 DBIA967 File REGISTRATION 1994/08/22 APPROVED Active Private 2
The IVM package requests permission to directly access
and file various fields in the PATIENT (#2) file.
968 DBIA968 File REGISTRATION 1994/08/22 APPROVED Active Private 408.31
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).
969 DBIA969 File REGISTRATION 1994/08/22 APPROVED Other Private 408.12
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).
970 DBIA970 File REGISTRATION 1994/08/22 APPROVED Other Private 408.13
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).
971 DBIA971 File REGISTRATION 1994/08/22 Pending Private 408.21
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).
972 DBIA972 File REGISTRATION 1994/08/22 APPROVED Other Private 408.22
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).
974 DBIA974 Routine REGISTRATION 1994/08/23 APPROVED Active Controlled Subscription
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.		 DGMTU
993 DBIA993-A File REGISTRATION 1994/09/30 Retired Private 45
994 DBIA993-B File REGISTRATION 1994/09/30 APPROVED Active Controlled Subscription 45.84
Used to check and make sure the PTF record has not been closed out.
997 DBIA997 File REGISTRATION 1994/08/31 APPROVED Active Controlled Subscription 42.4
998 DBIA998 File REGISTRATION 1994/08/31 APPROVED Active Controlled Subscription 2
1003 Scheduled Admission DBIA File REGISTRATION 1994/09/13 APPROVED Active Private 41.1
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
1008 DBIA104-D File REGISTRATION 2005/06/20 Retired Private 43
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.
1010 DBIA1010 File REGISTRATION 1994/09/30 Retired Private 45.83
This is associated with 993 and 994
1011 DBIA1011 Routine REGISTRATION 1994/09/30 Pending Private
Fee will look into changing to the mailman mailgroup
functionality in a future version.		 VATRAN
1031 DBIA1031 Routine REGISTRATION 1994/10/20 APPROVED Active Private
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		 DGSEC
1032 DBIA1032 Routine REGISTRATION 1994/10/21 APPROVED Active Private
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.		 DPTLK
1037 DBIA1037 File REGISTRATION 1994/10/24 APPROVED Active Private 2
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.
1050 DBIA909-B File REGISTRATION 1994/07/14 APPROVED Active Private 42.4
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.		 2010/09/09
1051 DBIA909-C File REGISTRATION 1994/07/14 APPROVED Active Private 42
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.
1069 DS needs WARD AT DISCHARGE File REGISTRATION 1994/12/05 APPROVED Active Private 405
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.
1070 DBIA1070 Routine REGISTRATION 1995/03/30 APPROVED Active Private
The IVM package files new Means Tests into the PIMS
Means Test module. This routine contains utilities for Means Test processing. 		DGMTSCU3
1071 DGPMSTAT Routine REGISTRATION 1994/12/09 Pending Supported
Obtain Inpatient Status.		 DGPMSTAT
1073 VADATE Routine REGISTRATION 1994/12/09 Pending Supported
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.		 VADATE
1075 VATREDIT Routine REGISTRATION 1994/12/09 Pending Supported
Enter/Edit Transmission Routers File.		 VATREDIT
1076 VAUQWK Routine REGISTRATION 1994/12/09 APPROVED Active Private
Quick Lookup for Patient Data.		 VAUQWK 1994/12/10
1096 PATIENT MOVEMENT file cross reference File REGISTRATION 1995/01/03 APPROVED Active Controlled Subscription 405
Patient Movement file (#405)
- The "ATID1" xref.of the Patient Movement file. This is to order through
admissions in inverse date order.
1097 Lookup on Facility Movement file File REGISTRATION 1995/01/03 APPROVED Active Private 405.1
- 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.
1098 GENERAL LOOKUP File REGISTRATION 1995/01/03 APPROVED Active Private 405.2
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.
1099 LOOKUP on MAS MOVEMENT TRANSACTION TYPE file File REGISTRATION 1995/01/03 APPROVED Active Private 405.3
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.
1100 DISPOSITION NODE File REGISTRATION 1995/01/03 APPROVED Active Private 2
Global read access to the "DIS" node of the PATIENT
file, to look at the STATUS field.
1112 PATIENT TYPE File REGISTRATION 1995/01/26 APPROVED Active Controlled Subscription 391
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.
1118 ICD Codes update in PTF File REGISTRATION 1995/01/11 APPROVED Active Private 45.89
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.
1154 DIC(45.7, File REGISTRATION 1995/03/02 APPROVED Active Supported 45.7
The integration agreement allows reading (with FileMan
only) the SPECIALTY field (#1) of the FACILITY TREATING SPECIALTY file
(#45.7).
1159 DBIA1159 Routine REGISTRATION 1995/03/30 APPROVED Active Private
The IVM package files new Means Tests into PIMS Means
Test module. This routine contains utilities for audit changes to Means
Tests.		 DGMTAUD
1162 DBIA1161-B File REGISTRATION 1995/03/14 APPROVED Active Controlled Subscription 43.4
Convert speciality code to its text equivalent
1164 DBIA1161-D File REGISTRATION 1995/03/14 APPROVED Active Private 42.4
Convert speciality code to text equivalent
1181 DGPM MOVEMENT EVENT Other REGISTRATION 1995/03/23 APPROVED Active Controlled Subscription
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
1187 DBIA1187 File REGISTRATION 1995/03/30 APPROVED Active Private 408.34
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.
1188 DBIA1188 File REGISTRATION 1995/03/30 APPROVED Active Private 408.41
The IVM package files new Means Tests in the PIMS Means
Test module. IVM requests permission to read from the Means Test CHANGES
file.
1210 PRINT 1010F WITH ENCOUNTER FORMS Routine REGISTRATION 1997/04/10 APPROVED Active Private
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.		 DGMTP
1227 TREATING SPECIALTY INACTIVATION Routine REGISTRATION 1995/09/28 Withdrawn Supported
This is a supported reference to screen on active
Facility Treating Specialties or Specialties.		 DGACT
1246 DGPMDDCF CALLS Routine REGISTRATION 1995/07/20 APPROVED Active Supported
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.		 DGPMDDCF
1249 DIC(10, File REGISTRATION 1995/05/30 APPROVED Active Private 10
The integration agreement allows reading (with FileMan
only) the ABBREVIATION field (#2) of the RACE file (#10).
1255 DBIA1255 Routine REGISTRATION 1995/08/08 APPROVED Active Private
The IVM package files new Means Tests into the PIMS
Means Test module. This routine contains utilities for Means Test processing. 		DGMTSCU2
1257 DBIA1257 Routine REGISTRATION 1995/08/08 APPROVED Active Private
This routine contains utilities for Means Tests/Copay
processing.		 DGMTCOU1 2013/02/15
1265 OE/RR conversion needs sched admissions File REGISTRATION 1997/10/20 APPROVED Active Private 41.1
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.
1297 OE/RR conversion needs wait list file File REGISTRATION 1997/10/20 APPROVED Active Private 42.5
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.
1302 OE/RR conversion needs discharges File REGISTRATION 1997/10/20 APPROVED Active Private 405
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.
1337 DBIA1337 File REGISTRATION 1995/09/12 APPROVED Active Controlled Subscription 42.4
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.
1358 DBIA1358 File REGISTRATION 1995/09/21 APPROVED Active Private 405
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.
1359 DBIA1359 File REGISTRATION 1995/09/21 APPROVED Active Controlled Subscription 45.7
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.
1360 DBIA1360 File REGISTRATION 1995/09/21 APPROVED Active Private 42.4
The IBQ package requests permission to directly access
the SPECILTY File (#42.4) to retrieve the SERVICE field (#.03).
1372 PTF file access File REGISTRATION 1995/10/06 Under Revision Controlled Subscription 45
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		 2015/09/18
1375 DGACT Routine REGISTRATION 1995/11/07 Withdrawn Supported
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.		 DGACT
1377 WARD LOCATION File REGISTRATION 1995/11/07 APPROVED Active Controlled Subscription 42
Controlled access to the Ward Location (42) file
fields/cross-references as described in this DBIA.		 2009/07/10
1378 DGPM File REGISTRATION 1995/11/07 APPROVED Active Controlled Subscription 405
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
1380 ROOM-BED File REGISTRATION 1995/11/07 APPROVED Active Controlled Subscription 405.4
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.
1385 BRANCH OF SERVICE File REGISTRATION 1995/11/07 APPROVED Active Controlled Subscription 23
Nursing has permission to access the Branch of Service
(23) file as described in this DBIA.
1413 MARITAL STATUS File REGISTRATION 1995/11/08 APPROVED Active Controlled Subscription 11
Nursing has permission to access the Marital Status
(11) file as described in this DBIA.
1414 RELIGION File REGISTRATION 1995/11/08 APPROVED Active Private 13
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.		 2010/09/01
1476 DBIA1476 File REGISTRATION 1996/02/09 APPROVED Active Controlled Subscription 2
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.
1480 Global Read of zero node and AMV1 nodes in File 405 File REGISTRATION 1996/02/09 Other Controlled Subscription 405
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.
1481 Check Out-Of-Service nodes on File 42 File REGISTRATION 1996/02/09 APPROVED Active Private 42
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.
1494 SENSITIVE PATIENT BULLETIN NAME File REGISTRATION 1996/02/21 APPROVED Active Controlled Subscription 43
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.
1574 DBIA1574 File REGISTRATION 1996/08/07 APPROVED Active Controlled Subscription 43
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.
1576 DIVISION FILE LOOKUP File REGISTRATION 1996/08/08 Withdrawn Controlled Subscription 40.8
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.
1594 APPOINTMENT MULTIPLE File REGISTRATION 1996/08/12 APPROVED Active Controlled Subscription 2
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.
1624 Cross Reference on Date of Death Field File REGISTRATION 1996/10/24 APPROVED Active Private 2
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.
1847 DBIA1847 File REGISTRATION 1996/11/21 APPROVED Active Private 21
DSS Extracts will reference the following data from the
PERIOD OF SERVICE file (#21).
1848 DBIA1848 File REGISTRATION 1996/11/26 APPROVED Active Controlled Subscription 42
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)
1849 DBIA1849 File REGISTRATION 1996/11/26 Under Revision Private 40.8
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.
1850 DBIA1850 File REGISTRATION 1996/11/26 APPROVED Active Controlled Subscription 2
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.
1856 DBIA1856 File REGISTRATION 1996/12/03 APPROVED Active Private 45
DSS Extracts references the following data from the PTF
file (#45).
From the 501 multiple (45.02):
1857 DBIA1857 File REGISTRATION 1996/12/04 APPROVED Active Private 45.9
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)
1861 DBIA1861 File REGISTRATION 1996/12/04 APPROVED Active Controlled Subscription 10
DSS Extracts references the following data from the
RACE file (#10).
1865 DBIA1865 File REGISTRATION 1996/12/05 APPROVED Active Controlled Subscription 405
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 		2018/10/26
1866 DBIA1866 File REGISTRATION 1996/12/05 Retired Private 408.32
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).
1888 DBIA1888 File REGISTRATION 1997/01/23 APPROVED Active Private 45
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
1942 REGISTRATION FILE USED BY CPRS/OERR - DG(40.8 File REGISTRATION 1997/02/27 Pending Private 40.8
CPRS/OERR extracts data from the MEDICAL CENTER
DIVISION FILE [#40.8].
2010 DBIA2010 File REGISTRATION 1997/04/15 APPROVED Active Private 38.5
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.
2011 DBIA2011 File REGISTRATION 1997/04/15 APPROVED Active Private 38.6
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.
2041 DB2041 Routine REGISTRATION 1997/06/25 APPROVED Active Controlled Subscription
Used to display the Patient Profile report via a
"silent call".		 DGRPD
2042 DG Patient Sensitivity Routine REGISTRATION 1997/06/26 Withdrawn Private
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.		 MAGGTPTS
2049 LABORATORY DPT REFERRAL POINTER File REGISTRATION 1997/06/30 APPROVED Active Private 2
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.
2069 DBIA2069 File REGISTRATION 1997/07/24 Retired Private 2
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
2070 DBIA2070 File REGISTRATION 1997/08/04 APPROVED Active Controlled Subscription 2
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.
2076 DBIA2076-A Routine REGISTRATION 1997/08/20 APPROVED Active Private
To support patient data review, CIRN needs to include a
Hinq inquiry.		 DG10
2085 DBIA2085 File REGISTRATION 1997/08/26 APPROVED Active Private 43
This is needed because PCE now ask the classification questions for
Scheduling.
2086 DBIA2086 File REGISTRATION 1997/08/26 APPROVED Active Private 2
This is so PCE can find the Outpatient Encounter and thus the Visit for a
disposition.
2090 ACCESS TO PATIENT MOVEMENT DATA File REGISTRATION 1997/08/27 APPROVED Active Controlled Subscription 405
THIS ICR ALLOWS ACCESS TO PATIENT MOVEMENT DATA.		 2012/10/12
2233 DBIA2233 File REGISTRATION 1997/11/06 APPROVED Active Controlled Subscription 43
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).
2234 DBIA2234 File REGISTRATION 1997/11/06 Retired Private 408.32
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).
2242 DBIA2242 Routine REGISTRATION 1997/11/20 APPROVED Active Controlled Subscription
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.		 DGSEC
2248 DBIA 2248 Routine REGISTRATION 1997/12/12 APPROVED Active Controlled Subscription
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.		 DGACT 2010/05/20
2249 DBIA-2249 File REGISTRATION 1997/12/09 APPROVED Active Private 405
Outpatient Pharmacy package request permission to read
the 'AMV1' and 'APTT1' cross references of REGISTRATION file 405.
2269 DBIA2269 File REGISTRATION 1998/01/23 APPROVED Active Controlled Subscription 40.8
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.
2295 DBIA2295 File REGISTRATION 1998/02/07 APPROVED Active Private 40.8
2296 DBIA2296 File REGISTRATION 1998/02/07 APPROVED Active Controlled Subscription 43
2297 DBIA2297 File REGISTRATION 1998/02/07 Pending Private 405
2299 DBIA2299 File REGISTRATION 1998/02/07 Pending Private 42.4
2300 DBIA2300 File REGISTRATION 1998/02/07 APPROVED Active Private 2
2341 DBIA2341 Other REGISTRATION 1998/03/05 APPROVED Active Private 2
The Patient Merge application of the Kernel Toolkit
requests a private integration agreement to set the variable VAFCA08 during a
merge process.
2346 DBIA2346 File REGISTRATION 1998/03/24 APPROVED Active Private 2
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.
2360 DBIA2360 File REGISTRATION 1998/04/08 APPROVED Active Private 405
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.
2437 DBIA2437 File REGISTRATION 1998/06/21 APPROVED Active Controlled Subscription 405
References to ADT/Registration globals and routines.
2438 DBIA2438 File REGISTRATION 1998/06/22 APPROVED Active Controlled Subscription 40.8
Pharmacy Benefits Management (PBM) software needs to
extract the facility number from the Medical Center Division file #40.8.
2440 DBIA2440 File REGISTRATION 1998/06/22 APPROVED Active Controlled Subscription 42
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.
2460 DBIA2460 File REGISTRATION 1998/07/01 APPROVED Active Private 2
PATIENT file access.
2461 DBIA2461 File REGISTRATION 1998/07/01 APPROVED Active Private 408.32
MEANS TEST STATUS file access.
2462 DBIA2462 File REGISTRATION 1998/07/01 APPROVED Active Controlled Subscription 27.11
PATIENT ENROLLMENT file access.
2463 DBIA2463 Routine REGISTRATION 1998/07/01 APPROVED Active Private
Means Test utility routine.		 DGMTU
2464 DBIA2464 Routine REGISTRATION 1998/07/01 APPROVED Active Private
Inpatient ward location utility.		 DGPMSTAT
2465 DBIA2465 Routine REGISTRATION 1998/07/01 APPROVED Active Private
Provides ward location for a given inpatient movement.		 DGPMUTL
2483 FILE 2 IA for WVH File REGISTRATION 1998/07/15 APPROVED Active Private 2
The Women Veterans Health package would like to view
the following fields in the Patient File (#2):
2492 DBIA2492 File REGISTRATION 1998/08/17 APPROVED Active Private 45
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.
2504 DBIA2504 File REGISTRATION 1998/08/19 APPROVED Active Private 21
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
2516 DBIA2516 File REGISTRATION 1998/08/24 APPROVED Active Controlled Subscription 8.1
^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.
2517 FILE405 ADFN X-REF File REGISTRATION 1998/08/24 APPROVED Active Private 405
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.
2562 DBIA2562 File REGISTRATION 1998/09/22 Pending Private 2
Direct of PATIENT file(#2) Direct global read of "LR"
node. The code uses LABORATORY REFERENCE(#63)
2624 DBIA2624 Routine REGISTRATION 1998/10/23 APPROVED Active Private
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).		 VAFHUTL
2643 DBIA2643 File REGISTRATION 1998/11/03 APPROVED Active Private 2
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.		 IBCNSU1 2018/06/07
2652 DBIA2652 File REGISTRATION 1998/11/25 APPROVED Active Controlled Subscription 42.4
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).
2655 DBIA2655 File REGISTRATION 1998/12/02 APPROVED Active Private 2
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
2660 SCHEDULING CONVERSION FIELDS File REGISTRATION 1998/12/10 APPROVED Active Private 2
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.
2663 DBIA2663 Other REGISTRATION 1998/12/17 APPROVED Active Private
AMIE II is an "umbrella" menu for VA Regional Office
users on VistA systems. The IA is for the options included on the menu.
2664 OBSERVATION API Routine REGISTRATION 1998/12/24 APPROVED Active Supported
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.		 DGPMOBS
2716 DG MST STATUS API'S Routine REGISTRATION 1999/01/19 APPROVED Active Supported
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. 		DGMSTAPI
2751 DGCN(391.91 Treating Facility file File REGISTRATION 1999/03/15 APPROVED Active Private 391.91
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.
2753 ADD entries to PATIENT DATA EXCEPTION (#391.98) File Routine REGISTRATION 1999/03/16 Withdrawn Private VAFCEHU1
2755 $$GETSRVR VAFCMSG5 Routine REGISTRATION 1999/02/17 APPROVED Active Private
MPIF is requesting to use $$GETSRVR^VAFCMSG5 to get the
pointer to the HL7 server protocol for the A28 event type.		 VAFCMSG5
2756 $$BLDMSG VAFCMSG1 Routine REGISTRATION 1999/02/17 APPROVED Active Private
MPIF is requesting to use $$BLDMSG^VAFCMSG1 to build
the HL7 ADT-A28 message for a given patient.		 VAFCMSG1
2758 DBIA2758 Other REGISTRATION 1999/02/22 APPROVED Active Private
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]
2779 DBIA2779 Routine REGISTRATION 1999/03/22 APPROVED Active Private
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.		 VAFCUTL1
2784 Patient File Edit Routine REGISTRATION 1999/03/23 APPROVED Active Controlled Subscription
This private routine agreement allows packages to
update certain PATIENT (#2) file fields identified by each subscribing
package.		 VAFCPTED 2007/07/16
2785 SCD Alert Other REGISTRATION 1999/03/23 Withdrawn Private
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.
2787 DBIA2787 File REGISTRATION 1999/03/24 APPROVED Active Private 2
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.
2798 $$ADD VAFCPTAD(ARRAY) Routine REGISTRATION 1999/04/06 Retired Private
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.		 VAFCPTAD
2800 DBIA2800 File REGISTRATION 1999/04/14 Pending Private 40.8
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')
2803 DBIA2803 File REGISTRATION 1999/04/16 Pending Private 405
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.
2817 OE/RR looks at 'AD' x-ref in DG(40.8 File REGISTRATION 1999/05/17 APPROVED Active Controlled Subscription 40.8
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.
2819 ACCESS TO PTF RELEASE (#45.83) FILE File REGISTRATION 1999/05/18 APPROVED Active Private 45.83
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.		 2018/04/09
2820 DBIA2820 File REGISTRATION 1999/05/18 APPROVED Active Private 45.84
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.
2911 TREATING FACILITY LIST (#391.91): relationship with CIRN PD File REGISTRATION 2000/01/13 APPROVED Active Private 391.91
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.
2918 Patients Priority Routine REGISTRATION 1999/09/23 Withdrawn Supported
To look up a patients priority for report currently
using the call: $$PRIORITY^DGENA(DFN)		 DGENA
2919 Patients enrolled/preferred facility Routine REGISTRATION 2006/08/25 APPROVED Active Supported
Looks up a patients enrolled/preferred faility:		 DGENPTA
2943 DBIA2943 Routine REGISTRATION 1999/10/29 Withdrawn Private
To support CIRN Exception Handling, CIRN PD needs to
include an option to Edit Patient Data.		 DG10
2965 Direct access to file 405.1 File REGISTRATION 1999/11/10 APPROVED Active Controlled Subscription 405.1
This DBIA documents references to the FACILITY MOVEMENT
TYPE file (#405.1).
2966 Use of TYPE OF PATIENT file File REGISTRATION 1999/11/10 APPROVED Active Controlled Subscription 391
This DBIA documents access to the TYPE OF PATIENT file
(#391)
2969 DBIA2969 File REGISTRATION 1999/11/10 APPROVED Active Private 2
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.
2988 IAs for VAFCTFU utilities Routine REGISTRATION 1999/11/19 APPROVED Active Controlled Subscription
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		 VAFCTFU
2990 Treating Facility List Routine REGISTRATION 1999/11/23 APPROVED Active Supported
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.		 VAFCTFU1
2993 DBIA2993 Routine REGISTRATION 1999/11/24 APPROVED Active Private
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))		 DGRUDD01 2014/02/21
3015 PID segment generation (CIRN PD) Routine REGISTRATION 2000/01/12 APPROVED Active Controlled Subscription
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.		 VAFCPID
3016 EVN segment generation (CIRN PD) Routine REGISTRATION 2000/01/12 APPROVED Active Controlled Subscription
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.		 VAFHLEVN 2015/12/15
3017 PD1 segment generator Routine REGISTRATION 2000/01/12 APPROVED Active Supported
Supported call for building of HL7 PD1 segment (Patient
Additional Demographics).		 VAFHLPD1
3018 PV1 segment generator Routine REGISTRATION 2000/01/12 APPROVED Active Supported
Supported calls for building of HL7 PV1 segment
(Patient Visit)		 VAFHLPV1
3019 DG CHK BS5 XREF Y/N Remote Procedure REGISTRATION 2000/01/20 APPROVED Active Supported DG CHK BS5 XREF Y/N
3020 DG CHK BS5 XREF ARRAY Remote Procedure REGISTRATION APPROVED Active Supported DG CHK BS5 XREF ARRAY
3021 DG CHK MEANS TEST DIV DISPLAY Remote Procedure REGISTRATION APPROVED Active Supported DG CHK MEANS TEST DIV DISPLAY
3022 DG CHK PAT MEANS TEST REQUIRED Remote Procedure REGISTRATION APPROVED Active Supported DG CHK PAT MEANS TEST REQUIRED
3023 DG CHK PAT/DIV MEANS TEST Remote Procedure REGISTRATION APPROVED Active Supported DG CHK PAT/DIV MEANS TEST
3027 Security/Sensitive Record access Routine REGISTRATION 2000/01/31 APPROVED Active Supported
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.		 DGSEC4
3029 TRANSFER FACILITY File REGISTRATION 2000/02/03 APPROVED Active Private 405
This integration agreement grants permission to the
subscribing package to read with FileMan the TRANSFER FACILITY field (#.05) in
the PATIENT MOVEMENT file (#405).
3037 ADT/HL7 EVENT REASON (#391.72) file access File REGISTRATION 2000/02/15 APPROVED Active Private 391.72
This IA allows the subscribing package to access the
ADT/HL7 EVENT REASON (#391.72) file.
3082 PROTOCOL Distribution Other REGISTRATION 2000/04/17 APPROVED Active Private
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
3097 DBIA3097 File REGISTRATION 2000/04/21 APPROVED Active Controlled Subscription 2
3101 DBIA3101 File REGISTRATION 2000/05/03 APPROVED Active Private 2
PCE name-spaced routine references $D(^DPT(IEN)) in
order to do a one-time file clean up.
3108 DGMST ENTER NEW MST Other REGISTRATION 2000/05/10 APPROVED Active Private
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.
3109 DBIA3109 Other REGISTRATION 2000/05/12 APPROVED Active Private
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.
3145 Health Summary Admissions Treating Spec File REGISTRATION 2000/07/14 APPROVED Active Private 42.4
Retrieval and display of recognized PTF treating
specialties.
3147 Health Summary Facility Treating Specialty File REGISTRATION 2000/07/14 APPROVED Active Private 45.7
3157 PATIENT TREATMENT FILE DATA Routine REGISTRATION 2000/08/07 APPROVED Active Supported
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)		 DGPTFAPI 2015/08/19
3164 DG PATIENT TREATMENT DATA Remote Procedure REGISTRATION 2000/08/14 APPROVED Active Supported
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)		 DG PATIENT TREATMENT DATA 2015/08/19
3266 OBTAIN PATIENT DOB FROM DPTLK1 Routine REGISTRATION 2000/12/05 APPROVED Active Controlled Subscription
The patient lookup routine, DPTLK1, has a useful api
for obtaining a formated date of birth. Imaging is requesting permission to
use this api.		 DPTLK1
3267 OBTAIN PATIENT SSN FROM DPTLK1 Routine REGISTRATION 2000/12/05 APPROVED Active Controlled Subscription
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.		 DPTLK1
3299 DBIA3299 Routine REGISTRATION 2001/01/12 APPROVED Active Private
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.		 VAFCPDAT
3301 3301 File REGISTRATION 2001/01/30 APPROVED Active Controlled Subscription 2
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.
3303 DBIA3303 File REGISTRATION 2001/02/07 APPROVED Active Private 391.98
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.
3304 DBIA3304 File REGISTRATION 2001/02/07 APPROVED Active Private 391.984
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.
3325 DBIA3325 Routine REGISTRATION 2001/03/01 APPROVED Active Private
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. 		DGRPTU
3326 DBIA3326 Routine REGISTRATION 2001/03/01 APPROVED Active Private DGMTU
3327 DBIA3327 File REGISTRATION 2001/03/01 APPROVED Active Private 2
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.
3328 DBIA3328 File REGISTRATION 2001/03/01 APPROVED Active Private 408.12
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.
3329 DBIA3329 File REGISTRATION 2001/03/01 APPROVED Active Private 408.13
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.
3330 DBIA3330 File REGISTRATION 2001/03/01 APPROVED Active Private 408.21
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.
3331 DBIA3331 File REGISTRATION 2001/03/01 APPROVED Active Private 408.22
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.
3338 DBIA 3338 - Imaging & VADPT routines Other REGISTRATION 2005/03/10 Retired Private
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."
3339 DBIA 3339 - FBCS & File 2 fields File REGISTRATION 2001/03/09 APPROVED Active Controlled Subscription 2
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)?		 2008/12/11
3340 DBIA 3340 - Imaging & file 2 xreferences File REGISTRATION 2001/03/09 Withdrawn Private 2
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.
3344 DG FIELD MONITOR Other REGISTRATION 2001/03/28 APPROVED Active Controlled Subscription
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.
3402 DG SENSITIVE RECORD ACCESS Remote Procedure REGISTRATION 2003/05/15 APPROVED Active Supported
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.		 DG SENSITIVE RECORD ACCESS
3403 DG SENSITIVE RECORD BULLETIN Remote Procedure REGISTRATION 2003/05/15 APPROVED Active Supported
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.		 DG SENSITIVE RECORD BULLETIN
3413 Download VIC Data Routine REGISTRATION 2001/06/25 Withdrawn Supported
The Registration package needs to be able to download
VIC data during the GUI Registration process.		 DGQESC5
3420 NOK Work Phone File REGISTRATION 2001/07/19 APPROVED Active Controlled Subscription 2
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.
3422 DBIA3422 File REGISTRATION 2001/07/23 APPROVED Active Private 391.71
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.
3426 DBIA3426 File REGISTRATION 2001/08/06 APPROVED Active Private 45
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.
3428 DBIA3428 File REGISTRATION 2001/08/08 Withdrawn Private 45.84
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.
3430 DBIA3430 File REGISTRATION 2001/08/09 APPROVED Active Private 40.8
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.
3431 DBIA3431 File REGISTRATION 2001/08/09 APPROVED Active Private 43
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.
3432 DBIA3432 File REGISTRATION 2001/08/09 APPROVED Active Private 405
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.
3433 DBIA3433 File REGISTRATION 2001/08/09 APPROVED Active Private 40.8
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)
3437 REGISTRATION FILE USED BY TIU - DG(40.8 File REGISTRATION 2001/08/15 APPROVED Active Private 40.8
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.		 TIUEN113
3444 REGISTRATION FILE USED BY TIU - DG(43 File REGISTRATION 2001/08/16 APPROVED Active Controlled Subscription 43
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.
3445 Determine the Service associated with a ward. File REGISTRATION 2001/08/22 APPROVED Active Private 42
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.
3456 DBIA3456-A Routine REGISTRATION 2001/09/18 APPROVED Active Controlled Subscription
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).		 DGNTAPI1
3457 DBIA3457 Routine REGISTRATION 2001/09/18 APPROVED Active Supported
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.		 DGNTAPI
3470 DBIA3470 Routine REGISTRATION 2001/10/18 APPROVED Active Private
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.		 DGPMV
3475 DBIA3475 File REGISTRATION 2001/11/05 APPROVED Active Controlled Subscription 2
The purpose of this DBIA is to allow Surgery to display
the patient's status related to environmental contaminants for patients having
ambulatory surgery.
3481 SC 0% NON COMPENSABLE Routine REGISTRATION 2001/11/23 APPROVED Active Controlled Subscription
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.		 DGMTR 2012/06/04
3489 DBIA3489 File REGISTRATION 2001/12/04 APPROVED Active Private 13
A direct read is used to display the CODE (#3) field if
the zero node exists using $DATA on the zero node.
3490 DBIA3490 File REGISTRATION 2001/12/04 Withdrawn Private 43
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.
3492 NAME VAFCPID2 Routine REGISTRATION 2001/12/12 APPROVED Active Private
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.		 VAFCPID2
3493 VAFCDD01 Routine REGISTRATION 2001/12/12 APPROVED Active Private
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.		 VAFCDD01
3494 VAFHPIVT Routine REGISTRATION 2001/12/12 APPROVED Active Private
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		 VAFHPIVT
3496 VAFC REMOTE PDAT Remote Procedure REGISTRATION 2001/12/19 APPROVED Active Controlled Subscription
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,"")		 VAFC REMOTE PDAT
3503 PATIENT DATES OF LEAVE FOR A BILLING DATE RANGE Routine REGISTRATION 2002/01/28 APPROVED Active Private
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.		 DGUTL2
3504 3504 File REGISTRATION 2002/01/30 APPROVED Active Private 2
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:
3511 DBIA3511 File REGISTRATION 2002/02/04 APPROVED Active Private 45
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:
3523 DBIA3523 Routine REGISTRATION 2002/02/20 APPROVED Active Supported DGMTU
3529 DBIA3529 File REGISTRATION 2002/02/15 APPROVED Active Controlled Subscription 21
Beneficiary Travel uses a direct read on the zero node
of the PERIOD OF SERVICE (#21) File.
3538 DBIA3538 File REGISTRATION 2002/03/05 APPROVED Active Private 43.1
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.
3545 DBIA3545 File REGISTRATION 2002/03/13 APPROVED Active Private 45
The Clinical Case Registries system needs access to the
'AAD' x-ref (admission date) and for field #80 (principle diagnosis).
3546 File 40.8 access File REGISTRATION 2002/03/14 Retired Controlled Subscription 40.8
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.
3549 VAFC HFS SCRATCH Other REGISTRATION 2002/04/01 APPROVED Active Private
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.		 VAFCHFS
3571 SENDING THE DIVISION ID TO CLAIMSMANAGER File REGISTRATION 2002/04/26 Withdrawn Private 40.8
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.
3581 DIQ FOR DATE ENTERED INTO FILE AND ALIAS File REGISTRATION 2002/05/16 APPROVED Active Private 2
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.
3593 DBIA3593 Routine REGISTRATION 2002/06/03 APPROVED Active Supported
Allow access to the Patient Lookup components for
checking Means Test Requirements and the Cleveland Alert.		 DPTLK6
3614 PROSTHETICS PATIENT ELIGIBILITY File REGISTRATION 2002/07/03 Withdrawn Private 2
The following are patient data to be passed to coreFLS
to support Purchasing and Inventory functions.
3619 GMT SECURITY KEY API Routine REGISTRATION 2002/07/11 APPROVED Active Controlled Subscription
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.		 DGREGDD1
3625 DBIA3625 File REGISTRATION 2002/07/23 Withdrawn Private 405
3630 VAFCQRY APIs Routine REGISTRATION 2002/07/30 APPROVED Active Controlled Subscription
MPIF and RG would like to call the generic segment
builders for version 2.4 messages for the PID, EVN and PD1 segments.		 VAFCQRY
3637 DBIA3637 Routine REGISTRATION 2002/08/06 APPROVED Active Private
Means Test generic utilities routine.		 DGMTUTL
3644 DBIA3644 File REGISTRATION 2002/08/07 APPROVED Active Private 2
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.
3646 EMPLOYEE ELIGIBILITY CODE CHECK Routine REGISTRATION 2004/05/25 APPROVED Active Controlled Subscription DGSEC4
3742 ACCESS TO ADDRESS FIELDS IN DPT File REGISTRATION 2002/08/29 APPROVED Active Private 2
Scheduling is requesting access to several address
fields in the Patient (#2) file.
3744 DBIA3744 Routine REGISTRATION 2002/09/03 APPROVED Active Supported VADPT
3745 DBIA3745 Routine REGISTRATION 2002/09/03 APPROVED Active Private VAFHLRO3
3787 DBIA3787 Other REGISTRATION 2003/08/06 APPROVED Active Private
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.
3788 Work Phone Number File REGISTRATION 2002/10/19 Pending Controlled Subscription 2
3789 DISPLAY MEANS TEST & ELIGIBILITY INFO Routine REGISTRATION 2002/10/20 APPROVED Active Controlled Subscription
Display Means Test info.		 DGMTU
3790 SERVICE OF WARD LOCATION File REGISTRATION 2002/10/20 Pending Controlled Subscription 42
3796 SCHEDULED ADMISSIONS File REGISTRATION 2002/10/23 Active Controlled Subscription 41.1
3797 PATIENT ENROLLMENT CLINIC/APPOINTMENTS File REGISTRATION 2002/10/23 APPROVED Active Controlled Subscription 2
3799 DBIA3799 Routine REGISTRATION 2002/10/23 APPROVED Active Supported
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)		 DGUTL4
3812 DBIA3812 Routine REGISTRATION 2002/10/25 APPROVED Active Controlled Subscription
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
-----------------------------		 DGENA 2015/08/07
3817 PXRM DIRECT READ OF THE PTF FILE File REGISTRATION 2002/11/15 APPROVED Active Private 45
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.
3829 DBIA3829-A File REGISTRATION 2002/11/04 Pending Private 35
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.
3830 DBIA3829-B File REGISTRATION 2002/11/04 Pending Private 81.3
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.
3855 Registration For DGRP Routine Routine REGISTRATION 2002/12/06 APPROVED Active Private
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.		 DGRP
3857 PATIENT SECURITY CHECK Routine REGISTRATION 2002/12/03 APPROVED Active Controlled Subscription
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		 DGSEC
3860 DGPF PATIENT RECORD FLAG Routine REGISTRATION 2003/07/08 APPROVED Active Controlled Subscription
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.		 DGPFAPI
3870 DG OPTIONS/MENUS ON SECURITY OFFICER MENU Other REGISTRATION 2003/01/10 APPROVED Active Private
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
3998 File 405 File REGISTRATION 2003/03/12 Withdrawn Private 405
4006 File 40.8 File REGISTRATION 2003/03/18 Withdrawn Private 40.8
4007 File 45.7 File REGISTRATION 2003/03/18 Withdrawn Private 45.7
4015 File 405.3 File REGISTRATION 2003/03/18 Withdrawn Private 405.3
4016 File 405.4 File REGISTRATION 2003/03/18 Withdrawn Private 405.4
4018 File 45.6 File REGISTRATION 2003/03/18 Withdrawn Controlled Subscription 45.6
4040 TIU reference to file 405.1 File REGISTRATION 2003/03/26 Withdrawn Private 405.1
4076 TIU Reference to file DGPM File REGISTRATION 2004/08/16 APPROVED Active Private 405
4079 Edit PATIENT (#2) file fields File REGISTRATION 2003/04/08 APPROVED Active Private 2
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
4080 BAD ADDRESS INDICATOR Routine REGISTRATION 2003/04/09 APPROVED Active Supported
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).		 DGUTL3
4116 NCEDIT DPTNAME Routine REGISTRATION 2003/06/04 APPROVED Active Private
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.		 DPTNAME
4138 NON-INTERACTIVE PATIENT LOOKUP LIST Routine REGISTRATION 2003/06/26 Withdrawn Controlled Subscription DPTLK1
4156 COMBAT VETERAN STATUS Routine REGISTRATION 2003/07/21 APPROVED Active Supported
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.		 DGCV
4177 DISK CONSUMPTION ESTIMATE FOR CLINICAL REMINDERS File REGISTRATION 2004/06/29 APPROVED Active Private
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
4192 DBIA4192 Routine REGISTRATION 2003/08/13 APPROVED Active Private
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.		 DGENA4 2019/09/20
4198 PATIENT ADDRESS EDIT API Routine REGISTRATION 2003/10/06 APPROVED Active Controlled Subscription
The API allows the user to edit patient's mailing
address.		 DGREGAED 2021/07/06
4205 DBIA4205 Routine REGISTRATION 2003/12/23 APPROVED Active Controlled Subscription
API to allow access to Inpatient CPTs and Inpatient
POVs.		 DGAPI
4220 DBIA4220-A File REGISTRATION 2003/11/17 APPROVED Active Controlled Subscription 46
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.
4221 INPATIENT POV FILE File REGISTRATION 2003/11/12 APPROVED Active Controlled Subscription 46.1
4238 DBIA4238-A Routine REGISTRATION 2003/09/16 APPROVED Active Private
Integrated Billing calls the HL7 function
$$MFE^VAFHLMFE when constructing the HL7 messages that are passed on through
Vitria for insurance confirmation.		 VAFHLMFE
4239 DBIA4238-B Routine REGISTRATION 2003/09/16 APPROVED Active Private
Integrated Billing calls the HL7 function
$$MFI^VAFHLMFI when constructing the HL7 messages that are passed on through
Vitria for insurance confirmation.		 VAFHLMFI
4242 DBIA4242 File REGISTRATION 2003/09/16 APPROVED Active Private 43
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.
4243 DBIA4243 File REGISTRATION 2003/09/16 APPROVED Active Private 408.13
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.
4244 DBIA4244 File REGISTRATION 2003/09/16 APPROVED Active Private 408.12
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.
4267 VDEF EVENTS AND EXTRACTION LISTS Other REGISTRATION 2004/08/23 Retired Supported
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
4280 DIC(21 File REGISTRATION 2004/05/27 APPROVED Active Private 21
4292 DBIA4292 Routine REGISTRATION 2003/11/06 APPROVED Active Supported
Supported calls for building of HL7 ZPD segment (VA
Specific Patient Demographics).		 VAFHLZPD
4312 COMBAT VET STATUS EXPIRED Routine REGISTRATION 2003/12/12 APPROVED Active Controlled Subscription
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.		 DGCVEXP
4317 ALLOW USEAGE OF DGUTQ Routine REGISTRATION 2003/12/23 Withdrawn Private
4318 ALLOW ACCESS TO ROUTINE DGUTQ Routine REGISTRATION 2003/12/29 APPROVED Active Private DGUTQ
4346 VAFHLU Routine REGISTRATION 2004/02/17 APPROVED Active Supported
Valid after patches DG*5.3*508 and SD*5.3*293 are
released.		 VAFHLU
4383 DGPF ASSIGNMENT LINK TIU PN Routine REGISTRATION 2004/03/29 APPROVED Active Controlled Subscription
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.		 DGPFAPI1 2018/05/29
4384 DGPF FILE/DELETE TIU PN LINK Routine REGISTRATION 2004/03/29 APPROVED Active Controlled Subscription
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.		 DGPFAPI2
4393 DPTNAME Routine REGISTRATION 2004/05/03 Retired Private
Kernel has the permission to use FORMAT^DPTNAME to
standardize person name as described in this DBIA.		 DPTNAME
4398 DBIA4398 Routine REGISTRATION 2004/04/09 APPROVED Active Controlled Subscription VAUTOMA 2015/09/08
4408 DBIA4408 Routine REGISTRATION 2004/06/24 APPROVED Active Controlled Subscription DGIBDSP
4418 ADT HL7 MSG Other REGISTRATION 2004/04/28 APPROVED Active Supported
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
4425 DBIA4425 File REGISTRATION 2004/05/07 APPROVED Active Controlled Subscription 41.41
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.
4430 DBIA4430 Other REGISTRATION 2004/05/24 APPROVED Active Private
Integrated billing has attached the IB option, IBJD
PERCENT PREREGISTERED, to the Registration menu Outputs for Preregistration
menu, [DGPRE PRE-REGISTER OUTPUTS].
4436 DBIA4436 Routine REGISTRATION 2004/06/03 APPROVED Active Controlled Subscription
This agreement will allow the Subscribing Packages the
ability to create and delete a Fee PTF entry using the following Registration
API call points.		 DGPTFEE
4438 DBIA4438 Routine REGISTRATION 2004/07/30 Retired Controlled Subscription DGENEGT1
4453 Edit COUNTY(#.117) field of the PATIENT(#2) file Routine REGISTRATION 2004/07/13 APPROVED Active Private
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.")		 XU8P328D
4457 ACCESS TO PTF API FOR CLINICAL REMINDER INDEX Routine REGISTRATION 2004/08/04 APPROVED Active Controlled Subscription
This API will allowed access to the PTF^DGPTPXRM API.		 DGPTPXRM
4459 MyHealtheVets Demographics File REGISTRATION 2005/12/02 APPROVED Active Private 2
This DBIA allows the MyHealtheVet Demographics
application access to fields in the PATIENT file.
4462 SHAD STATUS INDICATOR Routine REGISTRATION 2005/12/13 APPROVED Active Supported
This supported DBIA covers an API that will return a
value that indicates whether the patient has Project 112/SHAD exposure.		 DGUTL3
4495 DBIA4141-D Routine REGISTRATION 2004/08/04 APPROVED Active Private
Supported call for building of HL7 ZMH segment (VA
Specific Military History Segment). 		VAFHLZMH
4509 DBIA4509 Routine REGISTRATION 2004/09/23 APPROVED Active Controlled Subscription
Insurance display.		 DGRPDB
4512 VAFHAPV1 Routine REGISTRATION 2006/01/26 Expired Private VAFHAPV1
4521 4521 Routine REGISTRATION 2004/10/29 APPROVED Active Private
This routine and entry point is used for building the
PXRMINDX( crossreference with data from the PTF file. There are no required
variables.		 DGPTDDCR
4534 ACCESS TO PTF CLOSE OUT (#45.84) FILE File REGISTRATION 2006/02/13 APPROVED Active Controlled Subscription 45.84
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.		 2018/03/26
4535 VAFHLZRD Routine REGISTRATION 2006/02/14 APPROVED Active Private VAFHLZRD
4536 VAFHLZSP Routine REGISTRATION 2006/02/14 APPROVED Active Controlled Subscription VAFHLZSP 2010/06/19
4559 DBIA4141-C Routine REGISTRATION 2004/11/09 APPROVED Active Private
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		 VAFHLZCL 2018/08/08
4563 DGPF DISPLAY PATIENT RECORD FLAG Routine REGISTRATION 2004/11/20 APPROVED Active Controlled Subscription
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.		 DGPFAPI
4592 DBIA4589-D Other REGISTRATION 2005/02/03 APPROVED Active Controlled Subscription
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.		 2010/06/08
4597 DBIA4597 File REGISTRATION 2005/02/04 APPROVED Active Private 42.6
4598 DBIA4598 File REGISTRATION 2005/02/07 APPROVED Active Private 42.7
4648 VAFC LOCAL GETCORRESPONDINGIDS Remote Procedure REGISTRATION 2010/12/15 APPROVED Active Controlled Subscription
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"		 VAFC LOCAL GETCORRESPONDINGIDS VAFCTFU2 2011/01/14
4678 VAFCTFU GET TREATING LIST Remote Procedure REGISTRATION 2005/06/08 APPROVED Active Supported VAFCTFU GET TREATING LIST
4679 VAFCTFU CONVERT ICN TO DFN Remote Procedure REGISTRATION 2005/12/20 APPROVED Active Supported VAFCTFU CONVERT ICN TO DFN
4680 VAFCTFU CONVERT DFN TO ICN Remote Procedure REGISTRATION 2005/12/20 APPROVED Active Supported VAFCTFU CONVERT DFN TO ICN
4686 PATIENT SERVICE B-TYPE OPTIONS Remote Procedure REGISTRATION 2005/09/09 APPROVED Active Private
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.
4688 STANDARD RULES FOR REQUIRING A MEANS TEST Routine REGISTRATION 2005/06/28 APPROVED Active Controlled Subscription
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).		 DGMTR
4737 PFSS PID SEGEMENT BUILDER Routine REGISTRATION 2005/07/20 APPROVED Active Controlled Subscription
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.		 VAFPFSPD
4780 DBIA4780 Routine REGISTRATION 2005/08/16 Pending Private
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.		 DGPFSS1
4781 BUILD A28/A31 MESSAGE FOR PFSS Routine REGISTRATION 2005/08/17 APPROVED Active Private
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.		 VAFPFSM1
4798 VAFC NEW NC TREATING FACILITY Remote Procedure REGISTRATION 2010/12/15 APPROVED Active Private
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.		 2011/01/14
4800 EMERGENCY RESPONSE INDICATOR Routine REGISTRATION 2005/09/23 APPROVED Active Supported DGUTL 2020/04/08
4807 API FOR RATED DISABILITIES Routine REGISTRATION 2005/10/05 APPROVED Active Supported
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.		 DGRPDB
4808 DG SECURITY LOG SECURITY LEVEL File REGISTRATION 2010/12/28 APPROVED Active Private 38.1
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;		 2011/01/05
4817 PFSS EVN SEGMENT BUILDER Routine REGISTRATION 2005/10/24 APPROVED Active Controlled Subscription
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.		 VAFPFSEV
4840 PROCESS INBOUND BATCH HEC ORU MESSAGES TO A31 Routine REGISTRATION 2006/04/11 APPROVED Active Controlled Subscription
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.		 DGPFSS2
4849 DBIA #4849 Other REGISTRATION 2006/04/20 APPROVED Active Private 771
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
4865 DBIA4865 File REGISTRATION 2006/06/14 APPROVED Active Private 2
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.
4869 DBIA4869 File REGISTRATION 2006/08/03 APPROVED Active Private 45.7
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
4886 UPDATE PATIENT ADDRESSES Routine REGISTRATION 2006/08/28 APPROVED Active Controlled Subscription
This API allows the user to update a patient's mailing
or temporary address.		 DGADDUTL
4895 ADD PATIENT RELATION INFO FROM HEC File REGISTRATION 2006/08/29 APPROVED Active Private 408.12
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		 2006/11/29
4903 PATIENT RECORD FLAG DATA RETRIEVAL Routine REGISTRATION 2011/01/06 APPROVED Active Controlled Subscription
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.		 DGPFAPIH 2011/06/07
4921 VAFCSB APIS Routine REGISTRATION 2006/10/11 APPROVED Active Controlled Subscription
These APIs are used to include the Primary View
Criteria to the MPI for use in scoring the validity of the update.		 VAFCSB
4932 ANNUAL MEANS TEST FILE File REGISTRATION 2006/11/29 APPROVED Active Private 408.31
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 		2006/11/29
4933 ACCESS REGISTRATION MEANS TEST CODE Routine REGISTRATION 2006/11/29 APPROVED Active Private
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.		 DGMTAUD 2006/11/29
4934 SOURCE OF INCOME TEST FILE File REGISTRATION 2006/11/29 APPROVED Active Private 408.34
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		 2006/11/29
4937 DBIA4937 File REGISTRATION 2011/01/10 APPROVED Active Private 10
Read access of the Race file using the 'B'
cross-reference.		 2011/08/02
4938 PATIENT file File REGISTRATION APPROVED Active Private 2
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		 2007/02/01
4940 DBIA4940 File REGISTRATION 2011/01/10 APPROVED Active Private 10.2
Read access of the Ethnicity file using the "B"
cross-reference.		 2011/08/02
4941 MEANS TEST STATUS file File REGISTRATION 2006/12/11 APPROVED Active Controlled Subscription 408.32
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		 2007/03/05
4942 PATIENT MOVEMENT file File REGISTRATION 2006/12/11 APPROVED Active Private 405
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		 2007/03/04
4943 TREATING FACILITY LIST File REGISTRATION 2006/12/11 APPROVED Active Private 391.91
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		 2007/03/04
4944 SOURCE OF ADMISSION File REGISTRATION 2006/12/11 APPROVED Active Private 45.1
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		 2007/03/04
4945 PTF file File REGISTRATION 2006/12/11 APPROVED Active Private 45
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		 2007/03/04
4946 SPECIALTY file File REGISTRATION 2006/12/12 APPROVED Active Private 42.4
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		 2007/03/04
4947 PATIENT ENROLLMENT File REGISTRATION 2006/12/12 APPROVED Active Private 27.11
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		 2007/03/05
4969 DGENCDA - Catastrophic Disability API Routine REGISTRATION 2007/01/22 APPROVED Active Private DGENCDA 2011/03/22
5012 DBIA5012 File REGISTRATION 2007/07/05 Pending Private 38.5
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)
5016 SCREEN FOR ACTIVE PROVIDER Routine REGISTRATION 2007/07/13 APPROVED Active Controlled Subscription
Screen for active provider in NEW PERSON (#200) file. 		DGPMDD 2007/07/13
5017 Change notification for file 42.4 File REGISTRATION 2007/07/25 APPROVED Active Private 42.4
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.		 2008/03/04
5018 DBIA5018 Routine REGISTRATION 2011/01/10 Pending Private
Create pseudo SSN for John Doe patients or for a
patient that can't provide their SSN at Registration.		 DGRPDD1
5031 DBIA5031 File REGISTRATION 2007/09/18 Pending Private 2
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
5036 ENROLLMENT RATED DISABILITY UPLOAD AUDIT REPORTING Routine REGISTRATION 2007/10/23 APPROVED Active Private
This API will provide Rated Disability changes from the
ENROLLMENT RATED DISABILITY UPLOAD AUDIT file (#390) for a single or multiple
Veterans.		 DGENRDUA 2008/02/06
5039 AR Access to Patient File File REGISTRATION 2007/11/07 APPROVED Active Private 2
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)		 2007/11/13
5130 DBIA-5130 Routine REGISTRATION 2011/01/19 Pending Private
An API is needed that sends a request for Patient Data
from the Last Site Treated.		 DGROHLS
5132 PATIENT FILE-GUARDIAN DATA File REGISTRATION 2008/02/12 APPROVED Active Private 2
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.		 2008/03/07
5143 VADPT3 Routine REGISTRATION 2008/02/19 Pending Private VADPT3
5154 NAME VAFCPID2 Routine REGISTRATION 2008/03/04 APPROVED Active Private
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.		 VAFCPID2 2008/03/04
5158 PATIENT ENROLLMENT File REGISTRATION 2008/03/17 APPROVED Active Private 27.11
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.		 2008/04/24
5194 Recall Reminder Change to DGRPD Routine REGISTRATION 2008/05/07 Withdrawn Private
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		 DGRPD
5295 DSIV PATIENT ACCESS File REGISTRATION 2008/11/23 Withdrawn Private 2
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
5302 FBCS FILE 43.4 File REGISTRATION 2009/03/12 Retired Controlled Subscription 43.4
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
5310 FBCS ACCESS TO DGRPU Routine REGISTRATION 2009/03/12 Withdrawn Controlled Subscription
These components are used by the FBCS application to
format the patient address data.		 DGRPU
5311 FBCS ACCESS TO DGSDUTL Routine REGISTRATION 2009/03/12 Withdrawn Private
These components are used by the FBCS application for
patient demographic inquiries.		 DGSDUTL
5334 FBCS ACCESS TO DGPM GLOBAL File REGISTRATION 2009/01/11 Withdrawn Controlled Subscription 405
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
5335 ANNUAL MEANS TEST ACCESS File REGISTRATION 2009/01/12 Withdrawn Controlled Subscription 408.31
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
5337 MEANS TEST STATUS ACCESS File REGISTRATION 2009/01/12 Withdrawn Controlled Subscription 408.32
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
5338 MAS PARAMETERS ACCESS File REGISTRATION 2009/01/12 Withdrawn Controlled Subscription 43
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
5345 FBCS ACCESS TO GLOBAL DGS(41.41 File REGISTRATION 2009/01/14 Withdrawn Controlled Subscription 41.41
5346 FBCS ACCESS TO GLOBAL DIC(21 File REGISTRATION 2009/01/14 Withdrawn Controlled Subscription 21
5347 FBCS ACCESS TO PATIENT File REGISTRATION 2009/01/14 Retired Controlled Subscription 2
FBCS needs access to the Eligibility Status date for
demographic display.
^DPT(D0,.361)
.3612 ELIGIBILITY STATUS DATE .361;2 Fileman read
5354 MILITARY SERVICE INFORMATION Routine REGISTRATION 2009/01/29 APPROVED Active Private
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. 		DGMSE 2011/07/18
5364 ADD VAFCPTAD(PARAM) Routine REGISTRATION 2009/02/09 APPROVED Active Private
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.		 VAFCPTAD 2009/04/29
5375 ENROLLMENT STATUS File REGISTRATION 2009/02/27 APPROVED Active Private 27.15
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. 		2009/04/20
5379 FBCS ACCESS TO DGENA Routine REGISTRATION 2009/03/09 APPROVED Active Controlled Subscription DGENA 2013/04/10
5380 FBCS ACCESS TO DGENPTA Routine REGISTRATION 2009/03/09 Withdrawn Controlled Subscription DGENPTA
5381 FBCS ACCESS TO DGENQRY Routine REGISTRATION 2009/03/09 Withdrawn Controlled Subscription DGNEQRY
5382 FBCS ACCESS TO DGMTH Routine REGISTRATION 2009/03/09 Withdrawn Controlled Subscription DGMTH
5383 FBCS ACCESS TO DGMTR Routine REGISTRATION 2009/03/09 Retired Controlled Subscription DGMTR
5384 FBCS ACCESS TO DGPMV10 Routine REGISTRATION 2009/03/09 Withdrawn Controlled Subscription
FBCS access to INP^DGPMV10 to set-up inpt variables
needed (mimic VAIP array)		 DGPMV10
5431 PATIENT FILE File REGISTRATION 2009/04/14 APPROVED Active Private 2
The MRSA INITIATIVE REPORTS would like to request
Direct Global access to the following fields of the Patient file (#2) for
reporting purposes.		 2009/06/08
5433 CENSUS FILE File REGISTRATION 2009/04/14 APPROVED Active Controlled Subscription 41.9
The MRSA INITIATIVE REPORTS would like to request
Direct Global access to the following fields of the Census file (#41.9) for
reporting purposes.		 2009/06/08
5491 PATIENT RECORD FLAG VARIABLE POINTER Routine REGISTRATION 2011/01/31 APPROVED Active Controlled Subscription
Builds and returns a variable pointer to the Patient
Record Flag National or Local files based on the textual flag name.		 DGPFAPIU 2011/06/07
5528 ETHNICITY FILE ACCESS File REGISTRATION 2010/05/05 APPROVED Active Private 10.2
LAB SERVICE package will use the NAME (#.01), HL7 VALUE
(#3) and INACTIVE (#200) fields in Fileman sort and print templates.		 2010/11/02
5534 DBIA5534 Routine REGISTRATION 2010/06/16 Pending Private
DG1 - Diagnosis Information Segment		 VAFHLDG1
5535 DBIA5535 Routine REGISTRATION 2010/06/16 Pending Private
PR1 - Procedure Information Segment		 VAFHLPR1
5536 DBIA5536 Routine REGISTRATION 2010/06/17 Pending Private
ZSC - VA-Specific Stop Code Segment		 VAFHLZSC
5537 DBIA5537 Routine REGISTRATION 2010/06/17 Pending Private
ZEN - VA-Specific Enrollment Segment		 VAFHLZEN
5538 DBIA5538 Routine REGISTRATION 2010/06/17 Pending Private
ROL - Role Segment		 VAFHLROL
5571 DBIA5571 File REGISTRATION 2010/10/21 Pending Private 2
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.
5597 DPT File REGISTRATION 2011/02/04 APPROVED Active Controlled Subscription 2
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.
5598 NOK WORK TELEPHONES File REGISTRATION 2011/02/04 Pending Private 2
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.
5611 HOSPITAL LOCATION DATA AUDITING Other REGISTRATION 2011/02/17 APPROVED Active Controlled Subscription
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		 2011/02/18
5616 ADT/HL7 PIVOT FILE IEN File REGISTRATION 2011/03/21 APPROVED Active Private 391.71
Lab Service is allowed Fileman Read access to return
the ADT/HL7 Pivot IEN via the "D" cross reference.		 2011/03/21
5627 Patient File POW field (#.525) File REGISTRATION 2011/04/15 APPROVED Active Private 2
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. 		2011/05/03
5708 ALIAS SUBFILE File REGISTRATION 2011/08/08 APPROVED Active Controlled Subscription 2
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)		 2013/04/24
5783 MILITARY SERVICE EPISODE API Routine REGISTRATION 2012/03/20 APPROVED Active Controlled Subscription
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.		 DGMSEUTL 2024/04/04
5797 DBIA5797 - Update File #41.41 by VPS File REGISTRATION 2012/05/07 APPROVED Active Controlled Subscription 41.43
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.		 2012/11/09
5798 DBIA5798 - Update File #41.43 by VPS File REGISTRATION 2012/05/07 APPROVED Active Private 41.43
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.		 2012/11/09
5799 DBIA5799 UPDATE OF FIELDS IN FILE #2 File REGISTRATION 2012/05/16 APPROVED Active Private 2
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.		 2012/11/29
5817 Read/Update 41.42 file entries File REGISTRATION 2012/07/17 APPROVED Active Private 41.42
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. 		2012/11/07
5821 CENSUS DATE File REGISTRATION 2012/07/01 APPROVED Active Private 45.86 2013/07/10
5822 CENSUS/DISCHARGE/MOVEMENT/SURGERY DATES File REGISTRATION 2012/07/01 APPROVED Active Private 45 2013/07/10
5831 PATIENT FILE FIELDS File REGISTRATION 2012/08/08 APPROVED Active Private 2
This ICR documents access to several Patient (#2) file
fields not supported by other ICRs or APIs for the VPS Kiosk project.		 2012/08/08
5839 VPS PATIENT LOOKUP Routine REGISTRATION 2012/08/30 Withdrawn Controlled Subscription DPTLK1
5851 PADP PULL OF ADMISSION INFO File REGISTRATION 2012/10/03 Withdrawn Private 45
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.
5852 PADP PULL OF EMERGENCY CONTACT INFO File REGISTRATION 2012/10/03 Withdrawn Private 2
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.
5859 DG SENSITIVE RECORD ACCESS Remote Procedure REGISTRATION 2012/10/04 Withdrawn Private
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.		 DG SENSITIVE RECORD ACCESS
5860 DG SENSITIVE RECORD BULLETIN Remote Procedure REGISTRATION 2012/10/04 Withdrawn Private
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.		 DG SENSITIVE RECORD BULLETIN
5888 VIC API Routine REGISTRATION 2012/12/13 APPROVED Active Controlled Subscription
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.		 DPTLK 2013/11/20
5889 DG VIC PATIENT LOOKUP Remote Procedure REGISTRATION 2012/12/13 Deferred (re)approval until a Release Occurs Controlled Subscription
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.		 DG VIC PATIENT LOOKUP
5892 DBIA5892 Routine REGISTRATION 2013/01/16 Pending Private DGENA4 2013/04/10
5894 DBIA5894 Routine REGISTRATION 2013/01/24 APPROVED Active Private
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.		 DGSDU 2013/03/25
5904 DG PRINT PATIENT LABEL Routine REGISTRATION 2013/03/12 APPROVED Active Private
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.		 DGPLBL 2016/04/12
5905 DG PRINT WRISTBAND Routine REGISTRATION 2013/03/18 APPROVED Active Private DGPWB 2015/04/10
5928 DBIA 5928 Routine REGISTRATION 2013/06/18 APPROVED Active Private
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. 		DGSAUTL 2013/06/24
5932 Lab Access to Room-Bed Wards Which Can Assign Multiple File REGISTRATION 2013/06/24 APPROVED Active Private 405.4
Lab has permission to access the ROOM-BED file (#405.4) WARD(S) WHICH CAN
ASSIGN Multiple. 		2013/06/28
5991 READ B CROSS REFERENCE OF PRF NATIONAL FLAG FILE File REGISTRATION 2013/07/17 Pending Private 26.15
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.		 2013/10/17
6002 DGPFMPI Routine REGISTRATION 2013/08/01 APPROVED Active Private
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.		 DGPFMPI 2013/08/21
6014 MEANS TEST DATA FIELDS IN MAS PARAMETERS FILE File REGISTRATION 2013/08/12 APPROVED Active Private 43
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.		 2018/05/02
6025 PATIENT APPOINTMENT MULTIPLE File REGISTRATION 2014/02/12 Pending Private 2
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.
6030 WARD AT DISCHARGE Routine REGISTRATION 2014/03/07 APPROVED Active Private
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.		 DGPMUTL 2017/04/03
6031 DBIA6031 Routine REGISTRATION 2014/03/19 Withdrawn Controlled Subscription
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 		DGENA
6037 DGPM C CROSS REFERENCE File REGISTRATION 2014/04/10 Withdrawn Private 405
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.
6053 MBAA ACCESS TO THE PATIENT FILE File REGISTRATION 2014/04/23 APPROVED Active Private 2
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.		 2015/03/23
6098 MEANS TEST STATUS file File REGISTRATION 2014/08/24 APPROVED Active Private 408.31
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.		 2015/07/22
6099 READ PATIENT ENROLLMENT (#27.11) FILE File REGISTRATION 2014/08/24 APPROVED Active Controlled Subscription 27.11
VPS Kiosks has a need to provide patient eligibility
information to the VetLink application.		 2015/04/27
6106 DGCN(391.91 GET DFN FROM EDIPI File REGISTRATION 2014/09/24 Withdrawn Controlled Subscription 391.91
Treating Facility List where patients have had
treatment.
6125 READ PATIENT FILE FIELDS File REGISTRATION 2014/11/06 APPROVED Active Controlled Subscription 2 2015/02/25
6130 DGPTFUT Routine REGISTRATION 2014/11/20 APPROVED Active Controlled Subscription
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.		 DGPTFUT 2015/08/03
6138 HEALTH BENEFIT PLAN INFORMATION Routine REGISTRATION 2014/12/02 APPROVED Active Controlled Subscription
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.		 DGHBPUTL 2015/12/17
6144 PID SEGMENT BUILDING - RETURN RACE AND ETHNICITY Routine REGISTRATION 2015/01/13 APPROVED Active Private
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.		 VAFHLPI1 2015/08/04
6145 VPS READ 40.8 File REGISTRATION 2015/01/20 Withdrawn Controlled Subscription 40.8
This IA provides for the Fileman read of the NAME,
INSTITUTION FILE POINTER, and FACILITY NUMBER fields in the INSTITUTION FILE
file #40.8.
6179 VPS PAT PROVIDER AND ATTENDING File REGISTRATION 2015/03/10 Withdrawn Controlled Subscription 2
6213 INPATIENT VADPT30 Routine REGISTRATION 2015/08/17 Withdrawn Controlled Subscription
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.		 VADPT30
6284 HMP ACCESS TO DGCN(391.91 File REGISTRATION 2015/11/25 Withdrawn Controlled Subscription 391.91
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.
6354 DGPF ASSIGN FLAG Other REGISTRATION 2016/02/12 APPROVED Retired Controlled Subscription
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.
**********************************************************************		 2016/05/12
6373 LOOKUP PATIENTS IN PATIENT FILE File REGISTRATION 2016/02/24 Withdrawn Controlled Subscription 2
This integration agreement allows subscribing packages
to look up patients in the PATIENT file (#2).
6378 VA Community Care Access to Registration Options Other REGISTRATION 2016/02/29 APPROVED Active Private
Responsibility for processing VA Community Care (VACC)
claims has changed from the VISNs/VAMCs to the Chief Business Office for
Purchased Care (CBOPC). As a national program, staff members often require
access to multiple VistA systems in order to perform their duties. 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.		 2016/03/15
6405 LANGDEL~DGPRE Routine REGISTRATION 2016/05/10 APPROVED Active Private
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.		 DGRPE 2016/07/22
6406 LANGUAGE DATE/TIME File REGISTRATION 2016/05/11 APPROVED Active Private 2
Scheduling package requests permission to read/update
using FileMan to all fields in the LANGUAGE DATE/TIME multiple (#7) of the
PATIENT file (#2).		 2016/07/22
6415 HMP USE OF DGPF EDIT ASSIGNMENT PROTOCOL Other REGISTRATION 2016/05/27 APPROVED Retired Controlled Subscription
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.
*********************************************************************		 2016/08/12
6416 HMP USE OF DGPF CHANGE ASSIGNMENT OWNERSHIP Other REGISTRATION 2016/05/27 APPROVED Retired Controlled Subscription
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.
*********************************************************************		 2016/08/12
6419 MBAA ACCESS TO 1010EZ DATA File REGISTRATION 2016/06/01 APPROVED Active Controlled Subscription 2
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.		 2016/06/13
6421 VAFC DOD ACCEPT SET/DISPLAY Remote Procedure REGISTRATION 2016/06/20 APPROVED Active Private
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"		 VAFC DOD ACCEPT SET/DISPLAY 2016/08/10
6430 DATE OF DEATH UPDATE CHECK Routine REGISTRATION 2016/07/19 Pending Private
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.		 VAFCDODA 2016/10/12
6487 VIAB READ DPT(D0,0) - FULL SUBSCRIPT File REGISTRATION 2016/08/25 APPROVED Active Private 2
This documents the Vista Integration Adapter application's use of the PATIENT
file.		 2016/11/10
6596 PATIENT FILE ACCESS File REGISTRATION 2016/11/03 APPROVED Active Private 2
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.		 2018/07/26
6606 VAFHPIVT Routine REGISTRATION 2016/11/09 Pending Private
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.		 VAFHPIVT
6607 SC PERCENTAGE File REGISTRATION 2016/11/09 APPROVED Active Private 2
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.		 2016/11/09
6609 WARD File REGISTRATION 2016/11/10 APPROVED Active Private 42
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. 		2016/11/10
6610 FACILITY MOVEMENT TYPE File REGISTRATION 2016/11/10 APPROVED Active Private 405.1
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. 		2016/11/10
6611 SCHEDULED ADMISSION File REGISTRATION 2016/11/10 APPROVED Active Private 41.1
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. 		2016/11/10
6612 ROOM-BED File REGISTRATION 2016/11/10 APPROVED Active Private 405.4
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. 		2016/11/10
6613 PATIENT MOVEMENT File REGISTRATION 2016/11/10 APPROVED Active Private 405
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. 		2016/11/10
6741 RESIDENTIAL ADDRESS DISPLAY Routine REGISTRATION 2017/03/02 Withdrawn Controlled Subscription
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 		DGADDUT1
6752 OUTPATIENT PHARMACY PATIENT INQUIRY Routine REGISTRATION 2017/03/29 Withdrawn Controlled Subscription
This allows users of the Patient Medication LM to do
patient inquiry without leaving the list manager		 DGRPD
6759 DGWPT BYWARD Remote Procedure REGISTRATION 2017/05/01 APPROVED Retired Private
**********************************************************************
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.		 DGWPT BYWARD 2017/10/18
6810 CAPRI Call to VAFCPTAD Routine REGISTRATION 2017/08/08 Pending Controlled Subscription VAFCPTAD
6812 REGISTRATION FILE USED BY BCMA - DG(43 File REGISTRATION 2017/08/21 APPROVED Active Private 43
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.		 2017/09/06
6831 CPT AND DIAGNOSIS UPDATE Routine REGISTRATION 2017/11/13 Pending Private
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.		 DGAPI
6850 PTF ICD DIAGNOSIS NOTIFICATION Other REGISTRATION 2017/11/24 APPROVED Active Controlled Subscription
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.		 2018/06/19
6873 DG OTH ELIGIBILITY PATIENT STATUS Routine REGISTRATION 2018/02/13 APPROVED Active Private
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.		 DGOTHBTN 2018/05/29
6874 DGPF DBRS DATA Routine REGISTRATION 2018/02/13 APPROVED Active Controlled Subscription
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).		 DGPFDBRS 2018/05/29
6905 Option DG G&L CHANGES VIEW used on external menus Other REGISTRATION 2018/04/10 APPROVED Active Private
Allow the G&L view changes option (DG G&L CHANGES VIEW)
to be assigned to menus on namespaces outside of DG.		 2018/05/29
6912 READ ACCESS TO DIC(13 File REGISTRATION 2018/05/03 APPROVED Active Private 13
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. 		2018/12/03
6913 READ ACCESS TO THE DIC(11 File REGISTRATION 2018/05/03 APPROVED Active Private 11
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. 		2018/12/03
6917 CCR&A USE OF VAFHLIN1 Routine REGISTRATION 2018/06/04 APPROVED Active Controlled Subscription
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.		 VAFHLIN1 2018/08/14
6922 GIVE THIS DBIA A BETTER NAME THAN DBIA6922 File REGISTRATION 2018/06/08 Pending Private
6923 CAMP LEJEUNE STATUS INDICATOR Routine REGISTRATION 2018/06/12 Withdrawn Supported
This supported DBIA covers an API that will return a
value that indicates whether the patient has Camp Lejeune exposure.		 DGUTL3
6948 DGMXVLD Routine REGISTRATION 2018/08/01 Pending Private
Incoming HL7 message PID validation tags.		 DGMXVLD
6949 DGMXHL7 Routine REGISTRATION 2018/08/01 Pending Private
Tags for building HL7 messages to send to MASS.		 DGMXHL7
6984 PATIENT FILE File REGISTRATION 2018/10/25 APPROVED Active Private 2
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.		 2018/11/13
7009 DGPF PRF EVENT Other REGISTRATION 2019/01/24 APPROVED Active Controlled Subscription
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		 2021/08/19
7019 Scheduling access to address data File REGISTRATION 2019/02/26 APPROVED Active Controlled Subscription 2
************************************************************************
* *
* 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
*
* *
************************************************************************		 2019/05/21
7020 Scheduling access to patient flags (local) File REGISTRATION 2019/02/26 APPROVED Active Private 26.11
VS GUI displays patient flags to schedulers. It
requires FileMan read access to the following fields:
.01 Name .02 Status		 2019/04/17
7021 VS GUI access to Patient flags (national) File REGISTRATION 2019/02/26 APPROVED Active Private 26.15
VS GUI displays patient flags to schedulers. It
requires FileMan read access to the following fields:
.01 Name .02 Status		 2019/04/17
7022 VS GUI access to Patient Flag Assignment File REGISTRATION 2019/02/26 APPROVED Active Private 26.13
VS GUI displays patient flags to schedulers. It
requires FileMan read access to the following fields:
.03 Status		 2019/05/21
7023 VS GUI access to patient enrollment data File REGISTRATION 2019/02/26 APPROVED Active Private 27.11 2019/04/17
7024 VS GUI access to Medical Center Division fields File REGISTRATION 2019/02/26 APPROVED Active Controlled Subscription 40.8
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		 2023/11/15
7025 VS GUI access to MAS Parameters (#43) file File REGISTRATION 2019/02/27 APPROVED Active Private 43 2019/04/17
7028 VS GUI access to Patient's next of kin and employer fields File REGISTRATION 2019/02/27 APPROVED Active Private 2
************************************************************************
* *
* 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
*
* *
************************************************************************		 2019/05/28
7029 VS GUI access to Patient's eligibility information File REGISTRATION 2019/02/27 APPROVED Active Private 2
************************************************************************
* *
* 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
*
* *
************************************************************************		 2019/05/28
7030 VS GUI access to patient appointment data File REGISTRATION 2019/02/28 APPROVED Active Private 2.98 2019/04/17
7034 VS GUI access to routine DGNFUNC Routine REGISTRATION 2019/02/28 APPROVED Active Private
$$FML^DGNFUNC returns the patient's name formatted in
'First Middle Last Suffix' format.		 DGNFUNC 2019/04/17
7035 VS GUI access to DGPMV10 routine Routine REGISTRATION 2019/03/11 Pending Private DGPMV10
7036 VS GUI access to DGSEC4 routine Routine REGISTRATION 2019/03/12 APPROVED Active Private
************************************************************************
* *
* 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
*
* *
************************************************************************		 DGSEC4 2019/05/21
7037 VS GUI access to routine DGUTL3 Routine REGISTRATION 2019/03/12 Pending Private DGUTL3
7049 VS GUI access to Patient Movement (#405) file. File REGISTRATION 2019/03/20 APPROVED Active Private 405 2019/05/28
7050 VS GUI access to Eligibility Code file (#8) File REGISTRATION 2019/03/22 APPROVED Active Private 8
************************************************************************
* *
* 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
*
* *
************************************************************************		 2019/05/28
7052 VS GUI access to MAS Eligibility Code (#8.1) File REGISTRATION 2019/04/01 APPROVED Active Private 8.1
************************************************************************
* *
* 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
*
* *
************************************************************************		 2019/05/28
7055 VAFC MVI MGRTD FACILITIES UPDT Remote Procedure REGISTRATION 2019/04/10 APPROVED Active Private
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).		 VAFC MVI MGRTD FACILITIES UPDT 2019/05/15
7088 DGMTU4 - Annual means test date determination Routine REGISTRATION 2019/07/11 APPROVED Active Controlled Subscription
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.		 DGMTU4 2019/07/19
7104 External Format of Subgroup Routine REGISTRATION 2019/10/02 APPROVED Active Private
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.		 DGENU 2019/10/02
7107 DGPFAA Routine REGISTRATION 2019/11/14 APPROVED Active Controlled Subscription
This documents the use of tags in routine DGPFAA to
retrieve patient record flags.		 DGPFAA 2019/11/22
7108 DGPFAAH Routine REGISTRATION 2019/11/14 APPROVED Active Controlled Subscription
This documents the use of tags in routine DGPFAAH to
retrieve patient record flag activity.		 DGPFAAH 2019/11/22
7109 VADPT Routine REGISTRATION 2019/11/26 APPROVED Active Supported
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.		 VADPT
7125 DSS APPLICATION ACCESS TO PATIENT FLAG ASSIGNMENT File REGISTRATION 2020/02/04 APPROVED Active Private 26.13
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.		 2022/07/25
7182 ALLOW IB TO READ ENROLLMENT FIELDS IN THE PATIENT FILE File REGISTRATION 2020/06/18 Pending Controlled Subscription 2
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
7185 DBIA7185 Routine REGISTRATION 2020/07/16 APPROVED Active Private
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		 VAFHLZCE 2020/12/01
7189 DG MENU OPTIONS FOR BILLING USERS Other REGISTRATION 2020/08/04 APPROVED Active Private
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.		 2020/09/04
7198 VDIF access to VA MPI FTL Other REGISTRATION 2020/09/03 Pending Private
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.
7208 RETRIEVE ENROLLMENT STATUS Routine REGISTRATION 2020/10/23 APPROVED Active Controlled Subscription
This API will be used to determine if the Patient is
known to Enrollment System or not by calling E&E Web Service.		 DGREGEEWS 2021/03/03
7214 DGPFAAH Routine REGISTRATION 2021/01/11 APPROVED Active Controlled Subscription
Retrieve list of history IENs for an assignment.		 DGPFAAH 2021/02/02
7229 DBIA7229 File REGISTRATION 2021/02/24 APPROVED Active Controlled Subscription 26.13
^DGPF(26.13,"C" use of the "C" cross-reference for
patient look-up.		 2021/03/12
7232 SCHEDULED ADMISSIONS FILE ENTRY NOTIFIER Other REGISTRATION 2021/03/04 APPROVED Active Controlled Subscription
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.		 2021/08/25
7233 VAFC LOCAL GETCORRESPONDINGIDS Routine REGISTRATION 2021/03/15 Withdrawn Private
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.		 VAFCTFU2
7243 ACCESS TO THE OTH REPORT Routine REGISTRATION 2021/04/07 APPROVED Active Private
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.		 DGOTHFSM 2021/04/15
7249 CAREGIVER RELATIONSHIPS Routine REGISTRATION 2021/04/30 APPROVED Active Supported
The purpose of this Integration Control Registration is
to grant packages the ability to retrieve patient caregiver relationship
information.		 VAFCREL 2022/01/27
7259 AbandonedDGSEC4 routine Routine REGISTRATION 2021/05/10 Withdrawn Private
7266 OEHRM Image Migration - access to file #391.91 File REGISTRATION 2021/06/01 Pending Private 391.91
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.
7276 COMPACT ACT ELIGIBLE Routine REGISTRATION 2021/07/23 Pending Supported
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.		 DGENELA
7277 READ PENSION INFORMATION File REGISTRATION 2021/08/06 APPROVED Active Private 2
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		 2022/03/18
7300 INDIAN SELF IDENTIFICATION CHANGE File REGISTRATION 2021/09/16 APPROVED Active Private 2
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)		 2021/12/08
7316 DGCN(391.91 - GET EDIPI FOR DFN File REGISTRATION 2021/12/16 Withdrawn Private 391.91
Treating Facility List where patients have had
treatment.
7323 VAFCAPI Routine REGISTRATION 2022/01/28 APPROVED Active Private
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.		 VAFCAPI 2022/02/08
7346 VAFCCRNR Routine REGISTRATION 2022/07/22 APPROVED Active Controlled Subscription VAFCCRNR 2022/11/03
7350 DG TEMPORARY ADDRESS UPDATE Routine REGISTRATION 2022/08/18 Pending Supported
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) 		DGENDBS
7354 DG PTF ICD PROCEDURE NOTIFIER Other REGISTRATION 2022/08/31 APPROVED Active Controlled Subscription
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.		 2022/08/31
7360 CERNER CERT and MOCK API Routine REGISTRATION 2022/10/27 APPROVED Active Controlled Subscription
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.		 VAFCCRNR 2022/10/31
7421 DGPROSAD Routine REGISTRATION 2023/04/10 APPROVED Active Controlled Subscription
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.		 DGPROSAD 2023/04/12
7459 Display Service Connected info on ACC Worklists File REGISTRATION 2025/03/24 APPROVED Active Private 2
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.		 2025/03/24
7462 COMPACT ACT Administrative Eligibility Routine REGISTRATION 2024/04/15 APPROVED Active Controlled Subscription
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.		 DGCOMPACTELIG 2024/05/07
7463 COMPACT Act Treatment Related to Flag in PTF Routine REGISTRATION 2024/04/15 APPROVED Active Private
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).		 DGCOMPACT 2024/04/23
7467 DGSEC Routine REGISTRATION 2024/04/19 APPROVED Active Controlled Subscription
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.		 DGSEC 2025/04/09
7470 sens dgsec4 REGISTRATION 2024/05/14 Pending Controlled Subscription
7479 Determine if sensitive record Routine REGISTRATION 2024/06/12 APPROVED Active Controlled Subscription
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.		 DGSEC4 2024/07/01
7480 Audit patient records at selection Routine REGISTRATION 2024/06/12 APPROVED Active Controlled Subscription
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.		 DGAUDIT2 2024/10/24
7484 TRT FOR ACUTE SUICIDAL CRISIS field in PTF File REGISTRATION 2024/08/07 Withdrawn Private 45
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).
7485 PATIENT MOVEMENT POINTER FIELDS File REGISTRATION 2024/08/09 Withdrawn Private 405
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).
7532 WITHDRAWN ICR REGISTRATION 2025/03/31 Withdrawn
7546 READ/WRITE DISCHARGED TO CERNER FIELD File REGISTRATION 2025/04/22 APPROVED Active Private 2 2025/04/23
10035 PATIENT FILE File REGISTRATION 2017/09/13 APPROVED Active Supported 2
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).		 2023/01/25
10036 DGPMLOS Routine REGISTRATION 1994/03/07 APPROVED Active Supported
Obtain length of stay by admission.		 DGPMLOS
10037 DGRPD Routine REGISTRATION 1999/11/16 APPROVED Active Supported
Patient Inquiry.		 DGRPD
10039 WARD LOCATION FILE File REGISTRATION 1994/10/28 APPROVED Active Supported 42 2009/06/29
10061 VADPT Routine REGISTRATION 1994/03/07 APPROVED Active Supported
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.		 VADPT 2024/08/26
10112 VASITE Routine REGISTRATION 1994/03/07 APPROVED Active Supported
See in routine documentation.		 VASITE