| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | printed form id(+) | 0;1 | NUMERIC | B | Uniquely identifies an instance of a printed encounter form. This is the same as the ien. | |
| .02 | patient(+) | 0;2 | POINTER | 2 | C | The patient that had the appointment. |
| .03 | appointment | 0;3 | DATE-TIME | D | The date/time of the appointment for which the encounter form was printed. | |
| .04 | form type | 0;4 | POINTER | 357.95 | AC | 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. |
| .05 | date/time printed | 0;5 | DATE-TIME | When the form was printed. | ||
| .06 | date/time received in dhcp | 0;6 | DATE-TIME | The date and time that the form is received in DHCP. | ||
| .07 | source of form id(+) | 0;7 | SET OF CODES | 1:IB 2:PANDAS 3:TELEFORM 4:PEN 5:WORKSTATION 99:OTHER | This field documents which means of data capture is being used. | |
| .08 | form type id (external source) | 0;8 | FREE TEXT | 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 | AEXT | This is the external format of the form id (internal entry number) that can be printed on forms and used for look-up. | |
| .1 | clinic | 0;10 | POINTER | 44 | This is the clinic of the appointment. | |
| .11 | processing status | 0;11 | SET OF CODES | 1:PRINTED 2:SCANNED 3:SCANNED TO PCE 4:SCANNED W/PCE ERROR 5:DATA ENTRY 6:DATA ENTRY TO PCE 7:DATA ENTRY W/PCE ERROR 11:PENDING PAGES 12:ERROR DETECTED,NOT TRANSMITTED 20:AVAILABLE FOR DATA ENTRY | 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. | |
| .12 | error | 0;12 | FREE TEXT | This can be used to document any error that occurred. | ||
| .13 | editing detected | 0;13 | BOOLEAN | 0:NO 1:YES | 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 OF CODES | 0:APPOINTMENT EXISTS 1:NO APPOINTMENT ENTRY | AN | 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. |
| .15 | total seconds to input | 0;15 | NUMERIC | 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 | 200 | 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 | 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. | |
| 2 | overflow data | 2;0 | MULTIPLE | 357.962 | 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 | 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 | A list of pages that should be scanned. | |
| 10 | raw scanned data | 10;0 | MULTIPLE | 357.9601 | 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. |
Not Referenced