| [604] | 1 | English French Notes Complete/Exclude
|
|---|
| 2 | Summary for division:
|
|---|
| 3 | For clinics with credit pair:
|
|---|
| 4 | For clinics with selected credit pair
|
|---|
| 5 | For clinics selected by name
|
|---|
| 6 | SDARR(
|
|---|
| 7 | Clinic Stop Code Pair:
|
|---|
| 8 | Detail for clinic:
|
|---|
| 9 | Ava.
|
|---|
| 10 | Pct.
|
|---|
| 11 | Credit Pair
|
|---|
| 12 | Sch. Wait
|
|---|
| 13 | Availability Date
|
|---|
| 14 | Enc.
|
|---|
| 15 | Appts Time
|
|---|
| 16 | Days Days
|
|---|
| 17 | Non-next Available Appointments
|
|---|
| 18 | Next Ava. 0-1 0-1 2-7 2-7 8-30 8-30 31-60 31-60 >60 >60
|
|---|
| 19 | Ava. Wait
|
|---|
| 20 | Days Wait
|
|---|
| 21 | Appts Time
|
|---|
| 22 | Next Ava. 0-1 0-1 0-1 2-7 2-7 2-7 8-30 8-30 8-30 31-60 31-60 31-60 >60 >60 >60
|
|---|
| 23 | Ava. Wait
|
|---|
| 24 | Days Wait Wait
|
|---|
| 25 | Appts Time1
|
|---|
| 26 | Appts Time1 Time2
|
|---|
| 27 | Ava. Date Wait Wait
|
|---|
| 28 | Scheduled Patient Name SSN Appointment Date Scheduling Request Type Ind. Desired F/U Time1 Time2
|
|---|
| 29 | REBOOK DATE
|
|---|
| 30 | Date extracted:
|
|---|
| 31 | No appointments scheduled during this date range were found.
|
|---|
| 32 | Next available
|
|---|
| 33 | Not-next ava-C/R
|
|---|
| 34 | Not-next ava-P/R
|
|---|
| 35 | Walk in appoint
|
|---|
| 36 | Multi booking
|
|---|
| 37 | Auto rebook
|
|---|
| 38 | Not-next available
|
|---|
| 39 | NOTE: TYPE '0' represents appointments scheduled during the report time frame not indicated by the user or by calculation to be
|
|---|
| 40 | 'next available' appointments. TYPE '1' represents appointments defined by the user as being 'next available' appointments. TYPE
|
|---|
| 41 | '2' represents appointments calculated to be 'next available' appointments. TYPE '3' represents appointments indicated both by the
|
|---|
| 42 | user and by calculation to be 'next available' appointments. WAIT TIME is the average number of days from the date an appointment
|
|---|
| 43 | was scheduled to the date it is to be performed. The '% NNA' and '% NA' columns reflect percentage of appointments scheduled within
|
|---|
| 44 | 30 days for 'non-next available' appointments (types 0 & 2) and 'next available' appointments (types 1 & 3), respectively.
|
|---|
| 45 | NOTE: The date range categories ('0-1', '2-7', '8-30', etc.) are based on the difference between the 'desired date' defined for the
|
|---|
| 46 | appointment and the date the appointment was performed. 'Wait Time' reflects the average of this difference for all appointments in
|
|---|
| 47 | each category. 'Follow up' status is determined by encounter activity to the same DSS ID credit pair as the appointment clinic
|
|---|
| 48 | within the previous 24 months.
|
|---|
| 49 | the date the appointment was performed. 'Wait Time2' reflects the average difference between the transaction date (the date the
|
|---|
| 50 | appointment was entered by the Scheduling package user) and the date the appointment was performed. 'Non-follow up' status is
|
|---|
| 51 | determined by the absence of encounter activity to the same DSS ID credit pair as the appointment clinic in the previous 24 months.
|
|---|
| 52 | NOTE: 'Next Ava. Ind.' Values--'0' = not indicated by the user or calculation to be a 'next available' appointment, '1' = defined
|
|---|
| 53 | by the user as a 'next available' appointment, '2' = indicated by calculation to be a 'next available' appointment, '3' = indicated
|
|---|
| 54 | by the user and by calculation to be a 'next available' appointment. 'Wait Time1' = the difference between the 'date desired' and
|
|---|
| 55 | the date of the appointment. 'Wait Time2' = the difference between the 'date scheduled' and the date of the appointment.
|
|---|
| 56 | Select PATIENT NAME:
|
|---|
| 57 | Correct Patient?
|
|---|
| 58 | No Patient Selected, OK to proceed?
|
|---|
| 59 | ACT REQ
|
|---|
| 60 | NOTE: 'APPT TYPE' Values--'0' = user indicated 'Not next available' and calculation indicated 'Not next available' used
|
|---|
| 61 | '1' = user indicated 'Next available' but calculation indicated next available appt not used
|
|---|
| 62 | '2' = user indicated 'Not next available' but calculation indicated next available appointment used
|
|---|
| 63 | '3' = user indicated 'Next available' and calculation indicated 'Next available' apppointment used
|
|---|
| 64 | WAIT TIME: -------------- the difference between the 'DATE DESIRED' and 'APPT DATE/TIME'
|
|---|
| 65 | TIME TO APPT.: ----------- days from 'DATE SCHEDULED' to 'APPT DATE/TIME'
|
|---|
| 66 | APPT STATUS: N - No-show, CC - Canceled by Clinic, NA - No Show & Auto Rebook, CCA -Canceled by Clinic & Auto Rebook,
|
|---|
| 67 | I - Inpatient, CP - Canceled by Patient, CPA - Canceled by Patient & Auto Rebook, NT - No Action Taken,
|
|---|
| 68 | F - Future, CI - Checked In, COA - Checked Out/Action Required, CO - Checked Out
|
|---|
| 69 | No activity found within the parameters specified.
|
|---|
| 70 | O U T P A T I E N T V I S I T S
|
|---|
| 71 | Act. Req./not accepted visits
|
|---|
| 72 | Transmitted, accepted visits
|
|---|
| 73 | O U T P A T I E N T U N I Q U E S
|
|---|
| 74 | Act. Req./not accepted unique pts.
|
|---|
| 75 | Transmitted, accepted unique pts.
|
|---|
| 76 | <*> OUTPATIENT ENCOUNTER WORKLOAD STATISTICS <*>
|
|---|
| 77 | For encounter dates
|
|---|
| 78 | For station:
|
|---|
| 79 | ***NONE ASSIGNED***
|
|---|
| 80 | Please select fiscal year
|
|---|
| 81 | XMITED OE MT=U RPT
|
|---|
| 82 | SCDX MTU
|
|---|
| 83 | SCDX ASORT
|
|---|
| 84 | Outpatient Encounters Scanned
|
|---|
| 85 | Outpatient Encounters Reported
|
|---|
| 86 | Patient Count
|
|---|
| 87 | ACRP MT=U STATS
|
|---|
| 88 | Transmitted Outpatient Encounters with Means Test = 'U'
|
|---|
| 89 | Medical Ctr
|
|---|
| 90 | Encounter Date
|
|---|
| 91 | MT Indicator
|
|---|
| 92 | * - Transmitted Outpatient Encounter
|
|---|
| 93 | No 'action required'/not accepted unique patients identified.
|
|---|
| 94 | 'action required'/not accepted unique patient
|
|---|
| 95 | <*> LIST OF 'ACTION REQUIRED'/NOT ACCEPTED UNIQUE PATIENTS <*>
|
|---|
| 96 | Would you like to print a detailed list of activity for a division
|
|---|
| 97 | WARNING: Selection high activity areas will result in lengthy output!
|
|---|
| 98 | Select type of list
|
|---|
| 99 | Select transmission status for CHECKED OUT encounters
|
|---|
| 100 | 5:Transmitted, no acknowledgment;6:Transmitted, rejected;7:Transmitted, error;8:Transmitted, accepted
|
|---|
| 101 | Select Medical Center division for detail:
|
|---|
| 102 | Required for patient detail!
|
|---|
| 103 | <*> DETAILED LIST OF DIVISION
|
|---|
| 104 | Encounters with
|
|---|
| 105 | Transmission status:
|
|---|
| 106 | No records found in this category.
|
|---|
| 107 | uniques identified.
|
|---|
| 108 | visits identified.
|
|---|
| 109 | encounters identified.
|
|---|
| 110 | Outpatient Encounter Workload Statistics
|
|---|
| 111 | *** Additional Detail Selection ***
|
|---|
| 112 | Break out workload by clinic group
|
|---|
| 113 | Specify if subtotals by encounter location CLINIC GROUP should be provided.
|
|---|
| 114 | List facility 'action required'/not accepted unique patients
|
|---|
| 115 | Outpatient Encounter Workload
|
|---|
| 116 | SDZ(
|
|---|
| 117 | An error has occurred.
|
|---|
| 118 | CURRENT USER
|
|---|
| 119 | Scheduling User Data Retrieval
|
|---|
| 120 | System Default
|
|---|
| 121 | Setting User Query Default
|
|---|
| 122 | NULL XMT POINTER
|
|---|
| 123 | No (Deleted) Outpatient Encounter entry found.
|
|---|
| 124 | Select Patient name, Clinic name, or Error Code:
|
|---|
| 125 | Enter as P.patient name, C.clinic name, or E.error name
|
|---|
| 126 | Searching for patient
|
|---|
| 127 | Searching for Clinic
|
|---|
| 128 | Searching for Error Code
|
|---|
| 129 | Answer with Yes to accept, or No to ignore
|
|---|
| 130 | Enter P.patient name to select a specific patient,
|
|---|
| 131 | C.clinic name to select a specific clinic, or E.Error Name
|
|---|
| 132 | to select a specific error.
|
|---|
| 133 | If selecting a specific error by its description it may be
|
|---|
| 134 | necessary to enter more than three characters(Ex. E.Abxxxx).
|
|---|
| 135 | Because this is a descriptive field, case sensitivity applies.
|
|---|
| 136 | If just a name is entered, any matches will be displayed in
|
|---|
| 137 | patient, clinic, error code order. You will have the option
|
|---|
| 138 | of selecting or ignoring the choice.
|
|---|
| 139 | Scheduling Option^1N
|
|---|
| 140 | OPC MENU NOW USED!
|
|---|
| 141 | OPTIONS MUST BE INDIVIDUALLY CALLED!
|
|---|
| 142 | Special Survey functionality is obsolete!
|
|---|
| 143 | SUPERVISOR OPTIONS NO LONGER ACCESSIBLE!
|
|---|
| 144 | Environmental Checks Started...
|
|---|
| 145 | Environmental Checks Completed.
|
|---|
| 146 | Passed
|
|---|
| 147 | on the 'SDAM APPOINTMENT EVENTS' protocol
|
|---|
| 148 | is a dangling pointer and must be corrected/removed
|
|---|
| 149 | before patch SD*5.3*132 can be installed.
|
|---|
| 150 | Please contact the Customer Support Help Desk for assistance.
|
|---|
| 151 | -> At least one patch check failed.
|
|---|
| 152 | -> All patch checks passed.
|
|---|
| 153 | not Ok
|
|---|
| 154 | SD*5.3*132 OVERRIDE FLAGS
|
|---|
| 155 | PACKAGE NAME
|
|---|
| 156 | NEEDED VERSION
|
|---|
| 157 | REASON TEXT
|
|---|
| 158 | REASON NUMBER
|
|---|
| 159 | Information On Patches Needed For SD*5.3*132 Install
|
|---|
| 160 | Patch or
|
|---|
| 161 | ...invalid namespace passed!
|
|---|
| 162 | ...override set for '
|
|---|
| 163 | ...override killed for '
|
|---|
| 164 | Post-Init Started...
|
|---|
| 165 | Post-Init Finished.
|
|---|
| 166 | >>> Deleting MAS PARAMETERS (#43) fields...
|
|---|
| 167 | >>> Deleting HOSPITAL LOCATION (#44) fields...
|
|---|
| 168 | >>> Deleting APPPOINT STATUS UPDATE LOG (409.65) fields...
|
|---|
| 169 | >>> Setting 'ACG' cross references...
|
|---|
| 170 | >>> Queuing task to set 'AG' cross reference.
|
|---|
| 171 | SDACS CGSCLIST
|
|---|
| 172 | AG Cross Reference Being Set
|
|---|
| 173 | -> Option 'SDACS CGSCLIST' has been placed out of service.
|
|---|
| 174 | Setting 'AG' Cross Reference
|
|---|
| 175 | >>> Option 'SDACS CGSCLIST' is back in service.
|
|---|
| 176 | Setting of 'AG' Cross Reference Task Information
|
|---|
| 177 | >>> Package Override Flag Information
|
|---|
| 178 | -> Override flag set for '
|
|---|
| 179 | -> No package override flags set.
|
|---|
| 180 | -> Fields already deleted.
|
|---|
| 181 | SD-SITE-PAIT
|
|---|
| 182 | Unable to update FACILITY NAME field of file 771
|
|---|
| 183 | Edit entry SD-SITE-PAIT manually
|
|---|
| 184 | HL7 Parameters Updated Successfully
|
|---|
| 185 | RE-LINKED
|
|---|
| 186 | Re-Linked successfully:
|
|---|
| 187 | Error has occurred.
|
|---|
| 188 | Please make a note of the following:
|
|---|
| 189 | Fix -1 Outpatient Encounters
|
|---|
| 190 | Task queued: #
|
|---|
| 191 | SDVISIT FIX
|
|---|
| 192 | COUNT ONLY
|
|---|
| 193 | Bad encounter entry passed
|
|---|
| 194 | Unknown Clinic
|
|---|
| 195 | ERROR OCCURRED
|
|---|
| 196 | SD TO PCE RESYNC
|
|---|
| 197 | >>>> Encounter Clean Up Tool for -1 Visit ID's [
|
|---|
| 198 | DUZ is not defined.
|
|---|
| 199 | No package with 'SD' namespace exists on the system.
|
|---|
| 200 | The Unique Visit ID cleanup has run to completion.
|
|---|
| 201 | End Time:
|
|---|
| 202 | Run Mode:
|
|---|
| 203 | Count Only
|
|---|
| 204 | Fix Entries
|
|---|
| 205 | >>> Task Stopped by user. <<<
|
|---|
| 206 | Total number of Outpatient Encounter entries
|
|---|
| 207 | that will be
|
|---|
| 208 | Note: Child encounters re-linked as part of parent
|
|---|
| 209 | re-linking process are not listed below nor
|
|---|
| 210 | counted in the total above.
|
|---|
| 211 | Message Format:
|
|---|
| 212 | Piece Description
|
|---|
| 213 | 1 Status of update
|
|---|
| 214 | 2 Internal Entry Number of Outpatient Encounter file
|
|---|
| 215 | 3 Internal Entry Number of Parent Outpatient Encounter file
|
|---|
| 216 | 4 Internal Entry Number of Visit file
|
|---|
| 217 | 5 Patient Name
|
|---|
| 218 | 6 Encounter Date/Time
|
|---|
| 219 | 7 Hospital Location
|
|---|
| 220 | Unique Visit ID Cleanup is Complete
|
|---|
| 221 | SDVISIT MSG
|
|---|
| 222 | 1:Count Only;2:Fix Entries
|
|---|
| 223 | Select update mode
|
|---|
| 224 | You are running this routine in scan mode, which will only identify
|
|---|
| 225 | the problems corrected. Please select a device (queueing allowed) so
|
|---|
| 226 | that a listing of what would have been done can be obtained.
|
|---|
| 227 | ACRP cleanup of files 409.73, 409.74, and 409.75
|
|---|
| 228 | Please enter the date/time that you would like this clean up queued to
|
|---|
| 229 | run. A summary of what was done will be sent to you and the
|
|---|
| 230 | recipients of the SCDX AMBCARE TO NPCDB SUMMARY bulletin.
|
|---|
| 231 | ** Unable to schedule correction **
|
|---|
| 232 | This routine will clean up dangling pointers and orphan entries within
|
|---|
| 233 | the ACRP transmission files. The following actions/checks will be
|
|---|
| 234 | (1) Entries in the Transmitted Outpatient Encounter file (409.73)
|
|---|
| 235 | that do not have a valid pointer to the Outpatient Encounter
|
|---|
| 236 | file (#409.68) or the Deleted Outpatient Encounter file
|
|---|
| 237 | (#409.74) are deleted.
|
|---|
| 238 | (2) Entries in the Transmitted Outpatient Encounter file that have
|
|---|
| 239 | been rejected by the Austin Automation Center and do not have an
|
|---|
| 240 | entry in the Transmitted Outpatient Encounter Error file
|
|---|
| 241 | (#409.75) are marked for re-transmission.
|
|---|
| 242 | (3) Entries in the Deleted Outpatient Encounter file that do not
|
|---|
| 243 | have a corresponding entry in the Transmitted Outpatient
|
|---|
| 244 | Encounter file are deleted.
|
|---|
| 245 | (4) Entries in the Transmitted Outpatient Encounter Error file that
|
|---|
| 246 | do not have a valid pointer to the Transmitted Outpatient
|
|---|
| 247 | Scanning of the Transmitted Outpatient Encounter, Deleted Outpatient
|
|---|
| 248 | Encounter, and Transmitted Outpatient Encounter Error files for known
|
|---|
| 249 | problems started on
|
|---|
| 250 | The following entries in the Transmitted Outpatient Encounter
|
|---|
| 251 | file (#409.73) will be acted upon when run in fix mode
|
|---|
| 252 | ,0) has bad pointer to Outpatient Encounter file
|
|---|
| 253 | ,0) has bad pointer to Deleted Outpatient Encounter file
|
|---|
| 254 | ,0) rejected with no reason on file (entry in 409.75)
|
|---|
| 255 | Last entry in Transmitted Outpatient Encounter file checked >>
|
|---|
| 256 | entries where checked
|
|---|
| 257 | would have been marked for retransmission
|
|---|
| 258 | would have been deleted
|
|---|
| 259 | have bad Outpatient Encounter pointers
|
|---|
| 260 | have bad Deleted Outpatient Encounter pointers
|
|---|
| 261 | The following entries in the Deleted Outpatient Encounter
|
|---|
| 262 | file (#409.74) will be deleted when run in fix mode
|
|---|
| 263 | ,0) not in Transmitted Outpatient Encounter file
|
|---|
| 264 | Last entry in Deleted Outpatient Encounter file checked >>
|
|---|
| 265 | entries where checked and
|
|---|
| 266 | Error file (#409.75) will be deleted when run in fix mode
|
|---|
| 267 | ,0) has bad pointer to Transmitted Outpatient Encounter file
|
|---|
| 268 | Scan ended on
|
|---|
| 269 | Use the entry point FIX^SD53105A to run in fix mode
|
|---|
| 270 | Use the entry point SCAN^SD53105A to re-run in scan mode
|
|---|
| 271 | SD53105-BULL1
|
|---|
| 272 | *** Note that process was asked to stop and did not run to completion ***
|
|---|
| 273 | Process began on
|
|---|
| 274 | and completed on
|
|---|
| 275 | entries in the Transmitted Outpatient Encounter file were
|
|---|
| 276 | checked and
|
|---|
| 277 | of them were deleted because of bad pointers to the
|
|---|
| 278 | Outpatient Encounter file and
|
|---|
| 279 | of them were deleted because of bad
|
|---|
| 280 | pointers to the Deleted Outpatient Encounter file. In addition to this,
|
|---|
| 281 | entries were marked for re-transmission because they were rejected and
|
|---|
| 282 | did not contain a reason for rejection in the Transmitted Outpatient
|
|---|
| 283 | Encounter Error file.
|
|---|
| 284 | entries in the Deleted Outpatient Encounter file were
|
|---|
| 285 | of them were deleted because an associated entry in the
|
|---|
| 286 | Transmitted Outpatient Encounter file could not be found.
|
|---|
| 287 | were checked and
|
|---|
| 288 | Transmitted Outpatient Encounter file.
|
|---|
| 289 | ACRP - SD*5.3*105
|
|---|
| 290 | >>> Deleting obsolete triggers on the TRANSMISSION REQUIRED field
|
|---|
| 291 | (#.04) of the TRANSMITTED OUTPATIENT ENCOUNTER file (#409.73).
|
|---|
| 292 | Trigger cross reference number
|
|---|
| 293 | >>> Updating the ERROR CODE DESCRIPTION field (#11) of
|
|---|
| 294 | the TRANSMITTED OUTPATIENT ENCOUNTER ERROR CODE file
|
|---|
| 295 | (#409.76) for error codes 420 and 105. Definitions
|
|---|
| 296 | were modified to reflect receipt of data by NPCD
|
|---|
| 297 | after close-out.
|
|---|
| 298 | Date of Encounter is invalid, after date of transmission, or after close-out.
|
|---|
| 299 | Event Date is missing, invalid, after processing date, or after close-out.
|
|---|
| 300 | *** The following error occurred while updating descriptions ***
|
|---|
| 301 | >>> Checking for existance of a valid mail group in the
|
|---|
| 302 | LATE ACTIVITY MAIL GROUP field (#217) of the MAS
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
