[604] | 1 | English French Notes Complete/Exclude
|
---|
| 2 | You have not chosen a valid extract number. Try again.
|
---|
| 3 | I will purge the following extract(s):
|
---|
| 4 | Is this OK
|
---|
| 5 | if you agree with this list and would like to proceed,
|
---|
| 6 | if you would like to make a different selection, or
|
---|
| 7 | to exit option.
|
---|
| 8 | Incomplete
|
---|
| 9 | PURGABLE EXTRACTS
|
---|
| 10 | FEEDER SYS
|
---|
| 11 | EXTRACT,
|
---|
| 12 | EXTRACT #
|
---|
| 13 | FROM-TO
|
---|
| 14 | RECORD CNT
|
---|
| 15 | TRANSMIT DATE
|
---|
| 16 | You have no data in the IVP holding file (file #728.113) to purge.
|
---|
| 17 | You have no data in the UDP holding file (file #728.904) to purge.
|
---|
| 18 | This file currently holds
|
---|
| 19 | data from <
|
---|
| 20 | Beginning date for purge:
|
---|
| 21 | Ending date for purge:
|
---|
| 22 | I will purge the
|
---|
| 23 | holding file from <
|
---|
| 24 | ** REMEMBER - Once this data is purged it CANNOT be recreated. **
|
---|
| 25 | if you agree with this date range and wish to proceed,
|
---|
| 26 | The CBOC Activity Report has not been viewed. Purge anyway
|
---|
| 27 | Contact an ADPAC or IRM for assistance.
|
---|
| 28 | Your division is not set up as a prosthetic division.
|
---|
| 29 | Your division (
|
---|
| 30 | ) is not a prosthetic primary division.
|
---|
| 31 | Note that the Station Number (
|
---|
| 32 | ) is longer than 3 characters
|
---|
| 33 | for the Station
|
---|
| 34 | Check with IRM to identify the primary division and add it to your New Person
|
---|
| 35 | file entry.
|
---|
| 36 | Select Prosthetic Division:
|
---|
| 37 | You did not select a prosthetic division.
|
---|
| 38 | You must be using the Quality Audiology & Speech Pathology
|
---|
| 39 | Audit & Review (QUASAR) software to run this extract.
|
---|
| 40 | Linkage has not been established between QUASAR and the DSS UNIT file (#724).
|
---|
| 41 | There is no data in the A&SP CLINIC VISIT file (#509850.6).
|
---|
| 42 | Dental Extract SAS Report
|
---|
| 43 | Try agian later... exiting.
|
---|
| 44 | Total for Feeder Location
|
---|
| 45 | Radiology Extract SAS Report
|
---|
| 46 | Prescription Extract SAS Report
|
---|
| 47 | Surgery Extract SAS Report
|
---|
| 48 | NON-OR
|
---|
| 49 | This option creates local entries in the DSS CLINIC AND STOP CODES file.
|
---|
| 50 | DSS Clinic stop code file does not exist
|
---|
| 51 | Gather Clinic stop codes for DSS
|
---|
| 52 | This option produces a worksheet of (A)ll DSS Clinic Stops or only the
|
---|
| 53 | (U)nreviewed Clinic Stops that are awaiting approval. Clinics that were
|
---|
| 54 | defined as
|
---|
| 55 | by MAS the last time the option
|
---|
| 56 | Create DSS Clinic
|
---|
| 57 | Stop Code File
|
---|
| 58 | was run will be indicated with an
|
---|
| 59 | Enter:
|
---|
| 60 | to print a worksheet of all DSS Clinic Stops,
|
---|
| 61 | to print only the Clinic Stops that have not been approved.
|
---|
| 62 | DSS clinic stop code work sheet
|
---|
| 63 | NO DATA FOUND FOR WORKSHEET.
|
---|
| 64 | WORKSHEET FOR DSS CLINIC STOPS
|
---|
| 65 | (last reviewed on
|
---|
| 66 | (NEVER REVIEWED)
|
---|
| 67 | NAT'L
|
---|
| 68 | (* - currently inactive)
|
---|
| 69 | STOP CODE :
|
---|
| 70 | CREDIT STOP CODE :
|
---|
| 71 | This option allows you to mark the current clinic entries in the CLINICS AND
|
---|
| 72 | STOP CODES file (#728.44) as
|
---|
| 73 | . Those entries will then be omitted
|
---|
| 74 | from the list printed from the
|
---|
| 75 | Clinic and DSS Stop Codes Print
|
---|
| 76 | when you
|
---|
| 77 | choose to print only
|
---|
| 78 | Are you ready to approve the reviewed information provided by the
|
---|
| 79 | if you concur with the
|
---|
| 80 | or <RET> if you do not want to approve the current information,
|
---|
| 81 | Approve DSS stop codes for clinic extract
|
---|
| 82 | ...approval queued
|
---|
| 83 | This option synchronizes the Primary and Secondary Stop Codes in the Clinics
|
---|
| 84 | and Stop Codes File #728.44 with those in the Hospital Location File #44.
|
---|
| 85 | It produces a report highlighting any non conformance reasons that pertain
|
---|
| 86 | to the Primary and Secondary Codes. Please contact the responsible party
|
---|
| 87 | for corrective action.
|
---|
| 88 | Enter an A for Active Clinics, I for Inactive Clinics,
|
---|
| 89 | B for Both Active and Inactive Clinics
|
---|
| 90 | . Please be patient, this may take a few moments...
|
---|
| 91 | Restricted Stop Code/DSS Identifier Report
|
---|
| 92 | Invalid Stop Code
|
---|
| 93 | No pointer in file #40.7
|
---|
| 94 | DSS IDENTIFIER NON-CONFORMING CLINICS REPORT
|
---|
| 95 | IEN #
|
---|
| 96 | (*currently inactive)
|
---|
| 97 | TEXT INTEGRATION UTILITIES
|
---|
| 98 | MISSING CLINICS in File #728.44
|
---|
| 99 | CLINICS w/o DIVISION Data
|
---|
| 100 | PROV CLASS
|
---|
| 101 | PROV NPI
|
---|
| 102 | Admission (setup)
|
---|
| 103 | Movement (setup)
|
---|
| 104 | Treating specialty change (setup)
|
---|
| 105 | SETUP EXTRACT FOR DSS
|
---|
| 106 | The DSS setup extract completed on
|
---|
| 107 | extract file entries were created.
|
---|
| 108 | ECM(
|
---|
| 109 | The setup extract is already running.
|
---|
| 110 | The setup extract has already been run.
|
---|
| 111 | This option will extract the admission data and data for the last
|
---|
| 112 | transfer and treating specialty change for all patients who
|
---|
| 113 | were in the hospital on the day you select.
|
---|
| 114 | NOTE - This will generate a snapshot of your inpatient population on the
|
---|
| 115 | BEGINNING of the day you select, not the end of the day as MAS reports do.
|
---|
| 116 | For example, for the inpatient setup extract if you choose October 1, 1994,
|
---|
| 117 | the report will start at midnight at the beginning of the day.
|
---|
| 118 | For the MAS
|
---|
| 119 | report, you would choose September 30, 1994. The MAS report begins at midnight
|
---|
| 120 | at the end of the day.
|
---|
| 121 | Select the starting date
|
---|
| 122 | Date must be in the past
|
---|
| 123 | Find all inpatients on
|
---|
| 124 | Admission setup
|
---|
| 125 | AUTO-REQUEUE EXTRACT FOR DSS
|
---|
| 126 | The BACKGROUND DSS-
|
---|
| 127 | was begun on
|
---|
| 128 | and completed on
|
---|
| 129 | Extract time was [HH:MM:SS]
|
---|
| 130 | The data was extracted using
|
---|
| 131 | fiscal year
|
---|
| 132 | ECMSG(
|
---|
| 133 | BACKGROUND EXTRACT FAILURE
|
---|
| 134 | extract was automatically requeued to extract
|
---|
| 135 | data for
|
---|
| 136 | Data for this range of dates has already been extracted.
|
---|
| 137 | The extract was NOT generated, but has been requeued to run
|
---|
| 138 | next month.
|
---|
| 139 | There was an attempt to automatically requeue the
|
---|
| 140 | extract for the month of
|
---|
| 141 | The extract was NOT generated. The first extract of the new fiscal
|
---|
| 142 | year will need to be queued to run after any required fiscal year
|
---|
| 143 | update is installed.
|
---|
| 144 | But a
|
---|
| 145 | extract appears to be currently running.
|
---|
| 146 | The requeued extract was NOT generated, but has been requeued
|
---|
| 147 | for next month.
|
---|
| 148 | The LOCAL USE DSS-
|
---|
| 149 | extract for
|
---|
| 150 | was completed on
|
---|
| 151 | The local
|
---|
| 152 | extract was not properly set up
|
---|
| 153 | Please review settings in file 727.1 and requeue this extract
|
---|
| 154 | EC(
|
---|
| 155 | Local extract not properly setup
|
---|
| 156 | extract is already scheduled to run
|
---|
| 157 | Extract
|
---|
| 158 | Information for DSS
|
---|
| 159 | information has already been extracted through
|
---|
| 160 | Please enter a new date range.
|
---|
| 161 | There does not appear to be any data in the IV EXTRACT DATA
|
---|
| 162 | file (#728.113) for the selected date range.
|
---|
| 163 | The IVP extract cannot be generated.
|
---|
| 164 | The DSS-
|
---|
| 165 | A user stop request was received by Taskmanager which caused processing
|
---|
| 166 | to terminate before completion. Any records which may have been created
|
---|
| 167 | in file #
|
---|
| 168 | for this extract have been deleted.
|
---|
| 169 | All active IV Rooms in the IV Room file (#59.5) must have a
|
---|
| 170 | assigned to run this extract!
|
---|
| 171 | This information can be entered using the DSS Extract Manager's Maintenance
|
---|
| 172 | Enter/Edit IV Room Division
|
---|
| 173 | You have not defined a proper transmission queue
|
---|
| 174 | for entry number 1 in the DSS EXTRACTS file (#728).
|
---|
| 175 | No transmission allowed.
|
---|
| 176 | Your user setup will only allow you to transmit extracts from the
|
---|
| 177 | following divisions:
|
---|
| 178 | If you can't select an extract, it is probably from another division.
|
---|
| 179 | Transmit which extract:
|
---|
| 180 | Records:
|
---|
| 181 | Generated on:
|
---|
| 182 | Start date:
|
---|
| 183 | Division:
|
---|
| 184 | End date:
|
---|
| 185 | MailMan transmission of the
|
---|
| 186 | extract is set to a
|
---|
| 187 | limit of 131,000 bytes per message. Each extract record ends with a ^~.
|
---|
| 188 | This extract was transmitted on
|
---|
| 189 | Do you want to retransmit
|
---|
| 190 | An
|
---|
| 191 | Extract is currently running or scheduled to run.
|
---|
| 192 | Please wait until that job has completed before attempting
|
---|
| 193 | this transmission.
|
---|
| 194 | ** This extract is being sent from a field office domain. **
|
---|
| 195 | ** Extract message(s) will only be delivered to you and **
|
---|
| 196 | ** will be placed into your 'DSSXMIT' mail basket. **
|
---|
| 197 | ** This extract will be transmitted to the AAC test queue **
|
---|
| 198 | Do you want to continue
|
---|
| 199 | Prosthetics
|
---|
| 200 | DSS EXTRACT, MESSAGE
|
---|
| 201 | XXX@Q-
|
---|
| 202 | transmitted on
|
---|
| 203 | Maximum number of Bytes (characters) per message: 131,000
|
---|
| 204 | messages were sent.
|
---|
| 205 | Message numbers :
|
---|
| 206 | FO-
|
---|
| 207 | ISC-
|
---|
| 208 | * This option should be used with caution as it allows for the *
|
---|
| 209 | * extraction of data using specified fiscal year logic. This *
|
---|
| 210 | * gives the ability to extract fiscal year 200x data using *
|
---|
| 211 | * fiscal year 200(x+1) logic and vice versa. Note that data *
|
---|
| 212 | * extracted via this method may or may not be transmittable to *
|
---|
| 213 | * the DSS production queue at the Austin Automation Center. *
|
---|
| 214 | * Note that this option does not update the last date used for *
|
---|
| 215 | * the given extraction. It also does not verify that the time *
|
---|
| 216 | * frame selected is after the last date used for the extract. *
|
---|
| 217 | Select DSS Extract to queue:
|
---|
| 218 | Selected extract is not correctly defined in the EXTRACT
|
---|
| 219 | DEFINITIONS file (#727.1). The ROUTINE field (#4) does not
|
---|
| 220 | have a value in it.
|
---|
| 221 | Select fiscal year logic to use for extract
|
---|
| 222 | Revision
|
---|
| 223 | Fiscal Year
|
---|
| 224 | This option will print the admission data and data for the last
|
---|
| 225 | NOTE - This will generate a report of your inpatient population on the
|
---|
| 226 | For example, for this report, if you choose October 1, 1994, the report will
|
---|
| 227 | start at midnight at the beginning of the day.
|
---|
| 228 | For the MAS report, you would
|
---|
| 229 | choose September 30, 1994. The MAS report begins at midnight at the end
|
---|
| 230 | of the day.
|
---|
| 231 | Select the date
|
---|
| 232 | Must be a date in the past
|
---|
| 233 | This report must be queued to a 132 column printer.
|
---|
| 234 | Print inpatient list (DSS)
|
---|
| 235 | INPATIENT WARD LIST (DSS) FOR
|
---|
| 236 | FOR WARD
|
---|
| 237 | ADMIT DATE
|
---|
| 238 | CBOC Activity Report
|
---|
| 239 | This report requires 80-column format.
|
---|
| 240 | This report prints a listing of all Clinical (CLI) records
|
---|
| 241 | that have a Community Based Outpatient Clinic (CBOC) status of
|
---|
| 242 | Y (=Yes). Reports are grouped by Feeder Key, Division, and
|
---|
| 243 | Clinic; detail lines include Patient Name, SSN, and Date of Visit.
|
---|
| 244 | Totals for unique SSNs and unique Dates of Visit will be displayed
|
---|
| 245 | at the Clinic, Division, Feeder Key, and Report levels.
|
---|
| 246 | Create the CBOC Activity Report for the following extract
|
---|
| 247 | Invalid choice. Please try again.
|
---|
| 248 | Selectable Clinic Extracts for CBOC Activity Report
|
---|
| 249 | Extract #
|
---|
| 250 | Run Date
|
---|
| 251 | Rec Count
|
---|
| 252 | Date Range of Extract
|
---|
| 253 | No extract records exist for the selected extract.
|
---|
| 254 | No records were found with a CBOC Indicator value of
|
---|
| 255 | Total Unique SSNs for Clinic:
|
---|
| 256 | Clinic Visits
|
---|
| 257 | Total Unique SSNs for Division:
|
---|
| 258 | Division Visits
|
---|
| 259 | Total Unique SSNs for Feeder Key:
|
---|
| 260 | Feeder Key Visits
|
---|
| 261 | Total Unique SSNs (entire report):
|
---|
| 262 | Total Visits
|
---|
| 263 | Report Run Date:
|
---|
| 264 | Feeder Key:
|
---|
| 265 | Visit Date/Time
|
---|
| 266 | This inquiry allows the user to select a CPT code, then displays
|
---|
| 267 | the Short Name, Category, and Description for the selected code.
|
---|
| 268 | CPT Code Error.
|
---|
| 269 | CPT Inquiry
|
---|
| 270 | CPT Code:
|
---|
| 271 | Short Name:
|
---|
| 272 | Description:
|
---|
| 273 | There are no unit dose orders to extract
|
---|
| 274 | Prosthetic Extract Unusual Cost Report
|
---|
| 275 | This report prints a listing of unusual costs that would be
|
---|
| 276 | generated by the Prosthetic extract (PRO) as determined by a
|
---|
| 277 | user-defined threshold value. It should be run prior to the
|
---|
| 278 | generation of the actual extract(s) to identify and fix, as
|
---|
| 279 | necessary, any costs determined to be erroneous.
|
---|
| 280 | Unusual costs are those where the Cost of Transaction is
|
---|
| 281 | greater than the threshold value.
|
---|
| 282 | The report is sorted by Feeder Key, then by descending Cost of
|
---|
| 283 | Transaction and SSN.
|
---|
| 284 | The default threshold cost for the Prosthetic extract is $
|
---|
| 285 | Would you like to change the threshold?
|
---|
| 286 | Cost > threshold
|
---|
| 287 | Enter the new threshold cost
|
---|
| 288 | No unusual costs to report for this extract
|
---|
| 289 | End Date:
|
---|
| 290 | Threshold Value:
|
---|
| 291 | PCE CPT/
|
---|
| 292 | Cost of
|
---|
| 293 | HCPCS CODE & Modifiers
|
---|
| 294 | Transaction
|
---|
| 295 | Surgery Extract Unusual Volume Report
|
---|
| 296 | generated by the Surgery extract (SUR) as determined by a
|
---|
| 297 | necessary, any volumes determined to be erroneous.
|
---|
| 298 | Unusual volumes are those where either the Operation Time,
|
---|
| 299 | Patient Time, or Anesthesia Time field is greater than the
|
---|
| 300 | threshold value.
|
---|
| 301 | The report is sorted by descending Volume and Case Number.
|
---|
| 302 | The default threshold volume for the Surgery extract is
|
---|
| 303 | #################### #################### ####################
|
---|
| 304 | #################### #################### ####################
|
---|
| 305 | #################### #################### ####################
|
---|
| 306 | #################### #################### ####################
|
---|
| 307 | #################### #################### ####################
|
---|