Global: ^IBD(357.96

FileMan FileNo	FileMan Filename	Package
357.96	ENCOUNTER FORM TRACKING	Automated Information Collection System

Package	Total	Routines
Automated Information Collection System	26	IBDF18C IBDF18E IBDF18E0 IBDF18E2 IBDF2A IBDF2F1 IBDFBK1 IBDFBK2 IBDFBKR IBDFDE IBDFDE5 IBDFDE6 IBDFDE7 IBDFDE8 IBDFDEA IBDFFRFT IBDFFT1 IBDFN11 IBDFOSG1 IBDFPCE IBDFPRG1 IBDFRPC3 IBDFRPC4 IBDX96 IBDX961 IBDX97

Package	Total	Routines
Automated Information Collection System	10	IBDF18C IBDF1B3 IBDF2F1 IBDFDE5 IBDFDE6 IBDFDEA IBDFM1 IBDFPCE IBDX96 IBDX97

Package	Total	FileMan Files
Automated Information Collection System	3	FORM DEFINITION(#357.95)[.04] AICS DATA QUALIFIERS(#357.98)[#357.961(.1)] PACKAGE INTERFACE(#357.6)[#357.961(.03), #357.962(.03)]
Kernel	1	NEW PERSON(#200)[.16, #357.963(.05)]
Registration	1	VA PATIENT(#2)[.02]
Scheduling	1	HOSPITAL LOCATION(#44)[.1]

Fields, Total: 21

Field #	Name	Loc	Type	Details
.01	PRINTED FORM ID	0;1	NUMBER	**********************REQUIRED FIELD********************** INPUT TRANSFORM: `K X` LAST EDITED: `JUL 18, 1994` HELP-PROMPT: `Can not be edited!` DESCRIPTION: Uniquely identifies an instance of a printed encounter form. This is the same as the ien. NOTES: `XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER` CROSS-REFERENCE: `357.96^B` 1)= S ^IBD(357.96,"B",$E(X,1,30),DA)="" 2)= K ^IBD(357.96,"B",$E(X,1,30),DA)
.02	PATIENT	0;2	POINTER TO VA PATIENT FILE (#2)	**********************REQUIRED FIELD********************** VA PATIENT(#2) LAST EDITED: `APR 02, 1996` HELP-PROMPT: `What patient was the form printed for?` DESCRIPTION: The patient that had the appointment. CROSS-REFERENCE: `357.96^C` 1)= S ^IBD(357.96,"C",$E(X,1,30),DA)="" 2)= K ^IBD(357.96,"C",$E(X,1,30),DA) CROSS-REFERENCE: `357.96^APTAP^MUMPS` 1)= S:$P($G(^IBD(357.96,DA,0)),"^",3) ^IBD(357.96,"APTAP",X,+$P(^IBD(357.96,DA,0),"^",3),DA)="" 2)= K ^IBD(357.96,"APTAP",X,+$P($G(^IBD(357.96,DA,0)),"^",3),DA) Cross-reference of all form ids by patient and appointment date/time. Set by both the .02 and .03 fields.
.03	APPOINTMENT	0;3	DATE	INPUT TRANSFORM: `S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X` LAST EDITED: `JUN 27, 1996` HELP-PROMPT: `What was the date/time of the appointment for which the form was printed?` DESCRIPTION: The date/time of the appointment for which the encounter form was printed. CROSS-REFERENCE: `357.96^APTAP1^MUMPS` 1)= S:$P($G(^IBD(357.96,DA,0)),"^",2) ^IBD(357.96,"APTAP",+$P(^IBD(357.96,DA,0),"^",2),X,DA)="" 2)= K ^IBD(357.96,"APTAP",+$P($G(^IBD(357.96,DA,0)),"^",2),DA) Cross-reference of all form ids by patient and appointment date/time. Set by both the .02 and .03 fields. CROSS-REFERENCE: `357.96^D` 1)= S ^IBD(357.96,"D",$E(X,1,30),DA)="" 2)= K ^IBD(357.96,"D",$E(X,1,30),DA) Regular cross-reference for use in looking up an encounter form tracking entry by date. CROSS-REFERENCE: `357.96^ADATNA1^MUMPS` 1)= S:$P(^IBD(357.96,DA,0),"^",14)'="" ^IBD(357.96,"ADATNA",X,$P(^(0),"^",14),DA)="" 2)= K ^IBD(357.96,"ADATNA",X,+$P(^IBD(357.96,DA,0),"^",14),DA) This mumps cross reference is used to find forms tracking entries not associated with a schedule appointment by date/time.
.04	FORM TYPE	0;4	POINTER TO FORM DEFINITION FILE (#357.95)	FORM DEFINITION(#357.95) LAST EDITED: `OCT 04, 1995` HELP-PROMPT: `What FORM DEFINITION TABLE is associated with the printed encounter form?` DESCRIPTION: If the encounter form has a FORM DEFINITION TABLE, this field points to it. The pointer equals the .01 field of the FORM DEFINITION TABLE entry and is used as the form type id. CROSS-REFERENCE: `357.96^A1^MUMPS` 1)= S:'(+$P($G(^IBD(357.96,DA,0)),"^",6)) ^IBD(357.96,"A",+X,DA)="" 2)= K ^IBD(357.96,"A",+X,DA) Used to determine if the encounter form has been accounted for. CROSS-REFERENCE: `357.96^AC` 1)= S ^IBD(357.96,"AC",$E(X,1,30),DA)="" 2)= K ^IBD(357.96,"AC",$E(X,1,30),DA) A regular cross-reference of all entries by form design number.
.05	DATE/TIME PRINTED	0;5	DATE	INPUT TRANSFORM: `S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X` LAST EDITED: `JUL 18, 1994` HELP-PROMPT: `When was the form printed?` DESCRIPTION: When the form was printed.
.06	DATE/TIME RECEIVED IN DHCP	0;6	DATE	INPUT TRANSFORM: `S %DT="ESTXR" D ^%DT S X=Y K:Y<1 X` LAST EDITED: `JUL 18, 1994` HELP-PROMPT: `When was the form received?` DESCRIPTION: The date and time that the form is received in DHCP. TECHNICAL DESCR: Don't mark a form as received until all of its pages are received. CROSS-REFERENCE: `357.96^A2^MUMPS` 1)= K:X ^IBD(357.96,"A",+$P($G(^IBD(357.96,DA,0)),"^",4),DA) S:('X)&$P($G(^IBD(357.96,DA,0)),"^",4) ^IBD(357.96,"A",$P($G(^IBD(357.96,DA,0)),"^",4),DA)="" 2)= K:X ^IBD(357.96,"A",+$P($G(^IBD(357.96,DA,0)),"^",4),DA) S:('X)&$P($G(^IBD(357.96,DA,0)),"^",4) ^IBD(357.96,"A",$P($G(^IBD(357.96,DA,0)),"^",4),DA)="" Used to determine if the encounter form has been accounted for.
.07	SOURCE OF FORM ID	0;7	SET	**********************REQUIRED FIELD********************** '1' FOR IB; '2' FOR PANDAS; '3' FOR TELEFORM; '4' FOR PEN; '5' FOR WORKSTATION; '99' FOR OTHER; LAST EDITED: `OCT 04, 1994` DESCRIPTION: This field documents which means of data capture is being used.
.08	FORM TYPE ID (EXTERNAL SOURCE)	0;8	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>30!($L(X)<2) X` LAST EDITED: `OCT 17, 1994` HELP-PROMPT: `Answer must be 2-30 characters in length.` DESCRIPTION: If the form was created externally to DHCP and was assigned an id externally, then this field can be used to document that.
.09	EXTERNAL PRINTED FORM ID	0;9	FREE TEXT	INPUT TRANSFORM: `K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>10!($L(X)<4) X` LAST EDITED: `OCT 17, 1994` HELP-PROMPT: `Answer must be 4-10 characters in length.` DESCRIPTION: This is the external format of the form id (internal entry number) that can be printed on forms and used for look-up. CROSS-REFERENCE: `357.96^AEXT` 1)= S ^IBD(357.96,"AEXT",$E(X,1,30),DA)="" 2)= K ^IBD(357.96,"AEXT",$E(X,1,30),DA) This is a regular cross reference on the external format of the form id
.1	CLINIC	0;10	POINTER TO HOSPITAL LOCATION FILE (#44)	HOSPITAL LOCATION(#44) LAST EDITED: `OCT 11, 1994` DESCRIPTION: This is the clinic of the appointment.
.11	PROCESSING STATUS	0;11	SET	'1' FOR PRINTED; '2' FOR SCANNED; '3' FOR SCANNED TO PCE; '4' FOR SCANNED W/PCE ERROR; '5' FOR DATA ENTRY; '6' FOR DATA ENTRY TO PCE; '7' FOR DATA ENTRY W/PCE ERROR; '11' FOR PENDING PAGES; '12' FOR ERROR DETECTED,NOT TRANSMITTED; '20' FOR AVAILABLE FOR DATA ENTRY; LAST EDITED: `MAY 16, 1996` DESCRIPTION: `This is the processing status of the form. This field is automatically updated by the system. When a form is printed for a patient an entry is created in this file and the processing status is set to printed. When data` is received by DHCP from the scanner the status is updated to Scanned. After the data is processed by PCE the status is updated to show the correct status. For multi-page forms, when not all pages have been scanned, the status is set to Pending Pages. The data is stored in this file from the scanned pages and merged with the rest of the data when all pages have been scanned. Then the complete data is sent to PCE. This is used to prevent sending data from a form to PCE more that once. The only exception is that if PCE returns an error, PCE did not store any data and the form may be re-scanned. TECHNICAL DESCR:
.12	ERROR	0;12	FREE TEXT	INPUT TRANSFORM: `K:$L(X)>30!($L(X)<3) X` LAST EDITED: `OCT 12, 1994` HELP-PROMPT: `Answer must be 3-30 characters in length.` DESCRIPTION: This can be used to document any error that occurred.
.13	EDITING DETECTED	0;13	SET	'0' FOR NO; '1' FOR YES; LAST EDITED: `APR 11, 1996` HELP-PROMPT: `Enter 'Yes' if manual data entry for this form has been done.` DESCRIPTION: `This field is automatically set if data entry on a form has been detected by PCE or Scheduling options. Data entry by AICS options will be indicated in the Processing Status field. If the processing status field contains` data and this field contains data then the visit was entered and then edited.
.14	NO APPOINTMENT ENTRY	0;14	SET	'0' FOR APPOINTMENT EXISTS; '1' FOR NO APPOINTMENT ENTRY; LAST EDITED: `JUN 27, 1996` DESCRIPTION: `This field gets set to 1, "No Appointment Entry" automatically when a forms tracking entry is created by routine IBDF18C if there is no corresponding appointment entry detected in ^DPT(dfn,"s",appt/datetime for the` patient. Forms tracking uses this Cross-reference to find forms not associated with appointments. CROSS-REFERENCE: `357.96^AN` 1)= S ^IBD(357.96,"AN",$E(X,1,30),DA)="" 2)= K ^IBD(357.96,"AN",$E(X,1,30),DA) regular cross reference of visits with no appointments CROSS-REFERENCE: `357.96^ADATNA^MUMPS` 1)= S:+$P(^IBD(357.96,DA,0),"^",3)'="" ^IBD(357.96,"ADATNA",$P(^IBD(357.96,DA,0),"^",3),X,DA)="" 2)= K ^IBD(357.96,"ADATNA",+$P(^IBD(357.96,DA,0),"^",3),X,DA) This mumps cross reference is created to easily retrieve data by date range for those encounter forms printed with no scheduled appointment. The cross reference is set up in ^IBD(357.96,"ADATNA",$P(^IBD(357.96,DA,0),"^",3),X,DA).
.15	TOTAL SECONDS TO INPUT	0;15	NUMBER	INPUT TRANSFORM: `K:+X'=X!(X>999999)!(X<0)!(X?.E1"."1N.N) X` LAST EDITED: `SEP 06, 1996` HELP-PROMPT: `Type a Number between 0 and 999999, 0 Decimal Digits` DESCRIPTION: `Enter the total elapsed time in seconds that it took to process this form, including the processing time in PCE if data was sent to PCE in the foreground.` This field is automatically updated by the AICS Data Entry option and by the AICS Workstation software. See the processing status to determine which method of input was used.
.16	USER INPUTTING DATA	0;16	POINTER TO NEW PERSON FILE (#200)	NEW PERSON(#200) LAST EDITED: `SEP 06, 1996` DESCRIPTION: `Enter the user that processed the data on the form, either through the AICS Data Entry options or through Scanning.` This field is automatically updated by the AICS Data Entry option and by the AICS Workstation software. See the processing status to determine which method of input was used.
1	DYNAMIC LIST ITEMS	1;0	Multiple #357.961	357.961 LAST EDITED: `JUL 21, 1995` DESCRIPTION: This is used to store a lookup table for lists printed on forms where the list was created at print time rather than design time. IDENTIFIED BY: `DATA TYPE(#.03)[R], VALUE TO PASS(#.04), FIELD ID(#.06)`
2	OVERFLOW DATA	2;0	Multiple #357.962	357.962 DESCRIPTION: This multiple is used to store the overflow data on forms whereby the list was created at print time rather than design time.
3	STORED IMAGES	3;0	Multiple #357.963	357.963 DESCRIPTION: This subfile will contain the image name, paths, workstation ID, and users for all pages of the form tracking entry that was saved as an image.
9	SCANNED PAGES	9;0	Multiple #357.969	357.969 DESCRIPTION: A list of pages that should be scanned.
10	RAW SCANNED DATA	10;0	Multiple #357.9601	357.9601 DESCRIPTION: This mulitiple holds the raw data from pages that have been scanned, pending the receipt of more pages. The data will not be processed until all pages that should be scanned are received.

Customize PDF page

Package: Automated Information Collection System

Global: ^IBD(357.96

Information

Description

Directly Accessed By Routines, Total: 26

Accessed By FileMan Db Calls, Total: 10

Pointer To FileMan Files, Total: 6

Fields, Total: 21