| 1 | English French Notes Complete/Exclude
|
|---|
| 2 | New Means Test Status
|
|---|
| 3 | ***End Of Report***
|
|---|
| 4 | Sort by Discharge or Admission: D//
|
|---|
| 5 | CHOOSE FROM
|
|---|
| 6 | START DATE:
|
|---|
| 7 | END DATE:
|
|---|
| 8 | THIRD PARTY REIMBURSEMENT
|
|---|
| 9 | PRINTED:
|
|---|
| 10 | EMPLOYMENT STATUS:
|
|---|
| 11 | EMPLOYED FULL TIME
|
|---|
| 12 | EMPLOYED PART TIME
|
|---|
| 13 | NOT EMPLOYED
|
|---|
| 14 | SELF EMPLOYED
|
|---|
| 15 | ACTIVE MILITARY DUTY
|
|---|
| 16 | (PT ID:
|
|---|
| 17 | EMPLOYER:
|
|---|
| 18 | OCCUPATION:
|
|---|
| 19 | INSURANCE TYPE
|
|---|
| 20 | INSURANCE #
|
|---|
| 21 | GROUP #
|
|---|
| 22 | EXPIRES HOLDER
|
|---|
| 23 | * - Insurer may not reimburse!
|
|---|
| 24 | Admitted:
|
|---|
| 25 | Discharged:
|
|---|
| 26 | Transferred in From
|
|---|
| 27 | No PTF Record Exists
|
|---|
| 28 | PTF Record not closed
|
|---|
| 29 | LOS BEDSECTION
|
|---|
| 30 | TOTAL LOS:
|
|---|
| 31 | DXLS:
|
|---|
| 32 | SURGERY DATE
|
|---|
| 33 | OP CODES
|
|---|
| 34 | Cleanup Patient Relation & Income Files
|
|---|
| 35 | This request queued as Task #
|
|---|
| 36 | NO LOCK GAINED
|
|---|
| 37 | Cleanup of Patient Related Income files
|
|---|
| 38 | *** ALREADY RUNNING ***
|
|---|
| 39 | Do you want to Re-Run in
|
|---|
| 40 | Entering Y, will delete the XTMP global where the previous cleanup
|
|---|
| 41 | information was stored and begin a new job, or N to cancel request
|
|---|
| 42 | ARE YOU SURE?
|
|---|
| 43 | Enter Y to begin a new Job or N to cancel request
|
|---|
| 44 | DG*5.3*488
|
|---|
| 45 | NOT RUNNING
|
|---|
| 46 | Task ID:
|
|---|
| 47 | Last ien
|
|---|
| 48 | Completed Time
|
|---|
| 49 | Tot 408.12 recs
|
|---|
| 50 | 408.12 recs purged
|
|---|
| 51 | 408.12 bad xrefs
|
|---|
| 52 | Tot 408.21 recs
|
|---|
| 53 | 408.21 recs purged
|
|---|
| 54 | 408.21 bad xrefs
|
|---|
| 55 | Tot 408.22 recs
|
|---|
| 56 | 408.22 recs purged
|
|---|
| 57 | 408.22 bad xrefs
|
|---|
| 58 | screen refreshes automatically every
|
|---|
| 59 | to Stop Monitor...
|
|---|
| 60 | IOINORM;IOINHI;IOUON;IOUOFF;IOBON;IOBOFF;IORVON;IORVOFF;IOHOME
|
|---|
| 61 | Elapsed time:
|
|---|
| 62 | Total 408.12 Records Processed:
|
|---|
| 63 | 408.12 bad records purged:
|
|---|
| 64 | 408.12 bad xrefs purged:
|
|---|
| 65 | Total 408.21 Records Processed:
|
|---|
| 66 | 408.21 bad records purged:
|
|---|
| 67 | 408.21 bad xrefs purged:
|
|---|
| 68 | Total 408.22 Records Processed:
|
|---|
| 69 | 408.22 bad records purged:
|
|---|
| 70 | 408.22 bad xrefs purged:
|
|---|
| 71 | >>Edit Clerk multiple (#45.52) found. Data dictionary nodes deleted.
|
|---|
| 72 | >>Edit Clerk multiple (#45.52) not found. Nothing deleted.
|
|---|
| 73 | >>> Checking the internal entry number(IEN), name, and activity
|
|---|
| 74 | of the 21 entries in the MAS ELIGIBILITY CODE file (#8.1).
|
|---|
| 75 | The following discrepancies were found:
|
|---|
| 76 | Missing IEN of
|
|---|
| 77 | IEN of
|
|---|
| 78 | should be
|
|---|
| 79 | The number of entries in the MAS ELIGIBILITY CODE file is greater than 21
|
|---|
| 80 | MAS ELIGIBILITY CODE file (#8.1) is correct.
|
|---|
| 81 | >>> Please correct the discrepancies in the MAS ELIGIBILITY CODE file
|
|---|
| 82 | and rerun DG53177P (D ^DG53177P)
|
|---|
| 83 | >>> Checking the entries in the ELIGIBILITY CODE file (#8).
|
|---|
| 84 | ELIGIBILITY CODE file (#8) is correct.
|
|---|
| 85 | Validation has completed with no discrepancies found
|
|---|
| 86 | The following entries do not point to an entry in the
|
|---|
| 87 | MAS ELIGIBILITY CODE file:
|
|---|
| 88 | The following inactive entries point to an active
|
|---|
| 89 | entry in the MAS ELIGIBILITY CODE file:
|
|---|
| 90 | These may be correct, just listing for further review.
|
|---|
| 91 | The following active entries point to an inactive
|
|---|
| 92 | Do you wish to continue?
|
|---|
| 93 | Enter Yes to continue, or No to quit
|
|---|
| 94 | Enter the Division you are setting up the
|
|---|
| 95 | RAI/MDS HL7 messaging for
|
|---|
| 96 | Select the appropriate division to set up the HL7 messaging parameters for.
|
|---|
| 97 | You have selected :
|
|---|
| 98 | Station Number :
|
|---|
| 99 | Undefined Station Number
|
|---|
| 100 | You cannot proceed with this division until the station number is
|
|---|
| 101 | corrected. Check the STATION NUMBER TIME SENSITIVE
|
|---|
| 102 | file to be sure this division is active today.
|
|---|
| 103 | You may select another division or quit.
|
|---|
| 104 | Is this correct?
|
|---|
| 105 | Enter Yes or No, Yes will select, No will cancel.
|
|---|
| 106 | Enter IP address of target COTS receiver:
|
|---|
| 107 | The IP address must be in the format 'nnn.nnn.nnn.nnn' where
|
|---|
| 108 | nnn is a numeric, 1-3 numbers in length and should designate
|
|---|
| 109 | the static IP address for the COTS database server.
|
|---|
| 110 | Enter the port number of the target COTS receiver:
|
|---|
| 111 | The port number must be a numeric value and should be
|
|---|
| 112 | the TCP/IP port the target COTS receiver is listening on.
|
|---|
| 113 | A Logical Link for
|
|---|
| 114 | FDA(1)
|
|---|
| 115 | ERR(1)
|
|---|
| 116 | DGRU ADT/HL7
|
|---|
| 117 | DGRU-
|
|---|
| 118 | A HL7 Application for
|
|---|
| 119 | HL7 Application data not available
|
|---|
| 120 | DGRU-RAI-
|
|---|
| 121 | A protocol for
|
|---|
| 122 | CLIENT PROTOCOL FOR
|
|---|
| 123 | DGRU-PATIENT-A08-
|
|---|
| 124 | A08 DEMOGRAPHIC UPDATES CLIENT PROTOCOL FOR
|
|---|
| 125 | DGRU-RAI-MFU-
|
|---|
| 126 | MFU CLIENT PROTOCOL FOR
|
|---|
| 127 | Setup complete
|
|---|
| 128 | Reviewing Income Data Inconsistency Errors
|
|---|
| 129 | Checking for WHILE ASIH discharges incorrectly linked to an Admission
|
|---|
| 130 | Deleting Patient Movement number
|
|---|
| 131 | G&L should be recalculated back to
|
|---|
| 132 | G&L does not need to be recalculated
|
|---|
| 133 | Unable to lock global try later!
|
|---|
| 134 | NPCDB patient demographics extraction
|
|---|
| 135 | Unable to queue extraction, contact Customer Service for assistance!
|
|---|
| 136 | NPCDB patient demographics extraction queued for
|
|---|
| 137 | Patient demographics extraction not queued--
|
|---|
| 138 | It appears that this process is already in progress!
|
|---|
| 139 | Patch DG*5.3*213
|
|---|
| 140 | DG(
|
|---|
| 141 | *** Status of NPCDB patient demographics extraction ***
|
|---|
| 142 | NPCDB patient demographics extraction completed!
|
|---|
| 143 | Unable to queue NPCDB patient demographics extraction continuation--
|
|---|
| 144 | Please contact Customer Service for assistance!
|
|---|
| 145 | Number of records found to send:
|
|---|
| 146 | Number of records that have been sent:
|
|---|
| 147 | Extraction process was requested to stop before building a complete list.
|
|---|
| 148 | The partially built list was cleared, extraction will be restarted as follows:
|
|---|
| 149 | NPCDB extraction queued for:
|
|---|
| 150 | Next transmission queued for:
|
|---|
| 151 | Task number:
|
|---|
| 152 | Unable to send these records:
|
|---|
| 153 | IFN:
|
|---|
| 154 | Cannot Delete in this Mode
|
|---|
| 155 | * Compiling Print Templates *
|
|---|
| 156 | * Compiling Input Templates *
|
|---|
| 157 | DG-MTIY
|
|---|
| 158 | DG-MTERR
|
|---|
| 159 | DG-
|
|---|
| 160 | record count
|
|---|
| 161 | filing errors
|
|---|
| 162 | POST INSTALLATION PROCESSING
|
|---|
| 163 | Once the post-install is completed, a mail message will
|
|---|
| 164 | be sent that will report the count of records, by income
|
|---|
| 165 | year, from which means test entries were purged.
|
|---|
| 166 | Additionally, the report will contain notes
|
|---|
| 167 | about any errors encountered during the post-installation.
|
|---|
| 168 | Beginning purge process
|
|---|
| 169 | >>purge process completed
|
|---|
| 170 | Unable to delete means test
|
|---|
| 171 | Purge of NO LONGER REQUIRED IVM verified Means Tests
|
|---|
| 172 | IVM/HEC PACKAGE
|
|---|
| 173 | Purge of NO LONGER REQUIRED verified Means Tests
|
|---|
| 174 | Income year
|
|---|
| 175 | # of IVM MT purged
|
|---|
| 176 | Some records were not edited due to filing errors:
|
|---|
| 177 | Field #
|
|---|
| 178 | Error Message
|
|---|
| 179 | Deleting trigger on VIETNAM SERVICE INDICATED? field
|
|---|
| 180 | (#.32101) that deletes Agent Orange data when set to NO
|
|---|
| 181 | Updating definition of INCONSISTENT DATA ELEMENT number 25
|
|---|
| 182 | AO CLAIMED W/OUT VIETNAM POS
|
|---|
| 183 | AGENT ORANGE EXPOSURE INDICATED WITHOUT VIETNAM ERA PERIOD OF SERVICE
|
|---|
| 184 | SERVICE VERIFIED
|
|---|
| 185 | Inconsistency results if the patient is a veteran, the 'EXPOSED TO AGENT
|
|---|
| 186 | ORANGE' prompt is answered YES, and the 'PERIOD OF SERVICE' prompt is not
|
|---|
| 187 | answered VIETNAM ERA (#7).
|
|---|
| 188 | Creating definition of INCONSISTENT DATA ELEMENT number 60
|
|---|
| 189 | AGENT ORANGE EXP LOC MISSING
|
|---|
| 190 | 'AGENT ORANGE EXPOSURE LOCATION' REQUIRED IF AO EXP INDICATED
|
|---|
| 191 | Inconsistency results if the 'EXPOSED TO AGENT ORANGE' prompt is answered
|
|---|
| 192 | YES and the 'AGENT ORANGE EXPOSURE LOCATION' prompt is not answered.
|
|---|
| 193 | Routine to populate AGENT ORANGE EXPOSURE LOCATION field
|
|---|
| 194 | (#.3213) with VIETNAM for all patients claiming exposure
|
|---|
| 195 | to agent orange (AGENT ORANGE EXPOS. INDICATED? equals
|
|---|
| 196 | YES) will now be queued
|
|---|
| 197 | Post init appears to be running. If it is not, delete the
|
|---|
| 198 | ,2) and use line tag QUEUE^DG53342P
|
|---|
| 199 | to [re]start the process.
|
|---|
| 200 | Post init appears to have run to completion on
|
|---|
| 201 | If it did not, delete the node ^XTMP(
|
|---|
| 202 | ,3) and use
|
|---|
| 203 | line tag QUEUE^DG53342P to [re]start the process.
|
|---|
| 204 | Initial seeding of AGENT ORANGE EXPOSURE LOCATION field
|
|---|
| 205 | Task #
|
|---|
| 206 | queued to start
|
|---|
| 207 | ***** UNABLE TO QUEUE INITIAL SEEDING *****
|
|---|
| 208 | DFN:
|
|---|
| 209 | STOPPED PROCESSING AT DFN
|
|---|
| 210 | DG*5.3*342 post init has run to completion.
|
|---|
| 211 | DG*5.3*342 post init was asked to stop.
|
|---|
| 212 | YES) ran to completion on
|
|---|
| 213 | Post init routine DG53342P can be deleted.
|
|---|
| 214 | YES) was asked to stop on
|
|---|
| 215 | Use the entry point QUEUE^DG53342P to resume seeding.
|
|---|
| 216 | Patch DG*5.3*342
|
|---|
| 217 | NON TREATING PREFERRED FACILITY CLEAN UP REPORT
|
|---|
| 218 | Compile Start Date/Time:
|
|---|
| 219 | Report is currently compiling!
|
|---|
| 220 | A MailMan message will be sent when the compile is complete.
|
|---|
| 221 | Compile Stop Date/Time:
|
|---|
| 222 | Print Detail Report
|
|---|
| 223 | TaskMan Task:
|
|---|
| 224 | *** END OF REPORT ***
|
|---|
| 225 | Patch DG*5.3*355 (
|
|---|
| 226 | Errored
|
|---|
| 227 | Stopped
|
|---|
| 228 | Finished
|
|---|
| 229 | The compile process has completed. The detail report
|
|---|
| 230 | can be viewed by returning to the original menu option.
|
|---|
| 231 | After 30 days the compiled data will be purged and the
|
|---|
| 232 | report will have to be recompiled.
|
|---|
| 233 | Number of records for each non-treating Preferred Facility:
|
|---|
| 234 | No Entries Found
|
|---|
| 235 | Current Preferred Facility
|
|---|
| 236 | This process will find all patients that have a non-treating
|
|---|
| 237 | Preferred Facility on file. All identified patients will need
|
|---|
| 238 | to have their Preferred Facility changed to a valid treating
|
|---|
| 239 | The clean up process will perform the following steps in order:
|
|---|
| 240 | 1) Compile the patient data. (This step looks at
|
|---|
| 241 | every patient in the PATIENT (#2) file.) A summary
|
|---|
| 242 | MailMan message will be sent to the user when the
|
|---|
| 243 | compile is complete.
|
|---|
| 244 | 2) The user will need to return to this option to print
|
|---|
| 245 | the detail report within 30 days to avoid recompiling.
|
|---|
| 246 | NOTE: The system will purge the compiled data after 30
|
|---|
| 247 | All compiled data will be stored in the ^XTMP(
|
|---|
| 248 | DELETE PRMYTEST
|
|---|
| 249 | >>> Updating PTF Census Date File (#45.86) for 3rd Quarter, FY 2001.
|
|---|
| 250 | Problem with PTF CENSUS DATE File (#45.86) Update. Please
|
|---|
| 251 | contact the National VISTA Support Team for assistance.
|
|---|
| 252 | The new
|
|---|
| 253 | INFORMATION multiple is contained in
|
|---|
| 254 | an obsolete sub-file that still exists on your system.
|
|---|
| 255 | The obsolete sub-file (#
|
|---|
| 256 | ) will now be deleted.
|
|---|
| 257 | The B cross reference on the RACE file (#10) may be listed
|
|---|
| 258 | as the second cross reference of the NAME field (#.01)
|
|---|
| 259 | instead of the first. To ensure that the B cross
|
|---|
| 260 | reference is listed as the first cross reference, the
|
|---|
| 261 | second cross reference of the NAME field will now be
|
|---|
| 262 | The incorrect B cross reference on the RACE file (#10),
|
|---|
| 263 | which was removed by the pre-init, placed the entire value
|
|---|
| 264 | of the NAME field (#.01) into the cross reference. The
|
|---|
| 265 | correct logic for the B cross reference only places the
|
|---|
| 266 | first thirty characters into the cross reference. To
|
|---|
| 267 | ensure that the cross referenced values are correct, the
|
|---|
| 268 | entire B cross reference will now be deleted and then
|
|---|
| 269 | Marking all entries in the RACE file (#10) as inactive
|
|---|
| 270 | ** Unable to inactivate entry number
|
|---|
| 271 | ** Entry should be inactivated via FileMan
|
|---|
| 272 | Creating/updating nationally supported entries in the RACE
|
|---|
| 273 | ** Unable to create entry for
|
|---|
| 274 | ** Entry should be created via FileMan
|
|---|
| 275 | ** CDC Val (4):
|
|---|
| 276 | ** PTF Val (5):
|
|---|
| 277 | Removing old RACE field (#.06) as an identifier of the
|
|---|
| 278 | PATIENT file (#2).
|
|---|
| 279 | Entry not added to SPECIALTY File (#42.4). No further updating will occur.
|
|---|
| 280 | Please contact Customer Service for assistance.
|
|---|
| 281 | Entry exists in SPECIALTY File (#42.4), but with a different PTF Code #.
|
|---|
| 282 | No further updating will occur. Please review entry.
|
|---|
| 283 | added to
|
|---|
| 284 | exists in
|
|---|
| 285 | SPECIALTY File (#42.4).
|
|---|
| 286 | Updating SPECIALTY File fields.
|
|---|
| 287 | Answered NO to install question. Specialty will not be added to FACILITY
|
|---|
| 288 | TREATING SPECIALTY File (#45.7).
|
|---|
| 289 | Treating specialty not found in SPECIALTY File (#42.4). Cannot
|
|---|
| 290 | be added to FACILITY TREATING SPECIALTY File (#45.7).
|
|---|
| 291 | Answered YES to install question. SPECIALITY File (#42.4) does not
|
|---|
| 292 | contain the expected PTF Code #. Cannot update FACILITY TREATING
|
|---|
| 293 | SPECIALTY File (#45.7).
|
|---|
| 294 | Entry not added to FACILITY TREATING SPECIALTY File(#45.7).
|
|---|
| 295 | Entry exists in FACILITY TREATING SPECIALTY File (#45.7), but with
|
|---|
| 296 | a different PTF Code #. No further updating will occur.
|
|---|
| 297 | Please review entry.
|
|---|
| 298 | FACILITY TREATING SPECIALTY File (#45.7).
|
|---|
| 299 | Updating SPECIALTY field...
|
|---|
| 300 | Effective date not added.
|
|---|
| 301 | Effective date added.
|
|---|
| 302 | *** Updating MEANS TEST STATUS file(#408.32)***
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
