All ICR List

Package: Scheduling 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
18 DBIA18 File SCHEDULING 2003/04/03 Retired Private 44
Hospital Location file (44)
19 DBIA19 File SCHEDULING 1990/01/29 APPROVED Active Private 40.7
20 DBIA20 Routine SCHEDULING 1987/05/07 Retired Private SDACS
22 DBIA22 File SCHEDULING 2003/04/03 Retired Private 44
24 DBIA24 File SCHEDULING 2003/04/03 Retired Private 44
83 DBIA83 Routine SCHEDULING 1991/07/09 Retired Private
Lab uses suported call EN3^SDACS for adding stop codes. 		SDACS
84 DBIA84 Routine SCHEDULING 1991/07/09 Retired Private
Pharmacy uses EN3^SDACS for adding stop codes.		 SDACS
86 DBIA86 Routine SCHEDULING 2003/04/03 Retired Private
Create Requests for Records and Pull lists from clinic
appointments:
Record Tracking queues a task which parses the scheduling global for Record
Tracking 'Borrowers' ie 'Clinics' which have appointments in a date range and
creates Requested Records and Pull list entries for patients with
appointments.
IF there is a clinic appointment: An entry is made in the Pull list file
#194.2 with a name derived from the clinic name
SC(1,0)=Dr Jones Clinic^
RTV(194.2,n)=Dr Jones Clinic [04/01/91]^
An entry is made in the Requested Records file #190.1 ^RTV(190.1,n)
After the entry is added to the Requested Records file #190.1 an entry is made
in Parent Record Request field of the Patient subfield of the Hospital
Location file #44, ^SC(n,"S",,,,"RTR")=n^, by a call from CREATE+11^RTQ2 to
RTSET^SDUTL		 SDUTL
93 DBIA93-A File SCHEDULING 2005/02/17 APPROVED Active Controlled Subscription 44
This ICR allows direct global read and read with
fileman access to the Stop Code Number (#8), Name (#.01), and Type (#2)
fields. Name field direct read access is used to determine if a value exists
and the Type field direct read access is used to determine the Hospital
Location type before it can execute another task in TIUSRVP.
Revision History:
- 12/3/24: A previously missing Description was added to reflect the new
changes.
110 DBIA110-A Other SCHEDULING 2003/04/03 Retired Private
The following option will be placed on the QUIC menu
structure:
SDM - Make Appointment
112 DBIA112 Routine SCHEDULING 2003/04/03 Retired Private
Display a patient's eligibility and disabilities the
same way MAS does on the routing sheet..
The subroutine DIS^SDROUT2 make several global references:
^DPT(DFN,.372,
^DG(391,
^DIC(31,		 SDROUT2
131 DBIA131-A File SCHEDULING 1991/12/04 APPROVED Active Private 2
'Status of the clinic appointment' field in ^DPT('S'
node will be used to determine appointment status. If the status of the
appointment is active and not an inpatient visit, it will be counted as an
outpatient visit for social work totals.
179 DBIA179 Routine SCHEDULING 1992/06/18 Retired Private
Radiology uses supported call EN3^SDACS for adding stop
codes. 		SDACS
188 DBIA188-A Routine SCHEDULING 2003/04/03 Retired Private
STATUS^SDAMBAE4-- Incorporated current Ambulatory Procedure active status into
a CPT status function that also includes BASC and AMA status		 SDAMBAE4
195 DBIA195 Routine SCHEDULING 2003/04/03 Retired Private
Display a patient's eligibility and disabilities the
same way MAS does on the routing sheet.
The subroutine DIS^SPROUT2 makes several global references:
^DPT(DFN,.372, ^DG(391, ^DIC(31,		 SDROUT2
204 DBIA204 File SCHEDULING 2003/04/03 Retired Private 44
Read Only access to the Hospital Location File (#44),
Field 1900 (Appointment), to read scheduling information from the global
^SC(D0,S,D1,1,D2,0). The information read will be stored in a Prosthetics
package file and used in the quarterly compilation of AMIS reports.
Read access to the ^SC(D0,"I") node to check the inactivate date (field #2505)
and the re-activate date (field #2506) to allow Prosthetics to Select an
active Clinic when entering Prosthetics Clinics in the Prosthetics Site
Parameter File.
Until V. 6.0 of Registration.
225 DBIA225-A Other SCHEDULING 2003/04/03 Retired Private
Prosthetics has permission from MAS to call the
following:
Addition of the Prosthetics Protocol RMPR SCHED EVENT as an item on the SDAM
APPOINTMENTS EVENTS Protocol in File 101. Below is a display of the RMPR
SCHED EVENT protocol:
RMPR SCH EVENT ITEM TEXT: Prosthetics Scheduling file update TYPE: action
PACKAGE: PROSTHETICS
Updates the Prosthetics Scheduling Events file whenever an appointment is
created or updated. The Clinic must be in the Prosthetics Site Parameter file
before the Prosthetics files can be updated by MAS.
ENTRY ACTION: D ^RMPRSC
SDAM APPOINTMENT EVENTS ITEM TEXT: Appointment Event Driver
TYPE: extended action CREATOR: POSTMASTER
This extended action contains all the actions that need to be performed when
an action is taken upon an appointment, such as checking in.
ITEM: SDAM LATE ENTRY SEQUENCE: 2 ITEM: IBACM OP LINK
SEQUENCE: 1 ITEM: RMPR SCH EVENT
SEQUENCE: 3 TIMESTAME: 55576,33406
261 DBIA261-A Routine SCHEDULING 2003/04/03 Retired Private
The option HBHC Appointment uses the MAS routine ^SDM
as the Run Routine, and employs SDM^SDKILL in the exit action.
Select OPTION to edit: HBHC APPOINTMENT Make Appointment NAME: HBHC
APPOINTMENT// MENU TEXT: Make Appointment// PACKAGE: HOSPITAL BASED HOME
CARE// DESCRIPTION:
1>This option utilizes the MAS Scheduling Option, Make Appointment [SDM],
2>for entry of appointment data. The Exit Action on this option runs a
3>routine that creates records in the HBHC Visit File (HBHC(632)) using
4>the appointment data entered. Only data for clinics contained in the
5>HBHC Clinic File (HBHC(631.6)) will be added to the HBHC Visit File.
EDIT Option: TYPE: run routine// ENTRY ACTION: D:$T(HDLKILL^SDAMEVT)]""
HDLKILL^SDAMEVT EXIT ACTION: D SDM^SDKILL K ORACTION,ORVP,XQORQUIT W
!!,"Adding entries
to the visit file..." D WAIT^DICD,^HBHCAPPT
D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT
Replace ROUTINE: SDM//		 SDM
265 DBIA265 File SCHEDULING 1993/08/17 Retired Private
Clinical Monitoring System and MAS for read access to the following fields and
cross-references.
FIELDS:
ELEMENT FILE
DD LEVEL FIELD # DD NUMBER
APPOINTMENT DATE/TIME PATIENT
1 1900 2
2 .001 2.98
APPOINTMENT STATUS PATIENT
1 1900 2
2 3 2.98
PURPOSE OF VISIT PATIENT
1 1900 2
2 9 2.98
APPOINTMENT TYPE PATIENT
1 1900 2
2 9.5 2.98
APPT. CANCELLATION REASON PATIENT
1 1900 2
2 16 2.98
CLINIC PATIENT
1 1900 2
2 .01 2.98
(The above fields related to field 1900 will be eliminated with the scheduling
redesign.)
COVERED BY HEALTH INSURANCE? PATIENT
1 .3192 2
DATE OF DEATH PATIENT
1 .351 2
DISPOSITION PATIENT
1 1000 2
2 6 2.101
LOG IN DATE/TIME PATIENT
1 1000 2
2 .01 2.101
LOG IN STATUS PATIENT
1 1000 2
2 1 2.101
LOG OUT DATE/TIME PATIENT
1 1000 2
2 5 2.101
REASON FOR LATE DISPOSITION PATIENT
1 1000 2
2 8 2.101
SERVICE CONNECTED PERCENTAGE PATIENT
1 .302 2
SERVICE CONNECTED? PATIENT
1 .301 2
SPINAL CORD INJURY PATIENT
1 57.4 2
TYPE OF BENEFIT APPLIED FOR PATIENT
1 1000 2
2 2 2.101
TYPE OF CARE APPLIED FOR PATIENT
1 1000 2
2 2.1 2.101
TYPE OF MOVEMENT PATIENT MOVEMENT
1 .04 405
WARD LOCATION PATIENT MOVEMENT
1 .06 405
TRANSACTION TYPE PATIENT MOVEMENT
1 .02 405
ROOM-BED PATIENT MOVEMENT
1 .07 405
ADMITTED FOR SC CONDITION? PATIENT MOVEMENT
1 .11 405
ADMITTING REGULATION PATIENT MOVEMENT
1 .12 405
ATTENDING PHYSICIAN PATIENT MOVEMENT
1 .19 405
DIAGNOSIS [SHORT] PATIENT MOVEMENT
1 .1 405
FACILITY TREATING SPECIALTY PATIENT MOVEMENT
1 .09 405
MAS MOVEMENT TYPE PATIENT MOVEMENT
1 .18 405
MOVEMENT DATE/TIME PATIENT MOVEMENT
1 .01 405
PRIMARY CARE PHYSICIAN PATIENT MOVEMENT
1 .08 405
PATIENT PTF
1 .01 45
PTF ADMISSION DATE PTF
1 2 45
PTF DISCHARGE DATE PTF
1 70 45
PTF DISCHARGE SPECIALTY PTF
1 71 45
PTF DRG PTF
1 9 45
PTF DXLS PTF
1 79 45
PTF ICD 10 PTF
1 79.24 45
PTF ICD 2 PTF
1 79.16 45
PTF ICD 3 PTF
1 79.17 45
PTF ICD 4 PTF
1 79.18 45
PTF ICD 5 PTF
1 79.19 45
PTF ICD 6 PTF
1 79.201 45
PTF ICD 7 PTF
1 79.21 45
PTF ICD 8 PTF
1 79.22 45
PTF ICD 9 PTF
1 79.23 45
PTF PROCEDURE 1 PTF
1 45.01 45
PTF PROCEDURE 2 PTF
1 45.02 45
PTF PROCEDURE 3 PTF
1 45.03 45
PTF PROCEDURE 4 PTF
1 45.04 45
PTF PROCEDURE 5 PTF
1 45.05 45
PTF TYPE OF DISPOSITION PTF
1 72 45
PTF WARD AT DISCHARGE PTF
1 2.2 45
SURGERY/PROCEDURE DATE PTF
1 401 45
2 .01 45.01
OPERATION CODE 1 PTF
1 401 45
2 8 45.01
OPERATION CODE 2 PTF
1 401 45
2 9 45.01
OPERATION CODE 3 PTF
1 401 45
2 10 45.01
OPERATION CODE 4 PTF
1 401 45
2 11 45.01
OPERATION CODE 5 PTF
1 401 45
2 12 45.01
MAS MOVEMENT TRANSACTION TYPE MAS MOVEMENT TRANSACTION TYPE
1 .01 405.3
NAME DISPOSITION
1 .01 37
NAME FACILITY TREATING SPECIALTY
1 .01 45.7
FACILITY TREATING SPECIALTY SERVICE
1 2 45.7
NAME MAS MOVEMENTT TYPE
1 .01 405.2
NAME APPOINTMENT TYPE
1 .01 409.1
CODE NUMBER ICD DIAGNOSIS
1 .01 80
CODE NUMBER ICD OPERATION/PROCEDURE
1 .01 80.1
PATIENT HOSPITAL LOCATION
1 1900 44
2 2 44.001
3 .01 44.003
CROSS REFERENCES:
DATE OF BIRTH PATIENT
XREF: ADOB
SEX PATIENT
XREF: ASX
DATE OF ENROLLMENT PATIENT
XREF: AEB
DATE OF DEATH PATIENT
XREF: AEXP1
LOG IN DATE/TIME PATIENT
XREF: ADIS
DATA GLOBAL HOSPITAL LOCATION
XREF: ^SC(D0,"S",D1,1,D2,...
^ ^
| |-- PATIENT
|-- APPOINTMENT
CLOSE OUT DATE PTF CLOSE OUT
XREF: AC
DATA GLOBAL PTF
XREF: ^DGPT(D0,"S",D1,...
^
|-- SURGERY/PROCEDURE DATE
266 LIST TEMPLATE FILE Other SCHEDULING 1993/08/25 APPROVED Active Supported 409.61
The List Template file 409.61 may be populated with
entries that are namespaced (following the same principles as with the Option
file). Refer to List Manager documentation for current export utilities.
Entries should not be made to this file other than through VA FileMan and the
export utilities.
335 DBIA335-A File SCHEDULING 2003/04/03 Retired Private 44
Pharmacy Prescription Practices Prototype is granted
this DBIA with Scheduling to make the following calls:
I. Direct read access to the SC global.
A. ^SC("AC","C",CLINIC) -> Used to obtain a list of all
clinics currently in the file.
B. ^SC(CLINIC,"S",DATE) -> Used to check for patients
scheduled for clinic on a specified date.
341 DBIA341 Routine SCHEDULING 2003/06/25 APPROVED Active Private
The Problem List Application is granted permission from
Scheduling to use the entry point "DIS^SDROUT2". This will display a
patient's service connected data for the clinician.
DIS^SDROUT2
Input: DFN
Returned: Display of patient's service-connected data. 		SDROUT2
355 DBIA355 File SCHEDULING 1994/03/03 APPROVED Active Private 2
Read access to the following fields and
cross-references:
FIELDS:
ELEMENT FILE
DD LEVEL FIELD # DD NUMBER
**APPOINTMENT DATE/TIME PATIENT
1 1900 2
2 .001 2.98
**APPOINTMENT STATUS PATIENT
1 1900 2
2 3 2.98
**APPOINTMENT TYPE PATIENT
1 1900 2
2 9.5 2.98
**APPT. CANCELLATION REASON PATIENT
1 1900 2
2 16 2.98
**CLINIC PATIENT
1 1900 2
2 .01 2.98
(The above fields related to field 1900 will be eliminated with the scheduling
redesign.) **DATE OF ENROLLMENT PATIENT
XREF: AEB
356 DBIA356 File SCHEDULING 2003/04/03 Retired Private 44
Read access to the following fields and
cross-references.
FIELDS:
ELEMENT FILE
DD LEVEL FIELD # DD NUMBER
**PATIENT HOSPITAL LOCATION
1 1900 44
2 2 44.001
3 .01 44.003
**DATA GLOBAL HOSPITAL LOCATION
XREF: ^SC(D0,"S",D1,1,D2,...
^ ^
| |-- PATIENT
|-- APPOINTMENT
364 DBIA364 File SCHEDULING 2003/04/03 Retired Private 409.1
Read access to the following fields:
FIELDS:
ELEMENT FILE
DD LEVEL FIELD # DD NUMBER
NAME APPOINTMENT TYPE
1 .01 409.1
397 DBIA397 File SCHEDULING 1994/04/04 APPROVED Active Private 409.95
Request to export the following Scheduling files with the release
of Integrated Billing v2.0:
#409.95 PRINT MANAGER CLINIC SETUP
Also request read and write access for all fields in these files.
These files are used by the Print Manager to determine which
forms should be printed for each clinic.
398 DBIA398 File SCHEDULING 1994/04/04 APPROVED Active Private 409.96
Request to export the following Scheduling files with the release
of Integrated Billing v2.0:
#409.96 PRINT MANAGER DIVISION SETUP
Also request read and write access for all fields in these files.
These files are used by the Print Manager to determine which
forms should be printed for each clinic.
399 DBIA399 File SCHEDULING 1994/04/04 APPROVED Active Private 2
400 DBIA400 File SCHEDULING 1994/04/04 APPROVED Active Private 40.7
401 DBIA401 File SCHEDULING 2003/04/03 Retired Private 44
It is understood that these references will need to be
changed when Scheduling's new APIs are available.
402 DBIA402 File SCHEDULING 1994/04/04 Under Revision Controlled Subscription 409.68
This pointer is needed to retrieve data from this file
when a claim is being generated.
403 DBIA403 Routine SCHEDULING 2003/04/03 Retired Private SDCO3
404 DBIA404 Routine SCHEDULING 2003/04/03 Retired Private SDCO4
405 DBIA405 Routine SCHEDULING 2003/04/03 Retired Controlled Subscription SDROUT1
406 DBIA406 Routine SCHEDULING 2003/06/30 APPROVED Active Controlled Subscription SDCO21
407 DBIA407 Routine SCHEDULING 1994/04/04 APPROVED Active Private SDCOU2 2007/03/15
408 DBIA408 File SCHEDULING 1994/04/04 Retired Private 409.5
It is understood that these references will need to be
changed when Scheduling's new APIs are available.
409 DBIA409 File SCHEDULING 1994/04/04 APPROVED Active Controlled Subscription 409.42
410 DBIA410 File SCHEDULING 1994/04/04 APPROVED Active Private 409.72
411 DBIA411 File SCHEDULING 1994/04/04 Retired Private 409.43
450 DBIA450 Other SCHEDULING 1995/05/09 Retired Private
The CPT package would like to make the following
integration request with the Scheduling package:
Request to export the following scheduling routine
change to Scheduling v5.3 with the CPT annual release:
Routine Reason
-----------------------------------------------------------------------
SDAMBAE3 Update the effective date reference for current
release.
451 DBIA451 File SCHEDULING 1994/04/12 Retired Private 409.71
Reason: To populate the Ambulatory Procedure file with
all the CPT codes.
452 DBIA452 File SCHEDULING 1994/04/12 APPROVED Active Private 409.72
Reason: To populate the Ambulatory Procedure Time
Sensitive file with current CPT codes.
479 DBIA479 File SCHEDULING 1994/05/02 APPROVED Active Private 40.7
Visit Tracking (PIMS/MAS)
Entries used by Visit Tracking are passed by package developers
making calls to the Visit Tracking package.
The Visit Tracking package requests permission to read
and point to the following file:
Visit File Fields
-----------------
#08 Clinic Pointer to the Clinic Stop File #40.7
481 DBIA481 File SCHEDULING 2003/04/03 Retired Private 44
Visit Tracking (PIMS/MAS)
Entries used by Visit Tracking are passed by package developers
making calls to the Visit Tracking package.
The Visit Tracking package requests permission to read
and point to the following file:
Visit File Field
----------------
#22 Hospital Location Pointer to the Hospital Location File #44
Visit Tracking code checks the following fields
in the Hospital Location file:
Field / Name
-----------------------
2 Type
3.5 Division
8 Stop Code
1916 Principal Clinic
493 DBIA493 File SCHEDULING 2003/04/03 Retired Controlled Subscription 40.9
The patient oriented extracts in DSS distinguish
between inpatients and outpatients. To make this distinction, a field in the
extract log points to the LOCATION TYPE file (40.9).
515 DBIA31-C File SCHEDULING 1989/11/14 APPROVED Active Private 44
518 DBIA36-B File SCHEDULING 2003/04/03 Retired Private 44
^SC( Used to get patient variables
556 DBIA93-B File SCHEDULING 1991/09/11 Retired Controlled Subscription 409.5
557 DBIA93-C File SCHEDULING 1991/09/11 APPROVED Active Controlled Subscription 40.7
580 DBIA110-B File SCHEDULING 2005/06/20 Retired Private 40.7
605 DBIA131-B File SCHEDULING 2003/04/03 Retired Private 44
Read access to File 44 field .01 and Appointment
sub-fields 'Clinic Stop Code' and 'Patient Name'
659 DBIA188-B Routine SCHEDULING 2003/04/03 Retired Private
If outpatient, get appointment status		 SDAM1
660 DBIA188-C Routine SCHEDULING 1992/07/22 Retired Private SDUL
661 DBIA188-D Routine SCHEDULING 1992/07/22 Retired Private SDUL1
662 DBIA188-E Routine SCHEDULING 1992/07/22 Retired Private SDUL2
663 DBIA188-F Routine SCHEDULING 2003/04/03 Retired Private VADPT
665 DBIA188-H File SCHEDULING 2003/04/03 Retired Private 44
Used in finding and printing Check-off Sheets for
patient appointments, the user is allowed to select all Check-off Sheets for a
particular clinic
.01 NAME -- Used in searching, sorting, and printing the Clinic CPT
Usage' report
2 TYPE -- Used in searching, sorting, and printing the'Clinic CPT
Usage' report
15 MEDICAL CENTER DIVISION -- Used in BASC charge calculation on
the Check-off Sheet and the 'Clinic CPT Usage' report
25 PROCEDURE CHECK-OFF SHEET -- New field, associates a clinic and
a Check-off Sheet
1900 APPOINTMENT SUBFILE -- Printed on a patients Check-off Sheet
.01 APPOINTMENT DATE/TIME
1 PATIENT
X-REF: AF
666 DBIA188-I File SCHEDULING 2003/04/03 Retired Private 409.1
SD(409.1 APPOINTMENT TYPE FILE
.01 NAME
Printed on a patients Check-off Sheet
667 DBIA188-J File SCHEDULING 1992/07/22 Retired Private 409.5
SDV SCHEDULING VISITS-- Used to sort, search and
print the 'Unbilled BASC for Insured Patient Appointment' and the 'Clinic CPT
Usage' reports.
2 PATIENT
21 PROCEDURE 1
22 PROCEDURE 2
23 PROCEDURE 3
24 PROCEDURE 4
25 PROCEDURE 5
X-REF: AP
668 DBIA188-K File SCHEDULING 1992/07/22 APPROVED Active Private 409.71
SD(409.71 AMBULATORY PROCEDURE--Pointed to by
PROCEDURE field in the BILLABLE AMBULATORY SURGICAL CODE file (350.4), pointed
to by PROCEDURE field in the AMBULATORY SURG.CHECK-OFF SHEET PRINT FIELDS file
(350.71)
409.71 SD(409.71 AMBULATORY PROCEDURE
.01 CODE-- When BASC codes are added to 350.4 the CPT is added to
409.71 if its not already there
[SD-AMB-PROC-EDIT] Edit template used if new entry is added to file
409.71 during interactive edit of file 350.4
100 SYNONYMS SUBFILE (ALL)
669 DBIA188-L File SCHEDULING 1992/07/22 APPROVED Active Private 40.7
^DIC(40.7,Clinic Stop)-- ^IBOVOP1: get clinic name -
0;1 NAME
670 DBIA188-M File SCHEDULING 2003/04/03 Retired Private 44
^SC(HOSPITAL LOCATION-- ^IBOVOP1: scan clinic visits
^SDV(Scheduling Visits file) ^IBECEA3: check stop codes for a c&p
- "CS" CLINIC STOP
- "B" xref
- 0;5 APPOINTMENT TYPE
- "ADT" appointment date ^IBECEA3 ^SD(409.1,APPOINTMENT TYPE--
^IBOVOP1: get appointment type name
SC HOSPITAL LOCATION FILE-- Pointer to the Check-off sheet associated
with this clinic
25 PROCEDURE CHECK-OFF SHEET
x-ref: AF
671 DBIA188-N Other SCHEDULING 2003/04/03 Retired Private
IB Templates that look at MAS Files
IB CPT RG DISPLAY on file 409.71-- Displays a procedures billing fields:
.01 CODE history
.015 SHORT NAME
205 CURRENT ACTIVE STATUS
735 DBIA244-I File SCHEDULING 2003/04/03 Retired Private 44
^SC( 0;1 Hopital Location name
^SC("C"
736 DBIA244-J File SCHEDULING 2003/04/03 Retired Controlled Subscription 409.1
^SD(409.1 0;1 Appointment Type name
737 DBIA244-K File SCHEDULING 1993/06/15 Retired Private 409.5
^SDV( 0 Checks for the existence
of
739 DBIA244-M Routine SCHEDULING 2003/04/03 Retired Private SDM
747 DBIA261-B Routine SCHEDULING 1993/08/09 Retired Private
The option HBHC Appointment uses the MAS routine ^SDM
as the Run Routine, and employs SDM^SDKILL in the exit action. The option
HBHC Cancel Appointment uses ^SDCNP as the Run Routine, and the SDCNP^SDKILL
in the Exit Action.
Select OPTION to edit: HBHC APPOINTMENT Make Appointment NAME: HBHC
APPOINTMENT// MENU TEXT: Make Appointment// PACKAGE: HOSPITAL BASED HOME
CARE// DESCRIPTION:
1>This option utilizes the MAS Scheduling Option, Make Appointment [SDM],
2>for entry of appointment data. The Exit Action on this option runs a
3>routine that creates records in the HBHC Visit File (HBHC(632)) using
4>the appointment data entered. Only data for clinics contained in the
5>HBHC Clinic File (HBHC(631.6)) will be added to the HBHC Visit File.
EDIT Option: TYPE: run routine// ENTRY ACTION: D:$T(HDLKILL^SDAMEVT)]""
HDLKILL^SDAMEVT EXIT ACTION: D SDM^SDKILL K ORACTION,ORVP,XQORQUIT W
!!,"Adding entries
to the visit file..." D WAIT^DICD,^HBHCAPPT
D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT
Replace ROUTINE: SDM//
Select OPTION to edit: HBHC CANCEL APPOINTMENT Cancel Appointment
NAME: HBHC CANCEL APPOINTMENT Replace MENU TEXT: Cancel Appointment//
PACKAGE: HOSPITAL BASED HOME CARE DESCRIPTION:
1>This option utilizes the MAS Scheduling Option, Cancel Appointment
2>[SD CANCEL APPOINTMENT], for cancelling appointments. The Exit Action
3>on this option runs a routine that updates records in the HBHC Visit
4>File (HBHC(632)) using the cancellation data entered. EDIT Option:
TYPE: run routine// ENTRY ACTION: D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT
EXIT ACTION: D SDCNP^SDKILL W !!,"Updating entries in the visit
file..." D WAIT^DICD,^HBHCCAN D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT
Replace ROUTINE: SDCNP//		 SDKILL
748 DBIA261-C Routine SCHEDULING 1993/08/09 Retired Private
The option HBHC Cancel Appointment uses ^SDCNP as the
Run Routine, and the SDCNP^SDKILL in the Exit Action.
Select OPTION to edit: HBHC CANCEL APPOINTMENT Cancel Appointment
NAME: HBHC CANCEL APPOINTMENT Replace MENU TEXT: Cancel Appointment//
PACKAGE: HOSPITAL BASED HOME CARE DESCRIPTION:
1>This option utilizes the MAS Scheduling Option, Cancel Appointment
2>[SD CANCEL APPOINTMENT], for cancelling appointments. The Exit Action
3>on this option runs a routine that updates records in the HBHC Visit
4>File (HBHC(632)) using the cancellation data entered. EDIT Option:
TYPE: run routine// ENTRY ACTION: D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT
EXIT ACTION: D SDCNP^SDKILL W !!,"Updating entries in the visit
file..." D WAIT^DICD,^HBHCCAN D:$T(HDLKILL^SDAMEVT)]"" HDLKILL^SDAMEVT
Replace ROUTINE: SDCNP//		 SDCNP
749 DBIA261-D File SCHEDULING 1993/08/09 Retired Private 44
In routine HBHCAPPT
$O(^SC(HBHCCLN,"S",HBHCAPDT))
$O(^SC(HBHCCLN,"S",HBHCAPDT,1,HBHCSCN))
792 DBIA277-F File SCHEDULING 1993/09/13 APPROVED Active Controlled Subscription 31
File #31 - Disability Condition
Field #.01 - Name - ^DIC(31,D0,0) piece 1
837 DBIA325-C File SCHEDULING 1993/12/23 APPROVED Active Private 2
Globals -- For the APPOINTMENT (#1900) field (sub-file #2.98)
of the PATIENT (#2) file:
Zeroth node (^DPT(DFN,"S",Visit Date/Time,0)):
Field Name/#/Piece on node Reason Needed
============================ =============
APPOINTMENT DATE/TIME (#.001) (ien) Determine the visit date
CLINIC (#.01) (1) Need clinic to see of it
is non-count
STATUS (#3) (2) Need to see if visit was
cancelled
APPOINTMENT TYPE (#9.5) (16) Need to see if Appointment
Type is billable
OUTPATIENT ENCOUNTER (#21) (20) Need pointer to the
Outpatient Encounter (if
it exists) to see if visit
was related to claimed
exposures
For the DISPOSITION LOG-IN DATE/TIME (#1000) field
(sub-file #2.101) of the PATIENT (#2) file:
Zeroth node (^DPT(DFN,"DIS",Inv Log-In Date/Time,0)):
Field Name/#/Piece on node Reason Needed
============================ =============
STATUS (#1) (2) Make sure registration is
not Application w/o Exam
OUTPATIENT ENCOUNTER (#18) (18) Need pointer to the
Outpatient Encounter (if
it exists) to see if visit
was related to claimed
exposures
838 DBIA325-D File SCHEDULING 1993/12/23 Retired Private 409.5
For SCHEDULING VISITS (#409.5) file:
"ADT" cross reference (^SDV("ADT",DFN,Visit Date)=ptr):
This cross-reference is used to find all of a patient's stops
on a specific date.
CLINIC STOP CODE (#10) field (sub-file #409.51):
Zeroth node (^SDV(ptr,"CS",ien,0)):
Field Name/#/Piece on node Reason Needed
============================ =============
ASSOCIATED CLINIC (#3) (3) Need clinic to see of it
is non-count
APPOINTMENT TYPE (#5) (5) Need to see if Appointment
Type is billable
OUTPATIENT ENCOUNTER (#8) (8) Need pointer to the
Outpatient Encounter (if
it exists) to see if visit
was related to claimed
exposures
839 DBIA325-E File SCHEDULING 1993/12/23 APPROVED Active Private 209.42
For the OUTPATIENT CLASSIFICATION (#409.42) file:
Zeroth node (^SDD(409.42,ien,0)):
Field Name/#/Piece on node Reason Needed
============================ =============
TYPE (#.01) (1) Determine whether question
relates to AO, SC, IR, or
EC
VALUE (#.03) (3) Determine whether care was
related to the claimed
exposure.
"OE" cross reference (^SDD(409.42,"OE",ptr to #409.68,ien)):
This cross-reference is used to find all classification answers
for a specific outpatient encounter.
Please note that all of these references may be found in the
routine IVMUFNC2.
845 DBIA335-B File SCHEDULING 1994/01/18 APPROVED Active Private 2
Pharmacy Prescription Practices Prototype is granted
this DBIA with Scheduling to make the following calls:
C. ^DPT(DFN,"S",DATE,0) -> Used to verify that a clinic
appointment has not been canceled.
908 DBIA908 File SCHEDULING 2003/04/03 Retired Controlled Subscription 44
Read only access for the ^SC global.
Read ^SC(n,0) to obtain Hospital Location name, abbreviation and
Division.
Read ^SC(n,42) to obtain ward location file pointer to obtain field
#.017 Specialty in the Ward Location file #42.
Read ^SC("B", and ^SC("C", cross references to get patient location
internal entry #: $O(^SC("B",X,0)) and $O(^SC("C",X,0)).
Read access to the ^SC(D0,"I") node to obtain inactivate date
(field # 2505) and re-activate date (field # 2506).
Read only access to ^SC(D0,"S",D1,1,D2,0) to access patients by
clinic location and clinic date to print lab report.
Read only access to ^SC(D0,"S",DATE) used to check if a clinic
meets on a specified date.
923 DBIA923 File SCHEDULING 1994/07/28 APPROVED Active Private 40.7
The following fields are accessed in a read-only
manner:
^DIC( 40.7 STOP CODE file
1 AMIS REPORTING STOP CODE
In routines LRCAPPH line LRCAPPH+8
SDC S SDC=$S($P(^("NITE"),U,3):$G(^DIC(40.7,+$P(^LAB(69.9,1,"NITE"),
U,3),0)),1:"") S LRSDC=$S($P(SDC,U,2):+$P(SDC,U,2),1:108)
LRSTOPC line LRSTOPC+3
S LRSDC=$S(+$P($G(^DIC(40.7,+$P($G(^LAB(69.9,1,"NITE")),U,3),0)),U,2):
$P(^(0),U,2),1:108),CNT=0,LREND=0
Routine LRSTOPC manually records clinic stop codes for Lab. Routine LRCAPPH
automatically records clinic stop codes for Lab.
964 DBIA964 File SCHEDULING 2004/10/26 APPROVED Active Private 44
The IVM package requests direct access to the field
NON-COUNT CLINIC? (#2502) in the HOSPITAL LOCATION (#44) file. The field is
used to determine whether an outpatient encounter in a specific clinic is
potentially billable for Means Test billing.
1009 DBIA110-C File SCHEDULING 1994/09/27 Retired Private 409.5
The following references will be made from the ^QIP1*
routines which, while belonging to the QIP namespace, will be maintained by
the PIMS developers. Coordination of release and patches will be through the
QIP custodial ISC.
1012 DBIA110-D File SCHEDULING 2005/06/20 Retired Private 2
Routine QIP1NS will use the following field to
determine to percentage of no-show visits versus the total number of visits:
1015 DBIA1015 Routine SCHEDULING 2003/04/03 APPROVED Active Private
Integrated Billing requests use of the function
$$EXOE^SDCOU2. The purpose of the function is to determine whether the
classification questions should be asked for a specific outpatient encounter.
IB needs to know whether the classification questions were not asked of
patients who have claimed exposures, so that a message may be sent to the
Category C Billing mailgroup to alert MCCR personnel to manually review
whether that particular encounter was actually related to the veteran's
claimed exposures.		 SDCOU2 2007/03/15
1024 Health Summary to File 40.7 File SCHEDULING 1994/10/17 APPROVED Active Controlled Subscription 40.7
Health Summary accesses file ^DIC(40.7, to display the
Name of the Clinic Stop in one of its components.
1025 Health Summary access to 409.5 File SCHEDULING 1994/10/17 Retired Controlled Subscription 409.5
Health Summary accesses file 409.5, Scheduling Visits
file to display the Associated Clinic and Appointment Type in one of its
components, Clinic Past Visits (CVP).
1026 Health Summary access to file 409.1 File SCHEDULING 1994/10/17 Retired Controlled Subscription 409.1
Health Summary accesses file 409.1, Appointment Type
File, to display the name of the Appointment Type in one of its components,
Clinic Past Visits (CVP).
1101 Patient File Scheduling Node File SCHEDULING 2003/04/03 Retired Controlled Subscription
AMIE references the described fields on the 'S' Node of the Patient file to
implement C&P appointment linking for release with V2.7.
1102 Hospital Location File Scheduling Node File SCHEDULING 2003/04/03 Retired Private
AMIE references the described fields on the 'S' Node of the Hospital Location
file to implement C&P appointment linking for release with V2.7.
1103 AMIE use of SDAM1 Routine SCHEDULING 2003/04/03 Retired Private
AMIE calls $$STATUS^SDAM1 to retrieve for output the status of a given
appointment. 		SDAM1
1109 Use of Cross References File SCHEDULING 1995/01/26 Retired Private 409.5
Read access to the following cross references is being
requested. These cross references will be used to count the clininc stops and
the stop codes for a particular patient. The AMIE code will $O through these
structures.
^SDV("ADT"
^SDV("C"
1122 STOP CODES File SCHEDULING 1995/01/27 Retired Private 409.5
Read access is being requested to loop through the 'CS'
node of the Scheduling Visits file. The AMIE software will $O through this
node collecting the stop codes. The stop codes or any pointers will not be
stored in the AMIE database. The 'CS' node is the subfile that contains the
list of stop codes. The node looks like ^SDV(DATE,"CS",..
1163 DBIA1161-C File SCHEDULING 1995/03/14 APPROVED Active Private 40.7
Convert Speciality code to its text equivalent
1252 PRIMARY CARE INPUT AND OUTPUT API CALLS Routine SCHEDULING 1995/06/20 APPROVED Active Supported
SDUTL3 contains 2 input APIs and 3 output APIs which
allow enter of/return of the CURRENT PC PRACTITIONER and CURRENT PC TEAM. The
three output APIs will continue to be supported. The two input APIs will be
supported as long as the two fields exist in the patient file. The approximate
time for deletion of these fields is March 1 2000.		 SDUTL3
1295 DBIA 1295 HOSPITAL LOCATION File SCHEDULING 2003/04/03 APPROVED Active Private 44
The PCE package is requesting to look at and extract
data from the HOSPITAL LOCATION file (# 44).		 2024/12/20
1300 DBIA1300-A SDCO21 Routine SCHEDULING 2004/07/19 APPROVED Active Private
The Patient Care Encounter Developers would like to
request private permission to call the following entry points in routine
SDCO21 with the purpose of obtaining outpatient classification requirements.
IA #1301 is also associated with this request.		 SDCO21
1301 DBIA1300-B PATIENT File SCHEDULING 1995/08/17 APPROVED Active Controlled Subscription 2
Patient Care Encounter would like to request to
directly read the following fields in the PATIENT file (# 2). Our goal is to
reach the pointer value of the OUTPATIENT ENCOUNTER file (# 409.68)
1304 SDAM Routine SCHEDULING 2003/04/03 Retired Private
The PCE developers request the following DBIA with the
Scheduling developers. We are aware that these are not publicly supported
calls and request only PRIVATE USE BY PCE.
LIST^SDAM
All calls assume you are in a List Manager(LM) environment, so appropriate LM
variables have been initialized.		 SDAM
1305 SDAMBAE6 Routine SCHEDULING 2003/04/03 Retired Private
The Patient Care Encounter Developers request an IA to
call the following API.
FREE^SDAMBAE6
This API is called from an action protocol in the PCE's user interface which
allows a user to create a stand alone stop code whithout lieaving PCE's
Interface. This is so the user can get their workload credit and enter
billable data. If they were to enter this data into PCE, the data would not
get to the Scheduling package if the visit cannot be associated with the
appointment.		 SDAMBAE6
1317 SDAM1 Routine SCHEDULING 2003/04/03 Retired Private
The PCE developers request the following DBIA with the
Scheduling developers. We are aware that these are not publicly supported
calls and request only PRIVATE USE BY PCE.
BLD^SDAM1
This call assumes you are in a List Manager(LM) environment, so appropriate LM
variables have been initialized. 		SDAM1
1318 SDAM3 Routine SCHEDULING 2003/04/03 Retired Private
The PCE developers request the following DBIA with the
Scheduling developers. We are aware that these are not publicly supported
calls and request only PRIVATE USE BY PCE.
BLD^SDAM3		 SDAM3
1319 SDAMEP Routine SCHEDULING 2003/04/03 Retired Private
The PCE developers request the following DBIA with the
Scheduling developers. We are aware that these are not publicly supported
calls and request only PRIVATE USE BY PCE.
EN^SDAMEP 		SDAMEP
1320 SDAM APPOINTMENT EVENTS Other SCHEDULING 2004/01/08 APPROVED Active Controlled Subscription
This is the event that is invoked when an action is
taken upon an appointment, such as check in.
^TMP("SDEVT",$J,SDHDL,SDPROC,"SDOE",SDOE,0,"AFTER") = Zero node of encounter
after change
SDHDL = Handle (can get more than one at a time)
SDPROC = Originating process
1 = Appointment
2 = Add/Edit
3 = Disposition
4 = Credit Stop (ignore these)
SDOE = Pointer to encounter
1321 SCCV ENCOUNTER CONVERSION EVENTS Other SCHEDULING 2003/04/03 Withdrawn Controlled Subscription
This is the event that is invoked when an encounter is
converted as part of the Scheduling redesign.
1322 DBIA1322 File SCHEDULING 2003/04/03 Retired Private 44
References to the Provider multiple of the Hospital
Location file (44).
- returns list of providers for a clinic for printing on an
encounter form. References ^SC(clinic,"PR", and
^SC("ADPR",clinic,
1335 DBIA1335 File SCHEDULING 2003/04/03 Retired Private 44
This DBIA documents references made by the
Radiology/Nuclear Medicine package to fields in the Hospital Location file
#44. The references are global reads.
1368 OE/RR conversion needs recent/future appts File SCHEDULING 2003/04/03 Retired Private 44
We would like permission for the OE/RR version 3.0
orders conversion to loop through appointments in the HOSPITAL LOCATION file.
It will loop through appointments within 30 days of the conversion run date
(+/-).
1369 Get Clinic Appointments File SCHEDULING 1995/10/02 APPROVED Active Controlled Subscription 2
^DPT(DFN,"DE" for current clinics
1416 HOSPITAL LOCATION File SCHEDULING 2003/04/03 Retired Private 44
Nursing can access the Hospital Location (44) file as
described in this DBIA.
1417 LOCATION TYPE File SCHEDULING 2004/06/24 APPROVED Active Private 40.9
Nursing can access the Location Type (40.9) file as
described in this DBIA.
1474 DBIA1474 Other SCHEDULING 2003/04/03 Retired Private
Quality: Audiology and Speech Pathology Audit and
Review (QUASAR), will place the PIMS option [SDCLINIC WORKLOAD] on the QUASAR
Reports menu tree during the post-init process. This will provide Audiology
and Speech Pathology workload data to A&SP users.
1475 Global Read of S node in File 2 File SCHEDULING 1996/02/09 APPROVED Active Private 2
The Adverse Reaction Tracking package requests
permission to do a direct global read of the "S" nodes in the Patient file in
order to get the STATUS field (#3) value for an APPOINTMENT (#1900) entry.
1477 Global Read of S node of File 44 File SCHEDULING 2003/04/03 Retired Private 44
The Adverse Reaction Tracking package requests
permission to do a direct global read of the "S" nodes of the Hospital
Location file (#44) in order to get the PATIENT (#2) field value of the
APPOINTMENT multiple (#1900).
1478 Global Read zero and CS nodes of File 409.5 File SCHEDULING 1996/02/09 Retired Private 409.5
The Adverse Reaction Tracking package requests
permission to do a direct global read of the "CS" nodes in the Scheduling
Visits file (#409.5) in order to get the ASSOCIATED CLINIC field (#3) value of
the CLINIC STOP CODE (#10) multiple. Also, we wish to do a direct global read
of the zero node in order to get to the PATIENT (#2) field value.
1482 DBIA1482 File SCHEDULING 2003/04/03 Retired Controlled Subscription 44
Quality: Audiology and Speech Pathology Audit and
Review (QUASAR) will reference the zero node of the HOSPITAL LOCATION file,
fields .01 NAME and field 8 STOP CODE NUMBER.
Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package,
A&SP CLINIC VISIT File (#509850.6), CLINIC LOCATION Field (#2.6) points to
the HOSPITAL LOCATION File (#44) to accommodate recording, tracking and
reporting workload by clinic.
Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package,
A&SP SITE PARAMETER File (#508950.8), CLINIC Multiple (#1), CLINIC LOCATION
(# .01) points to the HOSPITAL LOCATION File (#44) to accommodate recording,
tracking and reporting workload by clinic.
Quality: Audiology and Speech Pathology Audit and Review (QUASAR) Package,
A&SP DELETE VISIT File (#509850.9), CLINIC Field (#20) points to the HOSPITAL
LOCATION File (#44) to accommodate recording, tracking and reporting workload
by clinic.
1486 Global Read of I nodes in File 44 File SCHEDULING 2003/04/03 Retired Controlled Subscription 44
The Adverse Reaction Tracking package requests
permission to do a direct global read of the "I" nodes in the HOSPITAL
LOCATION file (#44) in order to get the INACTIVATE DATE (#2505) and the
REACTIVATE DATE (#2506) field values.
1575 AMBCARE DATE CALLS Routine SCHEDULING 1996/08/07 APPROVED Active Private
The calls in this agreement are to be used in
conjunction with the installation and running of the Ambulatory Care Report
Project Patch SD*53*44.		 SCDXUTL
1579 SCHEDULING CLASSIFICATION Routine SCHEDULING 2003/06/30 APPROVED Active Controlled Subscription
This IA is for the purpose of calling into routine
^SDCO22 to ask the classification questions such as Service Connected, Agent
Orange, Ionizing Radiation and Environmental Contaminants.		 SDCO22
1580 SDAMU Routine SCHEDULING 2003/04/03 Retired Controlled Subscription
Request ability to call into two linetags within
routine SDAMU.		 SDAMU
1581 CHECK OUT Routine SCHEDULING 2003/04/03 Retired Controlled Subscription
This IA is for the purpose of determining if the
checkout is complete.		 SDCOU
1582 INPATIENT APPT Routine SCHEDULING 2003/04/03 Retired Controlled Subscription
This IA is for the purpose of calling into routine
^SDAM2 to determine if an appointment is for an inpatient.		 SDAM2
1583 CHECKOUT REQUIRED? Routine SCHEDULING 2003/04/03 Retired Controlled Subscription
The purpose of this IA is to call in to REQ^SDM1A to
determine if checkout is required.		 SDM1A
1584 SDM Routine SCHEDULING 2003/04/03 Retired Controlled Subscription
The purpose of this IA is to call into routine ^SDM
from the top with the patient defined, so that a follow up appointment can be
made for the patient.		 SDM
1585 PRINT MGR CLINIC SETUP File SCHEDULING 1996/08/08 APPROVED Active Controlled Subscription 409.95
The purpose of this IA is to retrieve the current print
manager clinic setup.
1588 SC GLOBAL REFERENCES File SCHEDULING 2003/04/03 Retired Controlled Subscription 44
The purpose of this IA is to determine if flag is set
to default to PC practitioner.
1590 PC PRACTITIONER Routine SCHEDULING 1996/08/09 APPROVED Active Controlled Subscription
This IA is for the purpose of determining the ien and
name of the practitioner filling the PC position.		 SCAPMCU2
1591 SCHEDULED APPOINTMENTS File SCHEDULING 2003/04/03 Retired Controlled Subscription 44
This IA is for the purpose of finding all patients with
an appointment for a clinic on a given day.
1623 SCDXUAPI - OCCASION OF SERVICE ENTRY Routine SCHEDULING 1996/10/22 APPROVED Active Controlled Subscription
The SCDXUAPI is used to add locations to the HOSPITAL
LOCATION file which are deemed occasions of service. This routine has some
supported references, but they should only be used after being discussed with
the scheduling developers. The subscription to these APIs will be controlled.
There are 4 supported calls in this routine. Line tags not specifically
mentioned in this DBIA are NOT supported. Detailed documentation on these
calls is provided within the routine.
The supported calls are: RAD - this tag is specifically written for the
radiology package. It
allows them to pass in an IEN and convert the entry in file 44 to be
an occasion of service location.
LOC - main entry point to add occasion of service locations. This may
also be used to edit or inactivate a location.
SCREEN - provides a screen (S DIC("S")="SCREEN^SCDXUAPI(pkg)" to allow
selection of only occasion of service locations which were added by
the package passed in.
EXEMPT - provides a screen (S DIC("S")="EXEMPT^SCDXUAPI()") which will
allow selection of only stop codes which are deemed occasion of
service stop codes.		 SCDXUAPI
1713 SC LISTER Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC LISTER
1714 SC FILER Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC FILER
1715 SC DELETE ENTRY Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC DELETE ENTRY
1716 SC FIND Remote Procedure SCHEDULING 2006/11/17 Under Revision Supported SC FIND
1717 SC FILE NUMBER Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC FILE NUMBER
1718 SC GLOBAL NODE Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC GLOBAL NODE
1719 SC GETS ENTRY DATA Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC GETS ENTRY DATA
1720 SC LOCK/UNLOCK NODE Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC LOCK/UNLOCK NODE
1721 SC VALIDATOR Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC VALIDATOR
1722 SC GLOBAL NODE COUNT Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC GLOBAL NODE COUNT
1723 SC PRTP Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC PRTP
1724 SC MAILMAN Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC MAILMAN
1725 SC NEW HISTORY OK Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC NEW HISTORY OK
1726 SC CHANGE HISTORY OK Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC CHANGE HISTORY OK
1727 SC INACTIVATE ENTRY Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC INACTIVATE ENTRY
1728 SC DELETE HISTORY Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC DELETE HISTORY
1729 SC HISTORY STATUS OK Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC HISTORY STATUS OK
1730 SC MEAN TEST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC MEAN TEST
1731 SC TEAM LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC TEAM LIST
1732 SC PATIENT LOOKUP Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC PATIENT LOOKUP
1733 SC POSITION MEMBERS Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC POSITION MEMBERS
1734 SC FILE SINGLE VALUE Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC FILE SINGLE VALUE
1735 SCTM AUTOLINK GETRECORD Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCTM AUTOLINK GETRECORD
1736 SC KEY CHECK Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC KEY CHECK
1737 SCTM AUTOLINK SETRECORD Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCTM AUTOLINK SETRECORD
1738 SCTM AUTOLINK GETLINK Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCTM AUTOLINK GETLINK
1739 SCRP DEFINITION GETRECORD Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCRP DEFINITION GETRECORD
1740 SCUT GET USER RECORD Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCUT GET USER RECORD
1741 SCRP QUERY GETRECORD Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCRP QUERY GETRECORD
1752 SCRP SELECTION SOURCE Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCRP SELECTION SOURCE
1753 SCRP FILE ENTRY GETSELECTION Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCRP FILE ENTRY GETSELECTION
1754 SCRP QUERY SAVE Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCRP QUERY SAVE
1755 SCRP QUERY VALIDATE Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCRP QUERY VALIDATE
1756 SCRP QUERY DELETE Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCRP QUERY DELETE
1757 SCRP QUERY CHECK NAME Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCRP QUERY CHECK NAME
1758 SCUT SET USER QUERY DEFAULT Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCUT SET USER QUERY DEFAULT
1759 SCRP REPORT PRINT Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SCRP REPORT PRINT
1760 SC STAFF LOOKUP Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC STAFF LOOKUP
1761 SC USER CLASS STATUS Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC USER CLASS STATUS
1762 SC PRIMARY CARE TEAM Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC PRIMARY CARE TEAM
1763 SC BUILD PAT CLN LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SC BUILD PAT CLN LIST
1764 SC GET PAT BUILD Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Private SC GET PAT BUILD
1765 SC ASSIGN PATIENT LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC ASSIGN PATIENT LIST
1766 SC FILE PATIENT LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC FILE PATIENT LIST
1767 SC BUILD PAT TM LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC BUILD PAT TM LIST
1768 SC GET PAT TM LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC GET PAT TM LIST
1769 SC GET PAT BLOCK Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC GET PAT BLOCK
1770 SC BLD PAT LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC BLD PAT LIST
1771 SC FILE PAT TM ASGN Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC FILE PAT TM ASGN
1772 SC BLD PAT CLN LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC BLD PAT CLN LIST
1773 SC FILE PAT POS ASGN Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC FILE PAT POS ASGN
1774 SC BLD PAT SCDE LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC BLD PAT SCDE LIST
1775 SC BLD PAT TM LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC BLD PAT TM LIST
1776 SC BLD PAT POS LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC BLD PAT POS LIST
1777 SC PAT ENROLL CLN Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC PAT ENROLL CLN
1778 SC CHECK FOR PC POS Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC CHECK FOR PC POS
1779 SC FILE ALL PAT TM ASGN Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC FILE ALL PAT TM ASGN
1780 SC BLD PAT APT LIST Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC BLD PAT APT LIST
1781 SC FILE ALL PAT POS ASGN Remote Procedure SCHEDULING 2006/11/17 APPROVED Active Supported SC FILE ALL PAT POS ASGN
1797 SC BLD NOPC TM LIST Remote Procedure SCHEDULING APPROVED Active Supported SC BLD NOPC TM LIST
1798 SC PAT ASGN MAILMAN Remote Procedure SCHEDULING APPROVED Active Supported SC PAT ASGN MAILMAN
1846 DBIA1846 File SCHEDULING 2003/04/03 Retired Controlled Subscription 44
In addition to fields which are supported by DBIA
10040, DSS Extracts will reference the following data from the HOSPITAL
LOCATION file (#44).
Numerous DSS extract files contain a field (e.g., WARD, CLINIC NAME, LOSING
WARD, OR ROOM NUMBER, LOCATION (WARD OR CLINIC)) which is a pointer to the
HOSPITAL LOCATION file (#44).
1868 DBIA1868 File SCHEDULING 1996/12/05 Retired Private 409.5
DSS Extracts references the following data from the
SCHEDULING VISITS file (#409.5).
As of 12/5/96, it is understood that this file may soon become obsolete as
part of the ambulatory care development.
1910 DBIA1910 File SCHEDULING 1997/01/24 APPROVED Active Controlled Subscription 409.68
DSS Extracts references the following data from the
OUTPATIENT ENCOUNTER file (#409.68). The data is referenced in the Clinic
Visit Extract for scheduled appointments, dispositions, stand- alones, and
appended visits.
(1) In determining the number of scheduled appointments: For each clinic in
the HOSPITAL LOCATION file, the APPOINTMENT multiple is examined. For each
patient appointment in the date range, the APPOINTMENT multiple in the PATIENT
file is examined. We get the OUTPATIENT ENCOUNTER (p20) pointer. Using this
IEN, we get the VISIT FILE ENTRY from the OUTPATIENT ENCOUNTER file. This is
used to call a PCE API for data. (2) In determining the number of
dispositions, stand-alones, etc.: We loop through the "B" cross-reference of
the OUTPATIENT ENCOUNTER file for the extract date range and get the encounter
IEN. Since all of the data is on the zero node, we set a local variable to the
zero node and process it from there.
DSS uses the "B" cross reference on the DATE field. ^SCE("B",DATE,D0)
1916 SCAPMC - SUPPORTED PCMM CALLS Routine SCHEDULING 1997/02/05 APPROVED Active Supported
These are supported references in the SCAPMC routine:
(1) $$PRTM(SCTEAM,SCDATES,SCUSRA,SCROLEA,SCLIST,SCERR) --
(2) $$PRCL(SC44,SCDATES,SCPOSA,SCUSRA,SCROLEA,SCLIST,SCERR) --
(3) $$PRPT(DFN,SCDATES,SCPOSA,SCUSRA,SCROLEA,SCPURPA,SCLIST,SCERR) --
;
(4) $$PTTM(SCTEAM,SCDATES,SCLIST,SCERR) --
(5) $$TMPT(DFN,SCDATES,SCPURPA,SCLIST,SCERR) --
(6) $$INSTPCTM(DFN,SCEFF) --
(7) $$PTPR(SC200,SCDATES,SCPURPA,SCROLEA,SCLIST,SCERR,SCYESCL)--		 SCAPMC
1917 PCMM CALLS FOR CPRS/OERR - SCAPMC Routine SCHEDULING 1997/02/06 Pending Private
These are the PCMM supported calls in the SCAPMC
routine for Team and Personal Patient lists used by CPRS/OERR which are not
supported elsewhere:
ACPRTP^SCAPMC ACPTTM^SCAPMC ACPTTP^SCAPMC ACTM^SCAPMC ACTMNM^SCAPMC
ACTP^SCAPMC ACTPNM^SCAPMC INPTTM^SCAPMC TMAU^SCAPMC TMINST^SCAPMC TMPR^SCAPMC
TPPR^SCAPMC TPTM^SCAPMC		 SCAPMC
1918 PCMM CALLS FOR SCAPMCU1 Routine SCHEDULING 1997/02/06 APPROVED Retired Private
These are the PCMM supported calls in the SCAPMCU1
routine for Team and Personal Patient lists which are not supported elsewhere:
DATES^SCAPMCU1 RSNDICS^SCAPMCU1 TEAMCNT^SCAPMCU1
ICR was originally created for use by OE/RR. As of 10/11/17, no references to
routine SCAPMCU1 were found in OR* routines. Removed OE/RR as a subscriber.
**************************************************************
This ICR was retired as of 10/27/17 when HMP was shut down. HMP*2.0*12
released on 10/17/17 is an informational patch outlining the steps for the
sites to shut down the application. If HMP is reactivated in the future, the
HMP project team should review the access provided by this ICR with the
custodial application before the ICR is reactivated. See VistA Document
Library for list of retired HMP ICRs.
**************************************************************		 SCAPMCU1 2017/10/11
1919 PCMM CALLS FOR CPRS/OERR - SCAPMCU3 Routine SCHEDULING 1997/02/06 Pending Private
These are the PCMM supported calls in the SCAPMCU3
routine for Team and Personal Patient lists used by CPRS/OERR which are not
supported elsewhere:
GETEAM^SCAPMCU3 GETREC^SCAPMCU3 SETREC^SCAPMCU3		 SCAPMCU3
1920 PCMM FILE USED BY CPRS/OERR - SCTM(404.51 File SCHEDULING 1997/02/06 Pending Private 404.51
The file SCTM(404.51 is supported by PCMM for use by
CPRS/OERR Team and Personal Patient lists.
1921 PCMM FILE USED BY CPRS/OERR - SCTM(404.57 File SCHEDULING 1997/02/06 Withdrawn Private 404.57
The file SCTM(404.57 is supported by PCMM for use by
CPRS/OERR Team and Personal Patient lists.
4/24/15-Status changed from Pending to Withdrawn with concurrence from CPRS
team and PCMM representative. No references to this file found in CPRS/OR
code.
1922 PCMM FILE USED BY CPRS/OERR - SCPT(404.42 File SCHEDULING 1997/02/06 Pending Supported 404.42
The file SCPT(404.42 is supported by PCMM for use by
CPRS/OERR Team and Personal Patient lists.
1923 PCMM FILE USED BY CPRS/OERR - SCTM(404.56 File SCHEDULING 1997/02/06 Pending Private 404.56
The file SCTM(404.56 is supported by PCMM for use by
CPRS/OERR Team and Personal Patient lists.
1924 PCMM FILE USED BY CPRS/OERR - SCTM(404.52 File SCHEDULING 1997/02/06 Pending Private 404.52
The file SCTM(404.52 is supported by PCMM for use by
CPRS/OERR Team and Personal Patient lists.
1925 PCMM FILE USED BY CPRS/OERR - SCTM(404.58 File SCHEDULING 1997/02/06 Pending Private 404.58
The file SCTM(404.58 is supported by PCMM for use by
CPRS/OERR Team and Personal Patient lists.
1926 PCMM FILE USED BY CPRS/OERR - SCTM(404.59 File SCHEDULING 1997/02/06 Pending Private 404.59
The file SCTM(404.59 is supported by PCMM for use by
CPRS/OERR Team and Personal Patient lists.
1943 PCMM FILE USED BY CPRS/OERR - SD(403.44 File SCHEDULING 1997/02/27 Pending Private 403.44
The file SD(403.44 is supported by PCMM for use by
CPRS/OERR Team and Personal Patient lists.
1944 PCMM FILE USED BY CPRS/OERR - SD(403.46 File SCHEDULING 1997/02/27 Pending Private 403.46
The file SD(403.46 is supported by PCMM for use by
CPRS/OERR Team and Personal Patient lists.
1945 DBIA1945 File SCHEDULING 1997/03/03 APPROVED Active Private 404.51
DSS Extracts references the following data from the
TEAM file (#404.51).
A DSS option, "Primary Care Team Print", prints an alphabetical list of all
primary care teams and the IEN for each team. The intent of the option is to
provide help for building primary care teams on the commercial DSS system.
1993 DBIA1993 Routine SCHEDULING 1997/04/08 Retired Private
This is a one-time only DBIA with Scheduling to allow
the CPT v.6.0 package update to revise routines SDAMBAE2 and SDAMBAE3 to
eliminate references to files 409.72 and 409.71, which will no longer be
maintained.
In addition, the EFFECTIVE DATE will now be referenced by API, and not be
hard-coded into these routines.		 SDAMBAE3
2025 DBIA2025 Routine SCHEDULING 2003/04/03 Retired Private
This will return the External Value of the Outpatient
Classification from file 209.41		 SDCODD
2026 SDPCE Routine SCHEDULING 2003/04/03 APPROVED Active Private
This DBIA will permit PCE to use exiting Scheduling
function calls to get Eligibility, Appointment Type, and Status of an
encounter. 		SDPCE 2003/04/03
2045 DBIA2045 File SCHEDULING 1997/06/30 APPROVED Active Controlled Subscription 409.68
This will permit the direct reads using the "AVSIT"
cross reference of the OUTPATIENT ENCOUNTER file (#409.68). This will be used
to find an encounter associated with a specific visit from the VISIT file
(#9000010), or determine that no entry exists for a visit in the OUTPATIENT
ENCOUNTER file.
Once the "AVSIT" cross-reference has been used to determine if an entry
exists, the entry will be viewed, using VA FileMan, to check the STATUS field
(#.12)		 2018/10/26
2046 DBIA2046 File SCHEDULING 1997/06/30 Retired Private 409.44
This will allow the user to use the "OE"
cross-reference to obtain the ifn of a record, in order to find the value of
the PROVIDER (.01) field in the OUTPATIENT PROVIDER file (#409.44).
2047 DBIA2047 File SCHEDULING 1997/06/30 Retired Controlled Subscription 409.43
This will allow the user to use the "OE"
cross-reference to obtain the ifn of a record, in order to find the values of
the DIAGNOSIS (.01) and the DIAGNOSIS RANKING (.03) fields in the OUTPATIENT
DIAGNOSIS file (#409.43).
2065 DBIA2065 File SCHEDULING 1997/07/21 APPROVED Active Controlled Subscription 409.68
This will permit direct reads using the "ADFN" cross
reference of the OUTPATIENT ENCOUNTER file (#409.68). This will be used to
find an encounter associated with a specific patient for a specific date via
^SCE("ADFN",PATIENT,DATE,D0).
Once the "ADFN" cross-reference has been used to determine if an entry exists,
the entry will be viewed by a direct global read of the 0-node, and using the
following fields:
.03 - CLINIC STOP CODE; .04 - LOCATION; .05 - VISIT FILE ENTRY; .06 - PARENT
ENCOUNTER; and .08 - ORIGINATING PROCESS TYPE.
2074 DBIA2074 File SCHEDULING 1997/08/18 APPROVED Active Private 40.7
Read access is requested of all fields on the Zero node
of this file. These fields will be used for reporting purposes.
These fields are:
Fld # Fld Name Node;Pce
.01 NAME 0;1
1 AMIS REPORTING STOP CODE 0;2
2 INACTIVE DATE 0;3
3 CONVERT TO STOP CODE 0;4
4 COST DISTRIBUTION CENTER 0;5
Read access is requested of the "C" cross reference on this file. The "C"
cross reference will be used to check the existence of a specific 'Amis
Reporting Stop Code' as defined in field number 1.
It is noted that Event Capture needs to reference entries in the Clinic Stop
file (40.7) via Internal Entry Numbers (pointers) to that file.
2083 DBIA2083 File SCHEDULING 1997/08/26 APPROVED Active Controlled Subscription 409.41
This DBIA allows PCE to Globally read Scheduling's OUTPATIENT CLASSIFICATION
TYPE file (#409.41) for the below fields. This is used in asking the user the
patient Service Connected and Classification questions. PCE is now asking
these question for Scheduling.
2084 DBIA2084 File SCHEDULING 1997/08/26 APPROVED Active Private 409.42
PCE request a DBIA with Scheduling to kill entries in the OUTPATIENT
CLASSIFICATION file (#409.42). This is done in the process of asking the user
for the patient's classification if the classification " is no longer
applicable...". This is needed because PCE now ask the classification
questions for Scheduling and this was done in the asking of the classification
questions.
2088 DBIA2088 File SCHEDULING 1997/08/26 APPROVED Active Private 409.68
2089 DBIA2089 Other SCHEDULING 2003/04/03 Retired Private
PCE has a copy of Schedulings protocol SDAM LIST MENU
called PXCE SDAM LIST MENU with a default of Total Appt Profile and different
Entry and Exit actions. This DBIA is to allow PCE to include Scheduling's
protocols listed below on PCE's protocol.
NAME: PXCE SDAM LIST MENU ITEM TEXT: Appointment Lists
TYPE: menu
PACKAGE: PCE PATIENT CARE ENCOUNTER
DESCRIPTION: This action allows you to change which appointments will
be displayed based on their status of the appointments. For example, you
may change the display to list cancelled, checked in, checked out, future
appointments, inpatient appointments, appointment where no action has
been taken, non count appointments, no show appointments or all
appointments.
COLUMN WIDTH: 40 IDENTIFIER: AL ITEM: SDAM LIST CHECKED
IN MNEMONIC: CI
SEQUENCE: 1 ITEM: SDAM LIST NO SHOWS MNEMONIC: NS
SEQUENCE: 2 ITEM: SDAM LIST ALL MNEMONIC: TA
SEQUENCE: 3 ITEM: SDAM LIST NO ACTION MNEMONIC: NA
SEQUENCE: 4 ITEM: SDAM LIST CANCELLED MNEMONIC: CA
SEQUENCE: 5 ITEM: SDAM LIST FUTURE MNEMONIC: FU
SEQUENCE: 6 ITEM: SDAM LIST INPATIENT MNEMONIC: IP
SEQUENCE: 7 ITEM: SDAM LIST NON-COUNT MNEMONIC: NC
SEQUENCE: 8 ITEM: SDAM LIST CHECKED OUT MNEMONIC: CO
SEQUENCE: 9
EXIT ACTION: S:'$D(VALMBCK) VALMBCK="" D EXIT^PXCESDAM
ENTRY ACTION: D FULL^VALM1 S XQORM(0)="1A"
HEADER: W "" MENU PROMPT: Select List:
MENU DEFAULT: Total Appt Profile TIMESTAMP: 57166,50591
2096 2096 File SCHEDULING 2005/12/01 APPROVED Active Controlled Subscription 409.63
2220 DBIA2220 Routine SCHEDULING 1998/04/01 APPROVED Active Private
Integration agreement to use the variables SDSTPAMB, SDIEMM, VALQUIET
in the routine SCDXHLDR.
SDSTPAMB prevents Scheduling/Amb Care from sending an Event
Capture patient procedure to the Austin NPCD for workload credit.
However, the patient procedure is still filed in the respective
Scheduling/PCE files.
SDIEMM is used to prevent the validation checks from executing during
the Event Capture conversion completed as part of the install of
EC*2*7.
VALQUIET is used to prevent the validation dialogue from displaying to
the user during Event Capture patient record edit processing.		 SCDXHLDR
2236 DBIA2236 Routine SCHEDULING 1998/04/01 APPROVED Active Private
Integration agreement to use the function $$OKTOXMIT^SCDXFU04 to
determine if Event Capture patient procedures are to be sent to the
Austin NPCD for workload credit.
This integration agreement is used solely by the Event Capture Patient
file (#721) clean up patch, EC*2*7.		 SCDXFU04
2371 REATTACH SC TEAM AUTO-ADD PROTOCOL Other SCHEDULING 1998/04/28 APPROVED Active Private
CPRS did an OOPS. When we attempted to add our
protocol to theSC CLINIC ENTROLL/DISCHARGE EVENT DRIVER protocol, we ended up
removing the SC TEAM AUTO-ADD protocol which was already attached.
We would like permission to do the reattachment as part of OR*3*19. The patch
sends SC TEAM AUTO-ADD as ATTACH AT SITE and SC CLINIC ENROLL/DISCHARGE EVENT
DRIVER as USE AS LINK so we're not actually sending out the definitions, just
making the connection.
2372 SC CLINIC ENROLL/DISCHARGE EVENT DRIVER protocol Other SCHEDULING 2003/04/03 Retired Controlled Subscription
The SC CLINIC ENROLL/DISCHARGE EVENT DRIVER protocol is
provided to post information whenever a patient is enrolled in or discharged
from a clinic.
It is exported with the SC TEAM AUTO-ADD protcol attached to it.
2431 DBIA2431 Routine SCHEDULING 2003/04/03 Retired Private
A need exists in Integrated Billing to be able to get
the disposition node from the pointer value in the 9th piece of the encounter
file 0-node. We would like to call $$ER^SDOE to accomplish this.		 SDOE
2432 DBIA2432 File SCHEDULING 2004/06/24 APPROVED Active Controlled Subscription 44
Medicine requests a FILEMAN read to the DIVISION field
(#3.5) of the HOSPITAL LOCATION file (#44) [$P(^SC(D0,0),"^",15)] to display
what division a Ward belongs to.
2439 DBIA2439 File SCHEDULING 2003/04/03 Retired Controlled Subscription 44
Pharmacy Benefits Management (PBM) software needs to
access the division pointer from the Hospital Location File in order to
extract the facility number from the Medical Center Division File... Existing
DBIA #2432 would meet the need.
2443 DBIA2443 File SCHEDULING 1998/06/30 APPROVED Active Private 409.68
CIRN traverses the ^SCE("C" x-ref and uses ^SCE(D0,0)
to calculate the Master of Record score.
2468 DBIA2468 Routine SCHEDULING 2003/04/03 Retired Private
Integration agreement to use the call SC^SDCO23(DFN) to
display the patient's service connection percentage and rated disabilities as
part of the help text. This will display during the Event Capture Data Entry
options when a '?' is entered in response to the service connected
classification prompt.		 SDCO23
2501 DBIA2501 File SCHEDULING 1998/08/17 APPROVED Active Private 40.7
CIRN needs read access to ^DIC(40.7,'C' to calculate
the Master of Record Score
2546 ACRP INTERFACE TOOLKIT (AIT) Routine SCHEDULING 1998/09/22 APPROVED Active Supported
The ACRP Interface Toolkit (AIT) is a set of programmer tools that
provides access to outpatient encounter data. The toolkit contains
Application Programmer Interfaces (APIs) and Remote Procedure Calls
(RPCs) that provide access to procedure, diagnosis, provider, and
general data related to an encounter.
This AIT provides Class I packages, Class III software, and other local
code with one highly structured interface to the encounter data.
Note: For detail information on each specific API call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE
2548 ACRP INTERFACE TOOLKIT (AIT) Routine SCHEDULING 1998/09/22 APPROVED Active Supported
The ACRP Interface Toolkit (AIT) is a set of programmer tools that
provides access to outpatient encounter data. The toolkit contains
Application Programmer Interfaces (APIs) and Remote Procedure Calls
(RPCs) that provide access to procedure, diagnosis, provider, and
general data related to an encounter.
This AIT provides Class I packages, Class III software, and other local
code with one highly structured interface to the encounter data.
Note: For detail information on each specific API call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDQ
2552 ACRP INTERFACE TOOLKIT (AIT) Routine SCHEDULING 1998/09/22 APPROVED Active Supported
The ACRP Interface Toolkit (AIT) is a set of programmer tools that
provides access to outpatient encounter data. The toolkit contains
Application Programmer Interfaces (APIs) and Remote Procedure Calls
(RPCs) that provide access to procedure, diagnosis, provider, and
general data related to an encounter.
This AIT provides Class I packages, Class III software, and other local
code with one highly structured interface to the encounter data.
Note: For detail information on each specific API call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDQUT
2553 SDOE ASSIGNED A DIAGNOSIS Remote Procedure SCHEDULING 1998/09/22 APPROVED Active Supported
This remote procedure call (RPC) returns a boolean indicator on
whether at least one diagnosis has been associated with an encounter.
---------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm 		SDOE ASSIGNED A DIAGNOSIS
2554 SDOE ASSIGNED A PROCEDURE Remote Procedure SCHEDULING 1998/09/22 APPROVED Active Supported
This remote procedure call (RPC) returns a boolean indicator on
whether at least one procedure has been associated with an encounter.
---------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm 		SDOE ASSIGNED A PROCEDURE
2555 SDOE ASSIGNED A PROVIDER Remote Procedure SCHEDULING 1998/09/22 APPROVED Active Supported
This remote procedure call (RPC) returns a boolean indicator on
whether at least one provider has been associated with an encounter.
---------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm 		SDOE ASSIGNED A PROVIDER
2556 SDOE FIND DIAGNOSIS Remote Procedure SCHEDULING 1998/09/22 APPROVED Active Supported
This remote procedure call (RPC) returns a boolean indicator on
whether a specific diagnosis has been associated with an encounter.
---------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm 		SDOE FIND DIAGNOSIS
2557 SDOE FIND FIRST ENCOUNTER Remote Procedure SCHEDULING 1998/09/22 APPROVED Active Supported
This remote procedure call (RPC) returns the internal entry number
of an Outpatient Encounter file (#409.68) entry for the first encounter
for a patient in a specified date range.
---------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm 		SDOE FIND FIRST ENCOUNTER
2558 SDOE FIND FIRST STANDALONE Remote Procedure SCHEDULING 1998/09/22 APPROVED Active Supported
This remote procedure call (RPC) returns the internal entry number
of an Outpatient Encounter file (#409.68) entry for the first
standalone add/edit encounter for a patient in a specified date range.
---------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm 		SDOE FIND FIRST STANDALONE
2559 SDOE FIND LAST STANDALONE Remote Procedure SCHEDULING 1998/09/22 APPROVED Active Supported
This remote procedure call (RPC) returns the internal entry number
of an Outpatient Encounter file (#409.68) entry for the last
standalone add/edit encounter for a patient in a specified date range.
---------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm 		SDOE FIND LAST STANDALONE
2560 SDOE FIND PROCEDURE Remote Procedure SCHEDULING 1998/09/22 APPROVED Active Supported
This remote procedure call (RPC) returns a boolean indicator on
whether a specific procedure has been associated with an encounter.
---------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm 		SDOE FIND PROCEDURE
2561 SDOE FIND PROVIDER Remote Procedure SCHEDULING 1998/09/22 APPROVED Active Supported
This remote procedure call (RPC) returns a boolean indicator on
whether a specific provider has been associated with an encounter.
---------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm 		SDOE FIND PROVIDER
2564 SDOE GET DIAGNOSES Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) returns an array of diagnoses for
an encounter.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE GET DIAGNOSES
2565 SDOE GET GENERAL DATA Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) returns the zeroth and other nodes
of an outpatient encounter.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE GET GENERAL DATA
2566 SDOE GET PRIMARY DIAGNOSIS Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) returns the internal entry number
of the primary diagnosis code (^ICD9) for an encounter.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
These files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE GET PRIMARY DIAGNOSIS 2012/04/10
2567 SDOE GET PROCEDURES Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) returns a subscripted array of
procedures for an encounter.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE GET PROCEDURES
2568 SDOE GET PROVIDERS Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) returns a subscripted array of
providers for an encounter.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE GET PROVIDERS
2569 SDOE GET ZERO NODE Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) returns the zeroth node of an
outpatient encounter.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE GET ZERO NODE
2570 SDOE LIST ENCOUNTERS FOR DATES Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) returns a list of outpatient encounters
for a date range.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE LIST ENCOUNTERS FOR DATES
2571 SDOE LIST ENCOUNTERS FOR PAT Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) returns a list of outpatient
encounters for a specified patient and specified date range.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE LIST ENCOUNTERS FOR PAT
2572 SDOE LIST ENCOUNTERS FOR VISIT Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) returns a list of outpatient
encounters for a specified PCE visit.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE LIST ENCOUNTERS FOR VISIT
2573 SDOE PARSE GENERAL DATA Remote Procedure SCHEDULING 1998/09/23 APPROVED Active Supported
This remote procedure call (RPC) will parse the data returned by
SDOE GET GENERAL DATA remote procedure call into individual field
nodes.
------------------------------------------------------------------
This RPC is part of the ACRP Interface Toolkit (AIT).
The AIT is a set of programmer tools that provides access
to outpatient encounter data.
Note: For detail information on this RPC call, see the following
AIT documentation files:
sd_53_p131_tooldoc.doc or
sd_53_p131_tooldoc.pdf.
Theses files are distributed as part of patch SD*5.3*131.
Also, the documentation is available on-line at the following URL:
http://127.0.0.1/softserv/mip/wr/acrpapi.htm		 SDOE PARSE GENERAL DATA
2579 SDAM Routine SCHEDULING 2003/04/03 Retired Private
The [HBHC APPOINTMENT] OPTION CALLS ROUTINE SDAM, USING
ENTRY POINT EN. This is IA is needed due to cloning the [SDAM APPT MGT]
option.		 SDAM
2580 SDAMEVT Routine SCHEDULING 2003/04/03 Retired Private
THE [HBHC APPOINTMENT] OPTION CALLS ROUTINE SDAMEVT IN
ITS EXIT ACTION USING ENTRY POINT HDKILL.
This is IA is needed due to cloning the [SDAM APPT MGT] option.		 SDAMEVT
2590 SD OUTPATIENT GAF SCORE UTILS Routine SCHEDULING 1998/09/30 APPROVED Active Supported
The purpose of these API's is to facilitate the entry
of Global Assessment of Function (GAF) scores to the Mental Health package
from outpatient encounters. VHA Directive, 97-059, dated November 25, 1997,
"Instituting Global Assessment of Function (GAF) Scores in Axis V Mental
Health Patients", provides guidelines for the collection of these GAF scores.
These API's will be used to (1) return whether a new GAF score is required for
an outpatient and (2) whether the outpatient encounter clinic is a Mental
Health clinic for which GAF scores must be collected. These API's have been
added to the routine: SDUTL2.		 SDUTL2
2591 SD OUTPATIENT ENCOUNTER GAF SCORE CAPTURE Routine SCHEDULING 2003/04/03 Retired Private
Patient Care Encounter needs to capture GAF scores for
outpatient encounters. This call will allow entry of the GAF score, Date/Time
of the GAF score, and provider determining the GAF score through the
Scheduling call used in appointment management. The internal entry number of
the patient, DFN, is passed into the call as variable DFN. There is no return
from the call. This call will ask for the score, date/time, and provider for
posting the GAF score.		 SDGAF
2669 DBIA2669 Other SCHEDULING 2003/04/03 Retired 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.
2675 IA2675 File SCHEDULING 2003/08/13 APPROVED Active Private 44
to determine the Medical Center Division IEN associated
with the Hospital Location when Batch Printing Progress Notes.
2795 DBIA2795 File SCHEDULING 1999/04/23 APPROVED Active Private 404.51
The Clinical Reminder Package would like to reference
the following file directly :
TEAM #404.51 - Determine team's institution
As corresponding APIs are planned, this IA will be in effect until the
appropriate APIs are released.
2804 DBIA2804 File SCHEDULING 2004/12/21 APPROVED Active Private 44
The Clinical Reminder Package would like to reference
the HOSPITAL LOCATION file #44 directly to determine the CLINIC GROUP and STOP
CODE NUMBER for a location and all patients with APPOINTMENTS at a clinic on a
given date.
2810 DBIA2810-A File SCHEDULING 1999/04/29 APPROVED Active Private 404.57
The Clinical Reminder Package would like to reference
the following file directly :
TEAM POSITION #404.57 - Determine associated Clinic for Team Position
As corresponding APIs are planned, this IA will be in effect until the
appropriate APIs are released.
2811 DBIA2810-B File SCHEDULING 1999/04/29 APPROVED Active Private 404.43
The Clinical Reminder Package would like to reference
the following files directly :
PATIENT TEAM POSITION ASSIGNMENT #404.43 - Determine Team Position
As corresponding APIs are planned, this IA will be in effect until the
appropriate APIs are released.
2822 DBIA2822 Routine SCHEDULING 2003/04/03 Retired Private
This call is needed to determine if data passed to IB
is from the OUTPATIENT ENCOUNTER file or from PCE.		 SDOEUT
2848 GETALL API CALL Routine SCHEDULING 1999/06/16 APPROVED Active Supported SCAPMCA
2850 TIU use of SDAM1 Routine SCHEDULING 2003/04/03 Retired Private
TIU calls $$STATUS^SDAM1 to retrieve the status of an
appointment.		 SDAM1
2851 TIU use of SD(409.63,'ACO',1,STATUS) File SCHEDULING 2004/08/05 APPROVED Active Private 409.63
TIU uses a global read of ^SD(409.63,"ACO",1,STATUS)
cross-reference on the 'Check Out Allowed?' field (#.06) of the Appointment
Status file (#409.63) to determine if the appointment is allowed for
check-out.
STATUS := appt status as determined by $$STATUS^SDAM1.
2881 DBIA2881 Routine SCHEDULING 1999/07/29 Pending Supported
Contains the supported reference to routine SCMCHLZ for
the supported API to be released with PCMM patch SD*5.3*177.		 SCMCHLZ
2936 GMTS/SCTM Team File SCHEDULING 1999/10/26 APPROVED Active Controlled Subscription 404.51
Health Summary extracts references the following data
from the TEAM file (#404.51).
The Demographic component of Health Summary prints the Team Name and and Team
Phone Number of the Primary Care Team.
2953 STATUS OF PATIENT IN THE OUTPATIENT ENCOUNTER FILE File SCHEDULING 1999/11/02 APPROVED Active Controlled Subscription 409.68
This database integration agreement (DBIA) is needed to
track a particular status of a patient in the OUTPATIENT ENCOUNTER (#409.68)
file. The input variable is the DFN of the patient, so our application needs
to roll down the 'ADFN' M cross-reference (Patient field) in file 409.68. Our
application intends to read, with FileMan, the STATUS (field .12) of the
patient in the OUTPATIENT ENCOUNTER (#409.68) file.
We are looking for a private subscription that would allow our application to
walk down the 'ADFN' cross-reference and then read, with FileMan, the STATUS
field in the OUTPATIENT ENCOUNTER file.
3070 SCAPMC Clinic List Routine SCHEDULING 2000/03/22 APPROVED Active Controlled Subscription SCAPMC
3284 DBIA3284 Routine SCHEDULING 2003/04/21 APPROVED Active Private SCAPMCU2
3285 DBIA3285 File SCHEDULING 2001/01/04 APPROVED Active Private 404.57
3286 DBIA3286 File SCHEDULING 2001/01/04 APPROVED Active Private 404.51
3306 SC TEAM INFORMATION List Template Other SCHEDULING 2003/04/03 Retired Private
The [PXCE SC DISPLAY TEAM INFO] protocol uses the SC
TEAM INFORMATION List Template.
3309 PCLINE-SDPPTEM Function Call Routine SCHEDULING 2003/04/03 Retired Private
PXCE functionality requires access a patient's PC
Provider, Associate Provider and Team Information. Routine PXCE makes a call
to the API $$PCLINE^SDPPTEM passing Patient's DFN and Date information.
$$PCLINE^SDPPTEM as a function returns the necessary data formatted as an 80
character line, or "" if none.		 SDPPTEM
3310 EN and PAT - SCMCQK Access Routine SCHEDULING 2001/02/13 APPROVED Active Private
The PC Assign or Unassign, [PXCE SC PC
Assign/Unassign], protocol uses the Scheduling routine SCMCQK as a means to
acquire Team information for display and possible processing. [PXCE SC PC
Assign/Unassign], PC Assign or Unassign, is an action item on the PXCE MAIN
and PXCE SDAM menus and accesses SCMCQK using the "EN" and "PAT" entry points. 		SCMCQK
3311 PXCE SC DISPLAY TEAM INFO Protcol Routine SCHEDULING 2001/02/13 APPROVED Active Private
The entry action for the Display Team Information,
[PXCE SC DISPLAY TEAM INFO], protocol has the potential to use routine SCMCU1
as means to select a patient. PXCE SC DISPLAY TEAM INFO (TI Display Team
Information) is an action item on the PXCE MAIN and PXCE SDAM menus and may
access ^SCMCU1 at its "SEL" entry point.		 SCMCU1
3312 SC PCMM ROLL Security Key Other SCHEDULING 2003/04/03 Retired Private
The PC Assign or Unassign, [PXCE SC PC
Assign/Unassign], protocol is locked by the SC PCMM ROLL security key and can
only be used by users who have this key assigned.
3313 ELSTAT and COLLAT - SDUTL2 Routine SCHEDULING 2003/04/03 Retired Private
The routine PXCE uses the SCHEDULING "miscellaneous
utilities" program SDUTL2 to access patient eligibility statuses. Accessing
SDUTL2 at entry points ELSTAT and COLLAT, PXCE accesses "eligibility status"
and "collateral eligibility status" functions respectively.		 SDUTL2
3398 ROUTINE SCMCUT Routine SCHEDULING 2003/04/21 Retired Controlled Subscription
In support of the Smart Card initiative, Registration
needs to use routine SCMCUT and the APIs in the routine to ensure that server
and client software running on both the local site and the remote site can run
together.		 SCMCUT
3399 ROUTINE SCUTBK3 Routine SCHEDULING 2001/05/30 APPROVED Active Controlled Subscription
In support of hte Smart Card initiative the
Registration Package needs the use of Scheduling APIs contained in this
routine.		 SCUTBK3
3400 FILE 404.45 File SCHEDULING 2001/05/30 APPROVED Active Controlled Subscription 404.45
In support of the Smart Card initiative the
Registration package needs to use file 404.45 - PCMM SERVER PATCH file.
3401 FILE 404.46 File SCHEDULING 2001/05/30 APPROVED Active Controlled Subscription 404.46
In support of the Smart Card initiative the
Registration package needs to use file 404.46 - PCMM CLIENT PATCH file.
3419 TIU use of Appt. Multiple (#2.98) File SCHEDULING 2003/04/03 Retired Private 2.98
TIU uses a call to EN^DIQ1 to retrieve fields
.01;100;9.5 from the Appointment multiple (#2.98) for a Patient.
TIU loops through the ^DPT(DFN,"S",IEN global to obtain the Appointment
multiple IEN for the patient.
The variable DA is set to DFN and DA(1) is set to IEN before calling EN^DIQ1
to obtain the field values.
The information obtained is then displayed to the user in External Format when
prompting the user to select a Scheduled Visit in TIU.
This agreement will have to change with the Scheduling Redesign.
3491 DBIA3491 File SCHEDULING 2001/12/07 APPROVED Active Private 40.7
3570 WHO IS THE CODER OF PCE File SCHEDULING 2002/04/26 Withdrawn Private 409.68
IB would like to determine the name of the coder for
outpatient encounters/claims. We shall determine this by the person who most
recently edited the outpatient encounter file.
3846 Print Full (Patient Profile MAS) Report Routine SCHEDULING 2002/11/19 APPROVED Active Private
DBIA for AMIE II (Automated Medical Information
Exchange) to use routine PRINT^SDPPRT in a remote procedure to print Full
(Patient Profile MAS) Report. Integration Agreement will be only until
Scheduling Replacement begin.		 SDPPRT
3859 APPOINTMENT DATA BY PATIENT Routine SCHEDULING 2002/12/12 APPROVED Active Controlled Subscription
This DBIA contains a list of the supported calls for
interaction with Appointment data contained in the Patient appointment
sub-file 2.98 and the Hospital Location appointment sub-file 44.001. This
DBIA is associated with Scheduling patch SD*5.3*275, to be released to NVS on
1/10/03.
The supported calls are:
GETAPPT^SDAMA201 and $$NEXTAPPT^SDAMA201		 SDAMA201
3864 SCHEDULING API Routine SCHEDULING 2003/01/06 Withdrawn Controlled Subscription
3869 APPOINTMENT DATA BY CLINIC Routine SCHEDULING 2003/01/08 APPROVED Active Controlled Subscription
This IA contains a list of the supported calls for
interaction with Appointment data contained in the Patient sub-file 2.98 and
the Hospital Location appointment sub-file 44.001. This IA is associated with
Scheduling patch SD*5.3*275, to be released to NVS on 1/10/03.		 SDAMA202
4084 FILE 44 AC X-REF File SCHEDULING 2003/04/30 APPROVED Active Controlled Subscription 44
This agreement allows permission to loop through the AC
cross-reference on the HOSPITAL LOCATION file (#44). The AC cross-reference is
on the TYPE EXTENSION field (#2.1). Using the AC cross-reference will allow us
to get the internal entry numbers (IENs) for locations by their type (e.g.,
retrieve only clinics). Using the AC cross-reference will speed up the
retrieval of IENs.		 2007/01/31
4133 IMO QUALIFIER Routine SCHEDULING 2003/06/25 APPROVED Active Controlled Subscription
The purpose of this DBIA is asking for permission to
call the scheduling API from OE/RR at server side to determine if a specific
patient at a specific clinic is qualified to receive inpatient medication.		 SDAMA203
4193 DBIA4193 Routine SCHEDULING 2003/08/20 APPROVED Active Private
As part of the Transitional Pharmacy Benefit project, a
list of eligible patients must be built upon install of the patches that make
up this project. There are various criteria used to determine eligibility, and
part of this process involves retrieving appointment information from the
PATIENT (#2) file, which is what the SDPHARM routine does.		 SDPHARM
4194 DBIA4194 Routine SCHEDULING 2003/08/13 APPROVED Active Private
As part of the Transitional Pharmacy Benefit project, a
list of eligible patients must be built upon install of the patches that make
up this project. There are various criteria used to determine eligibility, and
part of this process involves retrieving information from the SD WAIT LIST
(#409.3) file, and it's associated files, which is what the SDPBE routine
does.		 SDPBE
4196 DBIA4196 Routine SCHEDULING 2003/08/20 APPROVED Active Private
The Scheduling package will provide a default
Institution and default Station Number to Outpatient Pharmacy, based on future
appointments for patients, when someone is attempting to add a patient to the
TPB ELIGIBILITY (#52.91) File. The Scheduling package will also provide the
nearest Primary Care Appointment date and Hospital Location of that
appointment for a patient.		 SDPHARM1
4216 PATIENT APPOINTMENT EXISTS Routine SCHEDULING 2003/08/25 APPROVED Active Controlled Subscription
This DBIA contains an API that checks for the existence
of any appointment for a specific patient.		 SDAMA204
4347 SCMSVUT5 Routine SCHEDULING 2004/02/17 APPROVED Active Supported
Supported calls for parsing of an HL7 segment
Valid after patches DG*5.3*508 and SD*5.3*293 are released.		 SCMSVUT5
4422 READ OF AE CROSS REFERENCE File SCHEDULING 2005/11/17 APPROVED Active Controlled Subscription 44
OR request permission to do a read on file #44 "AE"
cross reference. This cross reference allows for a quick way to find all
hospital locations that have the same value for the "ADMINISTER INPATIENT
MEDS?" field.
4433 DBIA4433 Routine SCHEDULING 2004/05/25 APPROVED Active Supported SDAMA301
4450 DENTAL READ OF FILE 409.68 File SCHEDULING 2004/07/06 APPROVED Active Private 409.68
Dental transmits its dental specific data to the AAC
once a week. The Decision Support staff requested that Dental include all
data elements it needed in the HL7 extracts of VistA that are transmited to
the AAC. One of the VistA fields requested by the VA-DSS is the OUTPATIENT
ENCOUNTER (#409.68) date and time as well as the internal entry number. The
dental encounter file (#228.1) has a pointer to the VISIT (#900010) file. PCE
developers have said that for each entry in file 409.68 there should be a
1-to-1 relationship with the VISIT file. Thus the DENTAL package is
requesting to be allowed to do direct global reads of the "AVSIT" cross
reference on file 409.68 to get the 409.68 record number corresponding to a
VISIT file record number. Then using the 409.68 record number, a direct
global read will be done for the .01 field of that record to get the encounter
date and time.
4456 POINTER TO THE FILE# 409.67 File SCHEDULING 2004/08/03 APPROVED Active Controlled Subscription 409.67
This DBIA will allowed Clinical Reminders to point to
file# 409.67
4482 READ OF FILE 44 'AST' AND 'ACST' CROSS-REFERENCES File SCHEDULING 2004/07/28 APPROVED Active Controlled Subscription 44
Clinical Reminders request permission to do a global
read on file 44 "AST" and "ACST" cross-references. This gives permission to
access the CREDIT STOP CODE information in field 2503.
4518 DBIA4518 Routine SCHEDULING 2007/04/05 APPROVED Active Private
This DBIA provides an interface to retrieve the PCE
CHECK OUT (Field #11) and the CONSULT LINK (Field #33) for a specific RSA
appointment, which is identified by its appointment ID, from the RSA
APPOINTMENT LIST File #44.44. This file is currently the authoritative source
for these appointment related fields for RSA appointments.		 SDAMUTIL 2007/09/27
4565 DBIA4565 Routine SCHEDULING 2007/04/05 APPROVED Active Private
This DBIA provides an interface to delete the CONSULT
LINK (Field #33) in the RSA APPOINTMENT LIST File (#44.44) for a specific RSA
appointment, which is identified by its appointment ID.		 SDAMUTIL 2007/09/27
4652 CLNCHK - SDUTL2 (RESTRICTING STOP CODE) Routine SCHEDULING 2005/04/01 APPROVED Active Supported
The purpose of API CLNCK^SDUTL2 is to determine whether
a Clinic entry in the HOSPITAL LOCATION File #44 has conforming stop codes.
Stop codes are stored in the CLINIC STOP File #40.7 and are used in accordance
to their assigned restriction types. Stops codes with restriction type 'P'
can only be used in the primary stop code position. Stop codes with
restriction type 'S' can only be used in the secondary stop code position.
Stop codes with restriction type 'E' can be used in either the primary or
secondary stop code position		 SDUTL2
4668 PFSS ACCOUNT NUMBER REFERENCE Routine SCHEDULING 2006/09/20 APPROVED Active Controlled Subscription
This API will return the PFSS Account Number Reference
stored in the Scheduling APPOINTMENT ACCOUNT NUMBER REFERENCE File (#409.55).
This reference number is provided by the IBB PFSS ACCOUNT API when a new
appointment is made.		 SDPFSS2
4671 DBIA4671 File SCHEDULING 2005/05/31 APPROVED Active Controlled Subscription 409.1
For Patient Financial Services System (PFSS), the IBB
module of INTEGRATED BILLING requires direct global read of the SYNONYM field
(#4) in the APPOINTMENT TYPE file (#409.1).
4672 DBIA4672 File SCHEDULING 2005/05/31 APPROVED Active Controlled Subscription 44
For Patient Financial Services System (PFSS), the IBB
module of INTEGRATED BILLING requires direct global read of the DIVISION field
(#3.5) in the HOSPITAL LOCATION file (#44).
4782 CLINIC PHONE File SCHEDULING 2005/08/31 APPROVED Active Controlled Subscription 44
The purpose of this agreement is to allow access to TELEPHONE field #99, of
the HOSPITAL LOCATION file #44.
4836 DBIA4836 File SCHEDULING 2006/03/22 APPROVED Active Private 40.7
4841 CONSULT LINK File SCHEDULING 2006/04/10 APPROVED Active Private 44 2009/07/14
4842 DBIA4842 File SCHEDULING 2006/04/10 APPROVED Active Private 409.3
4843 DBIA4843 File SCHEDULING 2006/04/10 APPROVED Active Private 409.31
4844 DBIA4844 File SCHEDULING 2006/04/10 APPROVED Active Private 409.32
4850 CALL TO GET ENCOUNTER STATUS Routine SCHEDULING 2006/04/27 APPROVED Active Controlled Subscription
This DBIA will permit Clinical Reminders to use an
existing Scheduling function call to get the Status of an encounter. 		SDPCE
4929 CLINIC STOP file File SCHEDULING 2006/11/07 APPROVED Active Controlled Subscription 40.7
The Spinal Cord package would like to request direct
global access to the B cross-reference of the CLINIC STOP file (#40.7) for
reporting purposes
4930 OUTPATIENT DIAGNOSIS file File SCHEDULING 2006/11/28 APPROVED Active Controlled Subscription 409.43
The Spinal Cord package would like to request direct
global access to the following field of the OUTPATIENT DIAGNOSIS file
(#409.43) for reporting purposes:
^SDD(409.43,"AO",D0,D1)
.01 DIAGNOSIS 0;1 direct global read
4990 SERVICE CONNECTED AUTOMATION Routine SCHEDULING 2007/05/10 APPROVED Active Supported
This routine supports the Automated Service Connected
Designation (ASCD) project. It automates the service connected (SC) value for
outpatient encounters. It also determines whether an encounter should be sent
to the ASCD file #409.48 for additional review. The evaluation of the SC
value is based on the mapping of the patient rated disability codes and ICD
codes.		 SDSCAPI 2012/04/10
5040 AR Access to the Outpatient Encounter File File SCHEDULING 2007/11/07 APPROVED Active Private 409.68
For the Hold Debt to DMC project the Accounts
Receivable (AR) software package is providing some new reports for the AR
clerks to use. For these new reports the Business Office requested that AR
include bills that have an episode of care within the previous 365 days and if
appropriate display the date of the most recent Outpatient Encounter. This is
to be done using the RESULTING FROM (#.04) field in the INTEGRATED BILLING
ACTION (#350) file which contains a soft-link back to the entry in any file
that caused this billing transaction to be set. One of these soft-links is to
the OUTPATIENT ENCOUNTER (#409.68) file which relates to DBIA 402 subscribed
to by the Integrated Billing package.
The AR package requires access to the DATE (#.01) field of the OUTPATIENT
ENCOUNTER (#409.68) based on its interface with the IB package.		 2007/12/13
5195 Recall Reminder Display Routine SCHEDULING 2008/05/07 APPROVED Active Controlled Subscription
These changes are required to show Recall Reminder
information on the Cover sheet for all CPRS users. This is a view only NO
input done.
ORWCV.INT VST+22 ;***ADD CHANGES TO CALL COVER^SDRROR VST+23
D COVER^SDRROR DTLVST+14 I $P(APPTINFO,";")="R" D RCDTL^SDRROR
making two calls to SDRROR
SDRR is a new namespace being used to move a Class III application (Clinic
Recall) to a National Class I application called Reminder Recall (SDRR
NAMESPACE).		 SDRROR 2019/10/02
5250 PCMM CALLS FOR MYHEALTHEVET - SCAPMC Routine SCHEDULING 2008/08/01 APPROVED Active Private
Allows MyHealthEVet to call exisiting API's that are
not supported references.		 SCAPMC 2008/09/15
5253 DBIA5253 File SCHEDULING 2008/08/20 Pending Private 44
First Draft Request - Need to post developer as to
request questions and variables to determine correctness - LEC 8/20/08
5265 MyHealtheVet read access to File 40.9 Location Type File SCHEDULING 2008/09/25 APPROVED Active Private 40.9
Read access to file 40.9 by the MyHealtheVet package
using FILEMAN		 2008/09/30
5266 MyHealtheVet access to file 44 Hospital Location File SCHEDULING 2008/09/25 APPROVED Active Private 44
Myhealthevet access to file 44 Hospital Location to add
"Secure Messaging" as a location.		 2008/09/30
5349 FBCS ACCESS TO GLOBAL SCTM(404.51 File SCHEDULING 2009/01/15 Retired Controlled Subscription 404.51
Use cloned logic from existing routine "SDPPTEM" to
print Primary care team information to an array for the GUI interface.
5474 SCHEDULING Option Access SCHEDULING 2011/01/26 Withdrawn
5697 PCMM MHTC API's for CPRS Routine SCHEDULING 2011/07/26 APPROVED Active Controlled Subscription
This is a API that returns the Mental Health treatment
Coordinator from PCMM to CPRS for display in the CPRS Gui.		 SCMCMHTC 2011/12/07
5791 DBIA5791 - Update Field #309 in File #44 File SCHEDULING 2012/04/30 APPROVED Active Private 44
To support delivery of the VA Point of Service (VPS
Kiosks), access to the HOSPITAL LOCATION file (#44) is requested in order to
update field #309 (CHECKED-IN) via a direct FileMan edit. This field will be
updated when a patient executes the CHECK-IN procedure via a Remote Procedure
call (RPC) at a VA Kiosk.		 2012/09/26
5792 DBIA5792 - $$FIND call in SDAM2 Routine SCHEDULING 2012/04/30 APPROVED Active Private
To support delivery of the VA Point of Service (VPS
Kiosks), access to the API $$FIND^SDAM2() is requested in order to find all
the appointments for a patient on a given date.		 SDAM2 2012/09/26
5833 CLINIC PHYSICAL LOCATION File SCHEDULING 2012/08/14 APPROVED Active Private 44
The VA POINT OF SERVICE (KIOSK) package needs Fileman
read access to the PHYSICAL LOCATION field (10) of the HOSPITAL LOCATION file
(#44). The VPS GET PATIENT DEMOGRAPHIC remote procedure call will retrieve
data from this field and return the data to the Vecna Kiosk located at the
local VAMC.		 2012/08/20
5838 SDAMEVT Routine SCHEDULING 2012/08/30 APPROVED Active Private
THE [VETERAN POINT OF SERVICE] CHECK-IN RPC CALLS
BEFORE,HANDLE, AFTER, AND EVT IN SDAMEVT TO ENSURE THAT ALL OTHER PROCESSES
REQUIRING NOTIFICATION OF THE CHECK-IN ACTIVITY ARE NOTIFIED.
Parameters in the RPC have the following mapping for VPS:
VPSDT -> SDT Patient's appt. date and time.
VPSCLIN -> SDCL IEN of clinic in HOSPITAL LOCATION file #44
VPSCIEN -> SDDA IFN for ^SC(CLINIC,"S",DATE,1,IFN)
SDCIHDL -> SDHDL Event handle		 SDAMEVT 2012/10/12
6026 HOSPITAL LOCATION CLINIC APPOINTMENTS File SCHEDULING 2014/02/12 Pending Private 44
This agreement give the Surgery Quality and Workflow
Manager (SQWM) module of the VistA Surgery package permission to add and
update clinic appointments on the APPOINTMENT sub-file of the HOSPITAL
LOCATION file (#44).
6027 SCMC PCMM/R GET PRIMARY CARE DETAILS Routine SCHEDULING 2014/02/21 APPROVED Active Private
This is a new API developed for PCMMR that will return
details regarding the Patient Aligned Care Team (PACT) and other team
assignments (Mental Health, Specialty, OEF/OIF/OND) for a patient. This
information will be retrieved from PCMMR and displayed when a user clicks on
the PCMM "button" on the CPRS header.		 SCMCWS1 2014/06/16
6042 SCMC PCMM/R GET PRIMARY CARE SUMMARY Routine SCHEDULING 2014/04/15 APPROVED Active Private
This is a new API developed for PCMMR that will return
Patient Aligned Care Team (PACT) summary data for a patient. This information
will include site name, PACT name, Primary Care Provider (PCP) and Associate
Provider (AP) names. PCMMR will keep this data current. It will be stored in
the Outpatient Profile (404.41) file in the CPRS Header Text (.06) field.		 SCMCWSUT 2014/06/16
6044 MBAA Access to SC files File SCHEDULING 2014/04/22 APPROVED Active Private 44
The Scheduling Calendar View (MBAA namespace) RPCs,
MBAA APPOINTMENT MAKE, MBAA CANCEL APPOINTMENT, MBAA PATIENT PENDING APPT,
MBAA GET CLINIC AVAILABILITY, and MBAA PROVIDER TO CLINIC and the routines
below make reads and writes to the Hospital Location file (#44). The Routines
and Linetags list below describe the access:
Routine: MBAAMDA1 reads and writes from/to the Hospital Location file (#44) in
order to make and cancel appointments.
Linetags:
1. GETCLNX makes a FileMan read of the Hospital Location file (#44) to see if
a clinic exists.
2. GETPATT does a FileMan read of the ^SC(D0,"ST" node to get the clinic
availability for a specified date.
3. GETSCAP does a direct global read of the ^SC(D0,"S" node to get clinic
appointment information for a specific patient and date/time.
4. GETCAPT does a FileMan read to get appointment data for a patient. Fields
read are: Patient (.01), Length of Appointment (1), Other (3), Data Entry
Clerk (7), Date Appointment Made (8), OverBook (9), Eligibility (30),
Checked-in (309), Check in User (302), Checked Out (303), Check Out User
(304), Check Out Entered (306), Consult Link (688)
5. LOCKST locks the ^SC(D0,"ST" node for a specified date prior to record for
an appointment.
6. UNLCKST unlocks the ^SC(D0,"ST" node for a specified date after updating
the record for an appointment.
7. LOCKS locks the ^SC(D0,"S" node for a specific date/time in order to enter
a new appointment.
8. UNLCKS unlocks the ^SC(D0,"S", node for a specific date/time after an
appointment record has been created.
9. SETST uses FileMan to set the ^SC(D0,"ST",Date,1 node in order to set
appointment availability. This call updates fields .01, Pattern Date and 1
Current Availability.
10. MAKE uses UPDATE^DIE to make a clinic appointment in the Hospital Location
file (#44). The Appointment multiple is updated with a new appointment. Fields
that are updated are .01, 1, 3, 7, 8, 10, 688.
The SC("ARAD" cross reference is being hardset in existing SD namespaced
routines. The SDCNP0 routine is hardsetting this cross reference to be equal
to 'N'.
CANCEL updates the Hospital Location file (#44) when an appointment is
canceled:
a. The ^SC("ARAD" cross reference is hard set to "N".
b. The ^SC(D0,"S" node with the appointment record is deleted using
a KILL command.
c. A FileMan read (GETS^DIQ) is used to get the values of the Hour
Clinic Display Begins (#1914) and Display Increments Per Hour
(#1917). These fields are used to calculate the value to be used
to update the Current Availability field in the Pattern multiple
(See d and e below).
d. The value of the ^SC(D0,"ST",Date,1 node is read with a
FileMan read. (Date is the date the appointment is being canceled).
e. The ^SC(D0,"ST",Date/Time,1 node is set using a FileMan write to
the newly calculated Current Availability as calculated when
canceling an appointment. Steps c, d and e are making the
calculations to reset the current availability pattern to recover
the slot that was used when making the appointment.
11. COVERB checks to see if the clinic is overbooked for a specific date/time.
If so, the first overbooking is deleted using a KILL command.
12. GETFSTA gets the first available day for an appointment by reading the
^SC(D0,"T", node.
13. GETDAYA loops through the ^SC(D0,"S" nodes from a beginning date to get
the appointment status and overbooking status for each date/time where an
appointment is booked.
14. GETDST does a direct global read of the ^SC(D0,"ST",Date/Time, 1 node and
returns the current availability status for the date/time.
15. GETDPATT returns the day pattern for a specific date. Does a direct global
read of the ^SC(D0,"ST",date,D1,1) read and returns the data on this node.
16. ADDPATT uses UPDATE^DIE to update the PATTERN multiple for a specific
date.
Routine: MBAAMDA2 makes calls to read data from the Hospital Location file
(#44) to get information in order to make or cancel appointments.
Linetags: SLOTS does a FileMan read of the ^SC(D0,"ST" node for a clinic to
get the .01, Pattern Date and 1, Current Availability fields. Returns all
nodes for the clinic in the RETURN array.
Routine MBAAMDA4 makes calls to read and update the Hospital Location file
(#44) in order to make or cancel appointments.
Linetag:
1. UPDCAPT uses UPDATE^DIE to update the APPOINTMENT multiple for a new
appointment.
2. GETCAPT does a direct global read of the ^SC(D0,"S",Appointment Date/Time
to check if the appointment exists. If it exists, uses an EN^DIQ call to read
the appointment record. Fields that are read are Patient (.01), Length of
Appointment (1), Other (3), Data Entry Clerk (7), Date Appointment Made (8),
OverBook (9), Eligibility (30), Checked-in (309), Check in User (302), Checked
Out (303), Check Out User (304), Check Out Entered (306)
Routine MBAARPC1 In linetag PROVCLIN a direct global read is made to the
^SC(D0,"PR" to get the pointer to the NEW PERSON file (#200) for each Provider
that is associated with the specified clinic.
Routine MBAARPC2 makes direct global reads of the HOSPITAL LOCATION file (#44)
to read appointment information.
Linetag:
1. CLNDATA does a FileMan read of the ^SC(D0,0 node to get fields, STOP CODE
NUMBER (8), TREATING SPECIALTY (9.5), CREDIT STOP CODE (2503).
2. RECALL does a FileMan read to check to see if the Clinic ID entered exists
in the Hospital Location file (#44).		 2015/03/23
6045 MBAA Access to SD(403.5 File SCHEDULING 2014/04/22 APPROVED Active Private 403.5
The Scheduling Calendar View RPCs and code accesses the
Recall Reminders file (#403.5) to read recall data. The RPCs are the MBAA
RECALL BY FACILITY LIST and MBAA RECALL LIST BY PATIENT.
Routine MBAARPCL reads the Recall Reminders file (#403.5) to get the data
necessary to provide the facility Recall Reminders List and a Recall Reminders
List by patient.
Linetags:
RECALL does a FileMan read of the ^SD(403.5 file to get fields Patient Name
(.01), Clinic (4.5), Accession (2), Test/App (3), Provider (4), Recall Date
(5), Comment (2.5), Fast/Non-Fasting (2.6), Length of Appt (4.7), Date
Reminder Sent (6), User Who Entered Recall (7), Recall Date (Per Patient)
(5.5), Second Print (8).
RCLDFN does a FileMan read of the ^SD(403.5 file to get fields Patient Name
(.01), Clinic (4.5), Accession (2), Test/App (3), Provider (4), Recall Date
(5), Comment (2.5), Fast/Non-Fasting (2.6), Length of Appt (4.7), Date
Reminder Sent (6), User Who Entered Recall (7), Recall Date (Per Patient)
(5.5), Second Print (8).		 2016/06/10
6046 MBAA ACESS TO SDWL(409.3 File SCHEDULING 2014/04/22 APPROVED Active Private 409.3
The Scheduling Calendar View accesses the SD Wait List
file (#409.3) to read and write data in order to provide information about
patients on the Electronic Wait List (EWL) and to update the status of
patients on the EWL in order to remove them from the EWL. The mobile app
verifies the user holds the VistA security key, SDWL MENU prior to allowing
access to the mobile wait list options.
Routine MBAARPC1 reads data using direct global reads to confirm the patient
is on the EWL and then checks the status of the patient on the EWL.
Linetag:
UPDTEWL does a direct global read the ^SDWL(409.3,"B" cross reference to check
to see if the patient is on a EWL. If the patient is on an EWL, a FileMan read
of field 23, Current Status, is made to get the current status of the patient
on the EWL.
Routine MBAARPCL makes direct global reads to the ^SDWL(409.3 file to get EWL
information for a patient or for a facility.
Linetags:
EWL does a direct global read of the ^SDWL(409.3,"B" cross reference to check
to see if the patient is on the EWL. If the patient is on the EWL, it does a
FileMan read of for the Current Status (23), Originating Date (1), Desired
Date of Appointment (22), WL Specific Clinic (8), Priority (10), EWL Enrollee
Status (27), Date Appt. Made (13.1).
FACEWL does a direct global read of data on the ^SDWL(409.3,"B" cross
reference. A FileMan read is made of the Current Status (23) field to see if
the patient's entry is closed. If it is open, then a FileMan read is made to
pull the Originating Date (1), Desired Date of Appointment (22), WL Specific
Clinic (8), Priority (10), EWL Enrollee Status (27), Date Appt. Made (13.1)
fields.
Routine MBAAWLDA locks and unlocks records in the ^SDWL(409.3 file and
Linetags:
LOCK locks ^SDWL(409.3,D0 in order to perform and edit action.
UNLOCK unlocks ^SDWL(409.3,D0 after performing an edit action.
DISP edits Disposition (21), Date Dispositioned (19), Dispositioned By (20),
Current Status (23), Scheduled Date of Appt (13), Date Appt. Made (13.1), Appt
Clinic (13.2), Appt Institution (13.3), Appt Stop Code (13.4), Appt Credit
Stop Code (13.5), Appt Station Number (13.6), Appt Status (13.8), Apt Clerk
(13.7) using a FileMan call.
DISP also uses GET1^DIQ to get WL Specific Clinic. If there is a WL Specific
Clinic, the ^SDWL(409.3, "SC" cross reference for the entry is KILLed.		 2016/08/17
6047 MBAA Access to SDWL(409.32 File SCHEDULING 2014/04/22 APPROVED Active Private 409.32
ICR 6047 MBAA Access to SDWL(409.32.
The Scheduling Calendar View application access the SD WL Clinic Location file
(#409.32) to get the WL Clinic. The MBAA RPCs, MBAA WAIT LIST BY DFN and MBAA
FACILITY WAIT LIST makes this call to the file.
Routine MBAARPCL does a FileMan read of the SD WL CLINIC LOCATION File for the
specified record to get the Clinic field (.01) in external format.
Linetag:
EWL does a FileMan read of the SD WL CLINIC LOCATION File for the specified
record to get the Clinic field (.01) in external format. (RPC: MBAA WAIT LIST
BY DFN)
FACEWL does a FileMan read of the SD WL CLINIC LOCATION File to get the Clinic
field (.01) in external format. (RPC: MBAA FACILITY WAIT LIST)		 2015/02/26
6048 MBAA SDAMEVT API CALLS Routine SCHEDULING 2014/04/23 APPROVED Active Private
The Scheduling Calendar View application uses APIs in
the SDAMEVT routine to handle scheduling events.
API:
CANCEL^SDAMEVT - This API is used to log or trigger events when an appointment
is canceled. The API is called from routines MBAAMAP2 and MBAARPC2 and the RPC
is MBAA CANCEL APPOINTMENT.
MAKE^SDAMEVT - This API is used to log or trigger events when an appointment
is made. The API is called from routine MBAAMAP2 and the RPC is MBAA
APPOINTMENT MAKE.		 SDAMEVT 2015/02/24
6049 MBAA SDMANA API USE Routine SCHEDULING 2014/04/23 APPROVED Active Private
The Scheduling Calendar View application uses the
NAVA^SDMANA API to compute the next available indicator when making an
appointment.
Routine MBAAMAP2 calls this API when making an appointment. MBAAMAP2 is called
by the MBAA APPOINTMENT MAKE RPC.		 SDMANA 2015/01/05
6050 MBAA SDQQCN2 API Routine SCHEDULING 2014/04/23 APPROVED Active Private
The Scheduling Calendar View package uses the
SCH^SDQQCN2 API to schedule and change the status of a consult when an
appointment is made for the consult request.
Routine MBAAAPI1 calls this API when making an appointment.		 SDQQCN2 2016/06/09
6051 MBAA use of SDWLE6 API Routine SCHEDULING 2014/04/23 Withdrawn Private
The Scheduling Calendar View RPC, MBAA REMOVE FROM EWL
uses the DIS^SDWLE6 API to disposition an EWL entry when removing a patient
from the SD EWL. Prior to allowing a user to access the EWL options, the
software checks to be sure the user holds the SDWL MENU security key.
Routine MBAAWLAP calls the API in order to update the disposition of the EWL
entry. DIS^SDWLE6 updates the status of the specified entry on the Electronic
Wait List (EWL) to remove (Status of Closed) the patient from the EWL. The API
also checks to see if the patient is in the SDWL TRANSFER ACCEPT FILE
(#409.36). If the patient is in the file, a message is sent to the
S.SDWL-XFER-SERVER at the facility indicated in the SDWL TRANSFER ACCEPT FILE. 		SDWLE6
6054 MBAA USE OF SDAM2 API Routine SCHEDULING 2014/04/24 APPROVED Active Private
The Scheduling Calendar View application makes a call
to the API INP^SDAM2 from MAKE^MBAAMAP2 when scheduling an appointment for a
patient to check the inpatient status of the patient.
The SDAM2 API will be used by the MBAA APPOINTMENT MAKE RPC.		 SDAM2 2014/12/31
6064 MBAA ACCESS TO SCTM(404.57 File SCHEDULING 2014/06/04 APPROVED Active Private 404.57
The Scheduling Calendar View application is doing a
FileMan read of the ^SCTM(404.57 file for the specified record to check for
the existence of the record in the file. This check is to make sure the team
position exists in the file. If the position doesn't exist in the file an
error message is return to the calling application and the RPC stops
execution.
This is a data validation check to be sure the data that will be filed when
making a new entry for the Electronic Wait List is valid data. The record in
the file pointed to actually exists. This insures there will not be a broken
pointer when the new record is created.		 2015/01/30
6137 APPT CANCEL REMARKS File SCHEDULING 2014/11/26 APPROVED Active Controlled Subscription 2.98
VPS returns a patient's outpatient clinic appointment
status to Vetlink. The outpatient clinic appointment information returned
includes the cancellation remarks obtained from the APPOINTMENT sub-file 2.98,
field 17.		 2015/01/06
6150 VPS READ OF 403.5 File SCHEDULING 2015/01/26 APPROVED Active Controlled Subscription 403.5
This IA provides for the Fileman read of the PATIENT
NAME, TEST/APP, PROVIDER, CLINIC, RECALL DATE fields in the RECALL REMINDERS
file #403.5.		 2015/04/07
6158 MBAA Read Access to Recall Reminders Providers File File SCHEDULING 2015/02/12 Withdrawn Private 403.54
The Scheduling Calendar View Mobile App (MBAA
namespace) needs to read the Recall Reminders Providers File (#403.54) to look
up what security keys are required for a provider to use the recall reminders.
This is used by the MBAA RPC MBAA REMOVE FROM RECALL LIST, in routine
MBAARPC1, line tag REMREC. A FileMan read is made to the file to get the
security key (Field #6, KEY) needed for a user to enter or edit a recall
reminder for the specified provider.
6181 $$FIND API in SDAM2 Routine SCHEDULING 2015/03/18 Withdrawn Private
To support delivery of the Insurance Verification
Processor (IVP) project, which is part of Integrated Billing application,
access to the API $$FIND^SDAM2() is requested in order to find all the
appointments for a patient on a given date.
The input data will be 3 required data elements as follows: the patient's DFN,
date/time of the appointment (FileMan format), and the clinic's internal entry
number (IEN). The data of the input will be determined by the IVP software
based on the IVP Daily Appointment Worklist information. This API is called
by IVP code to get IEN of the sub file (#44.003), which is required to call
SDAMEVT APIs and to update the appointment entry properly.
Data input: 3 variables defined as follows: DFN - Patient's IEN from PATIENT
file (#2) SDT - Date/Time for the appointment in the File Man format SDCL -
clinic IEN from the HOSPITAL LOCATION FILE (#44)
Data output ($$FIND return value): If 0, no appointment was found and the
patient is notified. If > 0, then applicable appointment for that day is
passed back as IEN of the sub file (#44.003) of the sub file (#44.001) of the
file (#44).		 SDAM2
6182 Update fields (#309) and (#302) in file #44 File SCHEDULING 2015/03/18 Withdrawn Private 44
To support delivery of the Insurance Verification
Processor (IVP) project, which is part of Integrated Billing application,
access to the fields (#309) and (#302) in the file #44 is requested in order
to check-in the patient for a given appointment. Both fields (#309)
CHECKED-IN and (#302) CHECK IN USER of the file (#44) will be updated by the
FileMan call, which is made by IVP RPC "IBVP CHECKIN APPOINTMENT " at the
time when IVP user check in the patient in IVP web application.
6183 SDAMEVT APIs Routine SCHEDULING 2015/03/18 Withdrawn Private
The APIs will are used by IB to check-in the patient
from the Insurance Verification Processor's GUI interface via IB RPC "IBVP
CHECKIN APPOINTMENT " call. The IB RPC will use HDLKILL^SDAMEVT,
BEFORE^SDAMEVT, HANDLE^SDAMEVT, AFTER^SDAMEVT, and EVT^SDAMEVT APIs to ensure
that all other processes requiring notification of the check-in activity are
notified.		 SDAMEVT
6232 APPT MULTIPLE 2.98 READ/WRITE File SCHEDULING 2015/09/29 Withdrawn Controlled Subscription 2.98
VA Point of Service (Kiosks) (VPS) allows Veterans to
Make and Cancel clinic appointments using the VetLink Kiosk. This ICR provides
read/write access to the APPOINTMENT SUB-FILE #2.98 defined in the PATIENT
file (2). The sub-file contains patient appointment data such as clinic,
appointment date/time and reason for the appointment to be captured.
6233 READ/WRITE TO HOSPITAL LOCATION file (#44) File SCHEDULING 2015/09/29 Withdrawn Controlled Subscription 44
VA Point of Service (Kiosks) (VPS) allows Veterans to
Make and Cancel clinic appointments using the VetLink Kiosk. This ICR provides
read/write access to the subfiles 44.001, 44.003, and 44.005 of the HOSPITAL
LOCATION file (#44).
6297 USAGE OF SCHEDULING ENTRY POINT Routine SCHEDULING 2015/12/10 Withdrawn
VPS CANCEL APPOINTMENT RPC calls the CANCEL^SDCNSLT
entry point when an appointment is cancelled with the Vetlink Kiosk
application. The Vetlink Kiosk application provides the veteran Scheduling
functionality via the KIOSKS located at VA Medical Centers. The
CANCEL^SDCNSLT is a pre-existing procedure that is called to update the
consult as part of the processing of the CANCEL APPOINTMENT action located on
Appt Mgt Module screen associated with the Appointment Management [SDAM APPT
MGT] option.
If a consult link exists, determined at ^SC(D0,S,D1,1,D2,CONS), then VPS KIOSK
application will need to call the CANCEL^SDCNSLT entry point to support the
Scheduling Consult Appointment linkage functionality. 		SDCNSLT
6355 SCMC PATIENT TEAM CHANGES Other SCHEDULING 2016/02/12 Retired Controlled Subscription
The Electronic Health MGMT Platform (HMP) is modifying
the SCMC PATIENT TEAM CHANGES Protocol to add the HMP PCMM TEAM POSTION
Protocol as an Item to the SCMC PATIENT TEAM CHANGES Protocol. Adding the HMP
PCMM TEAM POSITION as an Item will trigger a sync action between VistA and JDS
whenever the Patient Team Assignment File (#404.42) is updated.
**********************************************************************
This ICR was retired as of 10/27/17 when HMP was shut down. HMP*2.0*12
released on 10/17/17 is an informational patch outlining the steps for the
sites to shut down the application. If HMP is reactivated in the future, the
HMP project team should review the access provided by this ICR with the
custodial application before the ICR is reactivated.
If HMP is reactivated in the future, this ICR should be discussed with PCMM
Web team to confirm the HMP protocols attached to the SCMC PATIENT TEAM
CHANGES and SCMC PATIENT TEAM POSITION CHANGES protocols provide the necessary
data for HMP.
**********************************************************************
6356 SCMC PATIENT TEAM POSITION CHANGES Other SCHEDULING 2016/02/12 Retired Controlled Subscription
The Enterprise Health MGMT Platform (HMP) is adding the
HMP PCMM TEAM POSITION Protocol as an Item under the SCMC PATIENT TEAM
POSITION CHANGES Protocol. The HMP PCMM TEAM POSITION Protocol will trigger a
sync action between VistA and JDS whenever the Patient Team Position
Assignment File (#404.43) is updated.
**********************************************************************
This ICR was retired as of 10/27/17 when HMP was shut down. HMP*2.0*12
released on 10/17/17 is an informational patch outlining the steps for the
sites to shut down the application. If HMP is reactivated in the future, the
HMP project team should review the access provided by this ICR with the
custodial application before the ICR is reactivated.
If HMP is reactivated in the future, this ICR should be discussed with PCMM
Web team to confirm the HMP protocols attached to the SCMC PATIENT TEAM
CHANGES and SCMC PATIENT TEAM POSITION CHANGES protocols provide the necessary
data for HMP.
**********************************************************************
6359 HMP USE OF STATUS~SDAMA308 Routine SCHEDULING 2016/02/18 APPROVED Retired Controlled Subscription
The Enterprise Health MGMT Platform (HMP) requests to
use the STATUS^SDAMA308 API in order to retrieve the status of a patient
appointment.
HMP is retrieving this information along with other information about a
patient's appointments and syncing this data with the HMP JDS database system.
This is a temporary agreement until the HMP application can switch from using
STATUS~SDAMA308 to SDAPI~SDAMA301 documented in ICR #4433. Expiration date is
set for 1/1/17.
10/24/17-ICR has been retired and expiration date changed to 6/16/17 to match
the release date for HMP*2.0*3. The patch description references DE4469 and
use of SDAMA308 API. Search of HMP routines found a commented line at
SDAM1+12 in routine HMPDJ04 noting the change from SDAMA308 API to supported
SDAMA301 API (ICR #4433). No other reference to routine SDAMA308 in HMP
routines. HMP will be shutdown as of 10/27/17. If HMP is reactivated in the
future and this ICR is needed, the ICR should be reviewed by the custodial
application for approval.		 SDAMA308 2016/04/20
6370 HMP ACCESS TO SC( File SCHEDULING 2016/02/23 Withdrawn Controlled Subscription 44
The Enterprise Health MGMT Platform (HMP) is accessing
the Hospital Location file (#44) to retrieve a list of all active clinics. HMP
builds a list containing the IEN for the entry and the Name (.01). HMP loops
thru the B cross reference to get each entry, then checks the Type field (2)
and if the location is designated as a clinic it is added to the list. This
list is then synced with the HMP JDS database.
6396 HMP ACCESS TO SCTM(404.51 File SCHEDULING 2016/03/18 APPROVED Retired Private 404.51
The Enterprise Health MGMT Platform (HMP) requests
permissions to do a direct global read of the TEAM File (#404.51) to retrieve
the Name (.01) and Team Phone Number (.02) from the file. HMP uses this data
as part of the sync process that syncs the local VistA data with the HMP JDS
data system.
**********************************************************************
This ICR was retired as of 10/27/17 when HMP was shut down. HMP*2.0*12
released on 10/17/17 is an informational patch outlining the steps for the
sites to shut down the application. If HMP is reactivated in the future, the
HMP project team should review the access provided by this ICR with the
custodial application before the ICR is reactivated. See VistA Document
Library (VDL) for list of retired HMP ICRs.
*********************************************************************		 2016/04/07
6402 HMP ACCESS TO FILE 404.42 File SCHEDULING 2016/04/08 Retired Private 404.42
The Enterprise Health Management Platform (HMP) uses a
FileMan read to retrieve the Patient assigned to a Team from the PATIENT TEAM
ASSIGNMENT FILE (#404.42).
**********************************************************************
This ICR was retired as of 10/27/17 when HMP was shut down. HMP*2.0*12
released on 10/17/17 is an informational patch outlining the steps for the
sites to shut down the application. If HMP is reactivated in the future, the
HMP project team should review the access provided by this ICR with the
custodial application before the ICR is reactivated.
There are APIs available for PCMM data but HMP was not able to convert to use
an API prior the the shut down of HMP on 10/27/17. HMP requested temporary
approval of this ICR to give the project team time to convert to an API and to
work with the PCMM Web team to identify the best path for retrieving data with
the current and web version of PCMM.
If HMP is reactivated in the future, the HMP project team will need to work
with the PCMM/Scheduling teams to resolve this issue and decide if this ICR is
needed.
**********************************************************************
6412 HMP Access to TPPR~SCAPMC Routine SCHEDULING 2016/05/25 APPROVED Retired Controlled Subscription
The Enterprise Health Management Platform (HMP) makes a
call to the TPPR^SCAPMC API to retrieve all the positions for a practitioner.
**********************************************************************
This ICR was retired as of 10/27/17 when HMP was shut down. HMP*2.0*12
released on 10/17/17 is an informational patch outlining the steps for the
sites to shut down the application. If HMP is reactivated in the future, the
HMP project team should review the access provided by this ICR with the
custodial application before the ICR is reactivated. See VistA Document
Library (VDL) for list of retired HMP ICRs.
*********************************************************************		 SCAPMC 2017/08/09
6417 SCV ACCESS TO DATP~SDWLEVAL Routine SCHEDULING 2016/06/01 APPROVED Active Controlled Subscription
The Scheduling Calendar View Mobile App (MBAA) calls
the DATP^SDWLEVAL API to retrieve specific appointment data for a patient.		 SDWLEVAL 2016/06/10
6418 SCV ACCESS TO CHKENC~SDWLQSC1 API Routine SCHEDULING 2016/06/01 APPROVED Active Controlled Subscription
This API checks for any encounters for a patient and
returns encounter data.		 SDWLQSC1 2016/06/10
6474 PATIENT APPOINTMENT File SCHEDULING 2016/08/23 Withdrawn Private 44
VIA needs to read File #44, field #1900 (sub-file
#44.001) to provide data to consuming applications via a remote procedure call
(RPC).
6594 HOSPITAL LOCATION FILE ACCESS File SCHEDULING 2016/11/03 APPROVED Active Private 44
The Advanced Prosthetics Acquisition Tool (APAT) checks
the HOSPITAL LOCATION File (#44) to obtain the location name, to determine if
the clinic is non-count, and to check the stop code number.		 2018/07/26
6744 DBIA6744 Routine SCHEDULING 2017/03/14 APPROVED Active Private
Registration version 5.3 uses entry point $$PCMMXMY to
build xmy array for the appropriate type of PCMM message. 		SCAPMC25 2017/03/30
6745 DBIA6745 Routine SCHEDULING 2017/03/14 APPROVED Active Private
Registration Version 5.3 uses API call $$PCMAIL^SCMCMM
to load standard patient centered information into a mail message.		 SCMCMM 2017/03/30
6769 SD RECEIVE OR Protocol Other SCHEDULING 2017/06/20 APPROVED Active Private
This agreement grants permission to Order Entry /
Result Reporting to use the protocol in order to send appointment requests to
Scheduling.		 2017/08/23
6805 SC PATIENT LOOKUP Routine SCHEDULING 2017/07/24 Pending Private
This ICR allows the return of patient information using
a lookup value.		 SCUTBK11
6822 OUTPATIENT ENCOUNTER LOOKUP Routine SCHEDULING 2017/09/14 Pending Private
OUTPATIENT ENCOUNTER LOOKUP will allow the DSS CyberREN
to take patient, appointment date/time, hospital location, as well as visit
file pointer and return all outpatient encounter IENs matching the given
criteria.		 SDVSIT2
6872 CLV BYPASS PARAMETER Routine SCHEDULING 2018/02/04 Withdrawn Supported
This supported DBIA covers an API that will return a
value that indicates whether a patient should be asked for Camp Lejeune
eligibility.
The master value is stored in the PARAMETER DEFINITION file (#8989.51) in the
SD CLV BYPASS PARAMETER entry.
The business side requirements included a parameter to be installed and
implemented across the board for the Camp Lejeune project. They do not want
ANY package to display Camp Lejeune information AT ALL if this master value is
ON. This IA will allow packages to call this API and determine if the
parameter is enabled.		 SDCLVMN
6903 PCE USAGE OF FILE 409.4 Routine SCHEDULING 2018/03/29 Pending Controlled Subscription 409.4
The Patient Care Encounter (PCE) has authority to use
the BYPASS ACTION REQUIRED LOG file (# 409.4).
An API is used to call routine BYPASS^SDCLVMN(PXUPAT,PXUHLOC,PXUDT,PXUTLVST)
to file the data into the BYPASS ACTION REQUIRED LOG file #409.4.		 SDCLVMN
6934 ENCOUNTER FILE XREF BY PATIENT/DATE File SCHEDULING 2018/06/19 APPROVED Active Controlled Subscription 409.68
This integration agreement is needed to determine
whether an appointment made using the mobile scheduling application by either
the veteran or staff is considered a follow-up appointment.		 2018/06/20
6946 SDMXCORE Routine SCHEDULING 2018/07/27 Pending Private
Core tags for MASS project.		 SDMXCORE
6947 SDMXERRO Routine SCHEDULING 2018/07/27 Pending Private
Outgoing Error Interface tags.		 SDMXERRO
6950 SDMXLKRQ Routine SCHEDULING 2018/08/01 Pending Private
Locking and Resequencing Tags.		 SDMXLKRQ
6978 VPR ACCESS TO APPOINTMENTS File SCHEDULING 2018/10/22 APPROVED Active Private 2.98
This agreement allows VPR to access fields in the
APPOINTMENT sub-file #2.98 that are not provided by the supported Scheduling
APIs.		 2018/10/26
7012 SCMC PATIENT TEAM CHANGES Other SCHEDULING 2019/01/24 APPROVED Active Controlled Subscription
The SCMC PATIENT TEAM CHANGES protocol is fired off
whenever the Patient Team Assignment File (#404.42) is updated.
This agreement documents the protocols allowed to subscribe to this event.
Supported HL7 utilities may be used to read the attached message; the message
itself and HL7 application variables may not be altered.		 2021/08/26
7013 SCMC PATIENT TEAM POSITION CHANGES Other SCHEDULING 2019/01/24 APPROVED Active Controlled Subscription
The SCMC PATIENT TEAM POSITION CHANGES protocol is
fired off whenever the Patient Team Position Assignment file (#404.43) is
updated.
This agreement documents the protocols allowed to subscribe to this event.
Supported HL7 utilities may be used to read the attached message; the message
itself and HL7 application variables may not be altered.		 2019/02/04
7058 Make Appointment API Routine SCHEDULING 2019/04/25 APPROVED Active Controlled Subscription
Making an appointment impacts several files in all
cases (e.g., Patient, Location, SDEC Appointment) and others in specific cases
(e.g., Consult). This ICR describes the scheduling API that can be used by
non-scheduling applications to make appointments.
Note: Subscribing applications that want to invoke this API using the SDEC
APPADD RPC can subscribe to the appropriate controlled ICR (#7059).		 SDEC07 2022/11/23
7059 SDEC APPADD Remote Procedure SCHEDULING 2019/04/25 Under Revision Controlled Subscription
RPC used to add a new appointment for a patient.
For further information including a description of the inputs and outputs, see
ICR #7058.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC APPADD 2022/11/23
7064 Cancel Appointment API Routine SCHEDULING 2019/05/06 APPROVED Active Controlled Subscription
Cancelling an appointment impacts several files in all
cases (e.g., Patient, Location, SDEC Appointment) and others in specific cases
(e.g., Consult). This ICR describes the scheduling API that can be used by
non-scheduling applications to cancel appointments.
Note: Subscribing applications that want to invoke this API using the SDEC
APPDEL RPC can subscribe to the appropriate controlled ICR (#7065).		 SDEC08 2020/05/04
7065 SDEC APPDEL Remote Procedure SCHEDULING 2019/05/06 Under Revision Controlled Subscription
RPC used to cancel an appointment for a patient.
For further information including a description of the inputs and outputs, see
ICR #7064.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC APPDEL 2021/11/01
7066 Check-In API Routine SCHEDULING 2019/05/07 APPROVED Active Controlled Subscription
Checking in an appointment impacts several files -
Location, SDEC Appointment. This ICR describes the scheduling API that can be
used by non-scheduling applications to check in appointments.
Note: Subscribing applications that want to invoke this API using the SDEC
CHECKIN RPC can subscribe to the appropriate controlled ICR (#7067).		 SDEC25 2021/11/01
7067 SDEC CHECKIN Remote Procedure SCHEDULING 2019/05/07 Under Revision Controlled Subscription
RPC used to check an appointment in.
For further information including a description of the inputs and outputs, see
ICR #7066.		 SDEC CHECKIN 2021/11/01
7068 Check out appointment Routine SCHEDULING 2019/05/08 Withdrawn Controlled Subscription
Checking a patient out for an appointment impacts
several files - Location, SDEC Appointment. This ICR describes the scheduling
API that can be used by non-scheduling applications to check out appointments.
Note: Subscribing applications that want to invoke this API using the SDEC
CHECKOUT RPC can subscribe to the appropriate controlled ICR (#7069).		 SDEC25
7069 SDEC CHECKOUT Remote Procedure SCHEDULING 2019/05/08 Withdrawn Controlled Subscription
RPC used to check out an appointment.
For further information including a description of the inputs and outputs, see
ICR #7068.		 SDEC CHECKOUT
7070 Available Slots API Routine SCHEDULING 2019/05/08 Pending Controlled Subscription
Returns list of slots set up for a clinic for a date
range along with their availability.		 SDEC57
7071 SDEC APPSLOTS Remote Procedure SCHEDULING 2019/05/08 APPROVED Active Controlled Subscription
RPC used to return list of appointment slots for a
clinic associated with a resource. For a list of inputs and outputs, see ICR
#7070.		 SDEC APPSLOTS 2019/09/13
7072 Cancel Appointment Check-Out API Routine SCHEDULING 2019/05/08 Withdrawn Controlled Subscription
Cancels appointment check-out and updates the
appropriate scheduling files.		 SDEC25
7073 SDEC CANCKOUT Remote Procedure SCHEDULING 2019/05/08 Withdrawn Controlled Subscription
RPC used to cancel check out for an appointment. For a
list of inputs and outputs, see ICR #7072.		 SDEC CANCKOUT
7074 No-Show Appointment API Routine SCHEDULING 2019/05/09 APPROVED Active Controlled Subscription
Marks appointment as no show or cancels no show and
updates the relevant files. Also executes the event triggers.		 SDEC31 2022/11/17
7075 SDEC NOSHOW Remote Procedure SCHEDULING 2019/05/09 APPROVED Active Controlled Subscription
RPC used to no show an appointment.
See ICR #7074 for a description of the input and output parameters.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC NOSHOW 2022/11/23
7076 Clinic schedule API Routine SCHEDULING 2019/05/15 Pending Controlled Subscription
Returns appointments scheduled for a set of resources.		 SDEC02
7077 SDEC CRSCHED Remote Procedure SCHEDULING 2019/05/15 Pending Controlled Subscription
RPC that returns appointments scheduled for a set of
resources. See ICR #7076 for a list of inputs and outputs.		 SDEC CRSCHED
7080 Appointment List for a Patient API Routine SCHEDULING 2019/05/22 Pending Controlled Subscription
Returns a list of appointments for a patient for a date
range. List may be all or only ancillary (Lab, X-ray, EKG) appointments.		 SDEC50
7081 SDEC FAPPTGET Remote Procedure SCHEDULING 2019/05/22 Pending Controlled Subscription
RPC that returns a list of appointments for a patient
for a date range. See ICR #7080 for a list of inputs and outputs.		 SDEC FAPPTGET
7082 Clinic Schedule - Slot Availability API Routine SCHEDULING 2019/05/30 Pending Controlled Subscription
Returns the slot counts for the clinic associated with
a resource for a date range.		 SDEC57
7083 SDEC APPSLOTS Remote Procedure SCHEDULING 2019/05/30 Pending Controlled Subscription
Returns the slot counts for the clinic associated with
a resource for a date range.
See ICR #7082 for a list of inputs and outputs.		 SDEC APPSLOTS
7110 EDIT SDAM PCE EVENT PROTOCOL Other SCHEDULING 2019/11/27 APPROVED Active Private 2024/08/21
7174 TEAM POSITION PROVIDER CHANGES File SCHEDULING 2020/05/11 APPROVED Active Private 404.52
Patch VPR*1*28 will use CREIXN^DDMOD to add a new
regular 'ADP' index to the POSITION ASSIGNMENT HISTORY (#404.52) file, to sort
assignments by Effective Date and Team Position. This cross reference will be
used by VPR to track PCMM team position provider changes to keep VPR and PCMM
synchronized.
This agreement permits the VPR application to create the new index and use it
in a nightly job to find position assignments that have changed that day.		 2021/12/09
7192 DETERMINE FOLLOW-UP Routine SCHEDULING 2020/08/31 Pending Private
The DSS Electronic Dental Record Manager (EDRM)
application is creating Dental appointments for the Cerner Millennium
integration. Millennium sends an SIU^S14 HL7 message when a Veteran checks in
to the Dental Clinic. The HL7 message allows Dental users to select a VistA
appointment that matches the Millennium Encounter. The HL7 message also
contains necessary encounter data to be returned to Millennium when filing
vital signs, notes and encounter procedures/diagnoses so that the records are
applied to the correct Millennium encounter.
The PTFU API returns the follow-up visit indicator to be filed into the
FOLLOW-UP VISIT (#28) field of the APPOINTMENT (#2.98) subfile of the PATIENT
(#2) file.		 SDM0
7193 NEW APPOINTMENT STATUS Routine SCHEDULING 2020/08/31 Pending Private
The DSS Electronic Dental Record Manager (EDRM)
application is creating Dental appointments for the Cerner Millennium
integration. Millennium sends an SIU^S14 HL7 message when a Veteran checks in
to the Dental Clinic. The HL7 message allows Dental users to select a VistA
appointment that matches the Millennium Encounter. The HL7 message also
contains necessary encounter data to be returned to Millennium when filing
vital signs, notes and encounter procedures/diagnoses so that the records are
applied to the correct Millennium Encounter.
The STATUS API determines the status for the new appointments to be fild into
the STATUS (#3) field of the APPOINTMENT (#2.98) subfile of the PATIENT (#2)
file when creating an appointment.		 SDM1A
7201 APPT CANCELLATION REASON TYPE Routine SCHEDULING 2020/09/04 Pending Private
This agreement allows the routine ORMCCORE to call the
routine SDMCGAPT to obtain the cancellation reason and type (in external and
internal format) for a given patient appointment.		 SDMCGAPT
7273 SDEC APPSDGET Remote Procedure SCHEDULING 2021/07/15 APPROVED Active Private
VTEX will use this as part of the CHECK-IN/KIOSK
replacement project. VSIP is the Veteran Scheduling InteroPerability web-based
solution. The SDEC APPSDGET will be used to get the veterans appointments.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC APPSDGET 2021/07/15
7362 SDEC ARCLOSE Remote Procedure SCHEDULING 2022/11/15 APPROVED Active Controlled Subscription
This RPC is due to be deprecated in April of 2023. All
consumers will need to transition to the appropriate Enterprise Appointment
Service (EAS) web service to replace this functionality by that time
Remove a Patient from the Appointment Requested by setting the STATUS to
CLOSED and updating the DISPOSITION fields.		 SDEC ARCLOSE 2022/12/19
7363 SDEC APPTYPES Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
Return all active Appointment types from the APPOINTMENT TYPE file 409.1
RETURN PARAMETER DESCRIPTION:
Dataset with columns APPTTYPE_IEN and APPTTYPE_NAME
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC APPTYPES 2022/11/23
7364 SDEC ARGET Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC retrieves appointment requests.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC ARGET 2022/12/09
7365 SDEC AROPEN Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC is to re-open an appointment request.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC AROPEN 2022/12/09
7366 SDEC ARSET Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC is to add a new appointment request or update
an appointment request.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC ARSET 2022/12/09
7367 SDEC CANCMT Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC Returns list of cancellation comments (hash
tag, type and text) from the SDEC CANCELLATION COMMENT file (#409.88).
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC CANCMT 2022/12/09
7368 SDEC CANREAS Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC return entries from the CANCELLATION REASONS
file.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC CANREAS 2022/12/09
7369 SDEC CLINSET Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC Returns CLINIC SETUP PARAMETERS for clinics
that are active in the HOSPITAL LOCATION file.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 2022/12/09
7370 SDEC CSLOTSCH Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC retrieves Assigned Appointment Slot Schedule
for a resource.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC CSLOTSCH 2022/12/14
7371 SDEC EDITAPPT Remote Procedure SCHEDULING 2022/11/17 Under Revision Controlled Subscription
This RPC will Edit an appointment (only 'note text' and
appointment length can be edited)
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC EDITAPPT 2022/12/09
7372 SDEC EP EVENT LOG Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC Provides Scheduling Expanded Entry Appointment
Event Log to VSE for displaying in the GUI the VS Gui.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC EP EVENT LOG 2022/12/09
7373 SDEC GETPRER Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC RETURNS ALL ENTRIES IN THE PREREQUISITE
MULTIPLE FROM THE SDEC APPT REQUEST FILE
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC GETPRER 2022/12/09
7374 SDEC NEWPERS Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC return entries from the NEW PERSON table 200
that are 'active' AND have PROVIDER CLASS defined.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC NEWPERS 2022/12/09
7375 SDEC PCSTGET Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC GET patient clinic status for a clinic stop
for a given time frame - has the patient been seen by the given Clinic Stop
code in the past 24 months
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC PCSTGET 2022/12/09
7376 SDEC REP1GET Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC will GET clinic data for report.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC REP1GET 2022/12/09
7377 SDEC RESCE Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC Returns all active Clinics/Scheduling
resources
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC RESCE 2022/12/09
7378 SDEC RESOURCE Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC Returns Recordset with ALL RESOURCE names.
Inactive RESOURCES are NOT filtered out.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC RESOURCE 2022/12/09
7379 SDEC RESGPUSR Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
PC Returns ADO Recordset with all ACTIVE GROUP/RESOURCE
combinations to which user has access based on entries in SDEC RESOURCE USER
file If SDECDUZ=0 then returns all ACTIVE GROUP/RESOURCE combinations for
current DUZ If user SDECDUZ possesses the key SDECZMGR then ALL ACTIVE
resource group names are returned.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC RESGPUSR
7380 SDEC VVC_APPT Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
If an appointment is for a VVC clinic, return the URL
of the VVC Web app. The NATIONAL entry in the SDEC Settings file (#409.98)
stores the stop code that identifies a VVC clinic in field #5 (VVC Clinic Stop
Code). If the stop code for the clinic associated with the resource scheduled
for the appointment equals this stop code, the RPC returns the value in field
#6 VVC APP URL of the NATIONAL entry in the SDEC Settings file.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC VVC_APPT 2022/12/09
7381 SDEC VVS DELETE ID Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC deletes the Video Visit ID from the SDEC
APPOINTMENT (#409.84) file.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC VVS DELETE ID 2022/12/09
7382 SDEC VVS GET ID Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC returns the Video Visit Service (VVS) ID.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC VVS GET ID 2022/12/09
7383 SDEC VVS SAVE ID Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC saves the VVS appointment ID in the SDEC
APPOINTMENT (#409.84), field (#2).
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC VVS SAVE ID 2022/12/09
7384 SDECLK LOCK Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC attempts to lock a request record. Request
records are in one of these files:
SDEC APPT REQUEST
REQUEST/CONSULTATION
SD WAIT LIST
RECALL REMINDERS
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDECLK LOCK 2022/12/09
7385 SDECLK UNLOCK Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC unlocks the request record that was locked
using SDECLK LOCK.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDECLK UNLOCK 2022/12/09
7386 SDEC57 OBM Remote Procedure SCHEDULING 2022/11/17 APPROVED Active Controlled Subscription
This RPC will GET overbook status and return message.
This RPC is due to be deprecated in April of 2023. All consumers will need to
transition to the appropriate Enterprise Appointment Service (EAS) web service
to replace this functionality by that time.		 SDEC57 OBM 2022/12/09
7452 SDEC APPADD Remote Procedure SCHEDULING 2024/01/17 Pending Private
The SwitchLane Periopt application is calling the code
for the SDEC APPADD RPC in order to schedule dental appointments.		 SDEC APPADD
7453 SDEC APPDEL Remote Procedure SCHEDULING 2024/01/17 Pending Private SDEC APPDEL
7530 Add New Disability Conditions File SCHEDULING 2025/03/25 APPROVED Active Private 31
This ICR allows new diagnosis codes (DX CODE) and NAME
fields to be added to the Disability Condition (#31) file. Implementation of
patch DG*5.3*1138, provides a mechanism to update the Disability Conditions
(#31) file. When disability conditions (NAME and DX CODE) are encountered
while parsing inbound HL7 messages, but the codes are missing from the
Disability Conditions (#31) file, then Registration is authorized to add those
disability conditions and diagnosis codes to the Disability Conditions (#31)
file.		 2025/03/25
10040 HOSPITAL LOCATION FILE File SCHEDULING APPROVED Active Supported 44
10041 SDACS Routine SCHEDULING 2003/04/03 Retired Controlled Subscription SDACS
10042 SDM Routine SCHEDULING APPROVED Active Supported SDM