| [604] | 1 | English French Notes Complete/Exclude
|
|---|
| 2 | No aberrant documents found...
|
|---|
| 3 | I like New York in June, how about you?
|
|---|
| 4 | I like a Gershwin tune, how about you?
|
|---|
| 5 | IS EVERYTHING OK?
|
|---|
| 6 | TIU IS THIS A CLINPROC?
|
|---|
| 7 | TIU IDENTIFY CLINPROC CLASS
|
|---|
| 8 | TIU LONG LIST CLINPROC TITLES
|
|---|
| 9 | You already have a CLASS called CLINICAL PROCEDURES...
|
|---|
| 10 | The new methods and properties to support the TIU/CP interface
|
|---|
| 11 | will be MERGED with the existing data. UPLOAD HEADERS
|
|---|
| 12 | which you have defined will NOT be overwritten.
|
|---|
| 13 | I'm going to create a new Document Definition for CLINICAL PROCEDURES now.
|
|---|
| 14 | Couldn't create Document Definition entry for CLINICAL PROCEDURES...
|
|---|
| 15 | CLINICAL PROCEDURES^CP^Clinical Procedures^CL^^
|
|---|
| 16 | Progress Notes^Vice SF 509^^0
|
|---|
| 17 | VISIT/EVENT DATE^VISIT/EVENT DATE^.07^TIUVDT^5/15/2001@08:15^1^1
|
|---|
| 18 | DATE/TIME OF DICTATION^DICTATION DATE/TIME^1307^TIUDDT^5/16/2001@09:25^0^1
|
|---|
| 19 | EXPECTED COSIGNER^EXPECTED COSIGNER^1208^^WELBY,MARCUS^1^0
|
|---|
| 20 | CONSULT REQUEST NUMBER^CONSULT REQUEST #^1405^TIUCNNBR^1455^1^1
|
|---|
| 21 | TIU DOCUMENT NUMBER^TIU DOCUMENT #^.001^TIUPLDA^543^1^0
|
|---|
| 22 | PROCEDURE SUMMARY CODE^PROCEDURE SUMMARY CODE^70201^TIUPSC^Normal^1^0
|
|---|
| 23 | DATE/TIME PERFORMED^DATE/TIME PERFORMED^70202^TIUDTP^5/15/2001@08:00^1^0
|
|---|
| 24 | The new CLINICAL PROCEDURES Class will now be added under
|
|---|
| 25 | Unable to add CLINICAL PROCEDURES under
|
|---|
| 26 | You'll have to attach it manually.
|
|---|
| 27 | Okay, I'm done.
|
|---|
| 28 | Please finish your implementation of CLINICAL PROCEDURES by adding
|
|---|
| 29 | any Document Classes and Titles as appropriate using the Create
|
|---|
| 30 | Document Definitions Option under the TIUF DOCUMENT DEFINITION MGR Menu
|
|---|
| 31 | as described in the Post-Installation Instructions.
|
|---|
| 32 | BUILDING NEW
|
|---|
| 33 | CROSS-REFERENCE ON FILE 8925.1
|
|---|
| 34 | This option creates Document Definitions, a User Class, and
|
|---|
| 35 | Business Rules for Laboratory Reports.
|
|---|
| 36 | Create DDefs, User Class, Rules for Laboratory Reports - TIU*1*137
|
|---|
| 37 | ***** Document Definitions for LABORATORY REPORTS *****
|
|---|
| 38 | Duplicate problem. See description for patch TIU*1*137,
|
|---|
| 39 | in the National Patch Module.
|
|---|
| 40 | was already created in a previous install.
|
|---|
| 41 | Couldn't create a
|
|---|
| 42 | Please contact National VistA Support for help.
|
|---|
| 43 | created successfully.
|
|---|
| 44 | Couldn't add entry to parent. Please contact National VistA Support
|
|---|
| 45 | for help.
|
|---|
| 46 | Entry added to parent.
|
|---|
| 47 | Problem filing data for entry. Please contact National VistA Support.
|
|---|
| 48 | Data for entry filed successfully.
|
|---|
| 49 | TIUPS139 Cleanup Routine
|
|---|
| 50 | Elapsed Time:
|
|---|
| 51 | # of Records:
|
|---|
| 52 | Searched
|
|---|
| 53 | (STATUS=UNCOSIGNED, EXPECTED COSIGNER=
|
|---|
| 54 | (COSIGNATURE REQUIRED=NO)
|
|---|
| 55 | (COSIGNATURE REQUIRED=YES)
|
|---|
| 56 | * co-signer requirement should be verified
|
|---|
| 57 | Host File Path:
|
|---|
| 58 | TIUPS139.TXT
|
|---|
| 59 | Current User:
|
|---|
| 60 | Current Date:
|
|---|
| 61 | Date range searched:
|
|---|
| 62 | Count Entry Date/Time
|
|---|
| 63 | Doc # Title Author/Dictator
|
|---|
| 64 | <NO RECORDS FOUND>
|
|---|
| 65 | ** The following records are STATUS=UNCOSIGNED COSIGNATURE REQUIRED=YES **
|
|---|
| 66 | TIUPS139 has finished.
|
|---|
| 67 | Delete the host file TIUPS139.TXT and QUIT
|
|---|
| 68 | Entering 'NO' will not delete the host file TIUPS139.TXT and continue.
|
|---|
| 69 | Entering 'YES' will delete the host file TIUPS139.TXT and QUIT.
|
|---|
| 70 | TIUPS139.TXT has been deleted.
|
|---|
| 71 | START WITH REFERENCE DATE:
|
|---|
| 72 | GO TO REFERENCE DATE:
|
|---|
| 73 | Jan 01, 2001
|
|---|
| 74 | Update the records at this time
|
|---|
| 75 | Entering 'YES' will find and update the records.
|
|---|
| 76 | STATUS will be changed from 'UNCOSIGNED' to 'COMPLETED' and
|
|---|
| 77 | COSIGNATURE NEEDED will be changed to 'NO'.
|
|---|
| 78 | Entering 'NO' will find and report the records without making any changes.
|
|---|
| 79 | Would you like to print or queue the search
|
|---|
| 80 | Entering 'YES' will send the search results to the selected device.
|
|---|
| 81 | It will also allow the search to be queued and run at a later time if desired.
|
|---|
| 82 | Entering 'NO' will not allow printing or queuing of the search results.
|
|---|
| 83 | The search results will be displayed on the current device.
|
|---|
| 84 | INVALID USER
|
|---|
| 85 | INVALID USER CLASS
|
|---|
| 86 | TIUPS139 WORKSTATION
|
|---|
| 87 | TIUPS139 Workstation HFS Device
|
|---|
| 88 | TIUPS139.DAT
|
|---|
| 89 | Workstation device creation failed.
|
|---|
| 90 | You must install CONSULT/REQUEST TRACKING 3.0 before
|
|---|
| 91 | implementing this part of patch TIU*1*4.
|
|---|
| 92 | called CONSULTS under
|
|---|
| 93 | PRINT METHODS which you have defined will NOT be overwritten.
|
|---|
| 94 | Okay to continue
|
|---|
| 95 | Great...No harm done!
|
|---|
| 96 | Okay, I'm done...Please finish your implementation of CONSULTS by
|
|---|
| 97 | adding any
|
|---|
| 98 | Document Classes and
|
|---|
| 99 | Titles
|
|---|
| 100 | as appropriate using the Create Document Definitions
|
|---|
| 101 | Option
|
|---|
| 102 | under the TIUF DOCUMENT DEFINITION MGR Menu, as described in
|
|---|
| 103 | of the Post-Installation Instructions.
|
|---|
| 104 | GREAT! A new Document Definition has been created for CONSULTS.
|
|---|
| 105 | Next, you need to decide whether you want CONSULTS to be set up
|
|---|
| 106 | as a separate CLASS (comparable to DISCHARGE SUMMARY or PROGRESS
|
|---|
| 107 | NOTES), or whether you want CONSULTS defined as a DOCUMENT CLASS
|
|---|
| 108 | under PROGRESS NOTES. The benefits of each strategy are outlined
|
|---|
| 109 | in the POST-INSTALLATION instructions for this patch.
|
|---|
| 110 | NOTE: If you're not yet CERTAIN which strategy you want your site
|
|---|
| 111 | to adopt, then quit here, and get consensus first (it's easier to
|
|---|
| 112 | get permission than forgiveness, in this case)!
|
|---|
| 113 | Define CONSULTS as a CLASS or DOCUMENT CLASS
|
|---|
| 114 | Okay, you've indicated that you want to make CONSULTS a
|
|---|
| 115 | FANTASTIC! Your NEW
|
|---|
| 116 | CONSULTS will now be added under
|
|---|
| 117 | Unable to add CONSULTS under
|
|---|
| 118 | PATIENT ETHNICITY
|
|---|
| 119 | TIU Object failed. The following error message was returned:
|
|---|
| 120 | TIU Object created successfully
|
|---|
| 121 | remove erroneous ACLAU and ACLEC cross-references.
|
|---|
| 122 | An alert will be sent to the initiator of this patch
|
|---|
| 123 | at completion.
|
|---|
| 124 | TIUPS153 Cleanup Routine
|
|---|
| 125 | TIUPS153 has finished.
|
|---|
| 126 | TIU HAS AUTHOR SIGNED?
|
|---|
| 127 | TIU ONE VISIT NOTE?
|
|---|
| 128 | TIU USER INACTIVE?
|
|---|
| 129 | a Business Rule for Patient Record Flags.
|
|---|
| 130 | Create DDefs, User Class, Rules for Patient Record Flags - TIU*1*165
|
|---|
| 131 | ***** Document Definitions for PATIENT RECORD FLAGS *****
|
|---|
| 132 | This routine has already been run...
|
|---|
| 133 | Adding Boilerplated Titles and Patient Data Objects to Shared Templates...
|
|---|
| 134 | Shared Templates
|
|---|
| 135 | Boilerplated Titles
|
|---|
| 136 | Patient Data Objects
|
|---|
| 137 | TIU Objects
|
|---|
| 138 | Boilerplate Titles
|
|---|
| 139 | Shared Templates Root Created.
|
|---|
| 140 | Boilerplated Titles Folder Created.
|
|---|
| 141 | Folder added.
|
|---|
| 142 | Patient Data Objects Folder Created.
|
|---|
| 143 | ** FIND CONVERTED NOTES WITH COSIGNER'S COMMENTS **
|
|---|
| 144 | COSIGNER'S COMMENT:
|
|---|
| 145 | GMR->TIU
|
|---|
| 146 | ** REMOVING PROGRESS NOTES v2.5 DB & DD's **
|
|---|
| 147 | ** REMOVING DISCHARGE SUMMARY v1.0 DB & DD's **
|
|---|
| 148 | ** REMOVING DISCHARGE SUMMARY v1.0 FILEMAN FUNCTIONS **
|
|---|
| 149 | GMRD ISADDENDUM
|
|---|
| 150 | GMRD NAME FORMAT
|
|---|
| 151 | GMRD TREAT SPEC NAME
|
|---|
| 152 | Deleting:
|
|---|
| 153 | FDA(396.4,
|
|---|
| 154 | Select 2507 EXAM REFERENCE NUMBER:
|
|---|
| 155 | TOTALS FOR CURRENT BATCH:
|
|---|
| 156 | TOTAL Document(s) RECEIVED:
|
|---|
| 157 | Document(s) NOT FILED:
|
|---|
| 158 | Document(s) FILED with MISSING FIELDS:
|
|---|
| 159 | FDA(
|
|---|
| 160 | Filed Successfully.
|
|---|
| 161 | >>> HEADER IDENTIFIED:
|
|---|
| 162 | INVALID DOCUMENT TYPE
|
|---|
| 163 | TARGET FILE NOT DEFINED FOR
|
|---|
| 164 | TEXT FIELD NOT DEFINED FOR
|
|---|
| 165 | Field Number NOT SPECIFIED for
|
|---|
| 166 | LOOK-UP FAILED FOR
|
|---|
| 167 | now Linked to Consult Request #:
|
|---|
| 168 | INCOMPLETE RPT
|
|---|
| 169 | Linked to Consult Request #:
|
|---|
| 170 | Please correct the buffered upload data.
|
|---|
| 171 | Document #:
|
|---|
| 172 | Dated:
|
|---|
| 173 | MM/DD/CCYY@HR:MIN
|
|---|
| 174 | Select Patient or Surgery Case Number:
|
|---|
| 175 | OK, you can try again later
|
|---|
| 176 | ... Is this the correct Surgery record
|
|---|
| 177 | To file the transcribed Surgeon's Dictation into the Surgery record you have
|
|---|
| 178 | just selected, you will need to correct the upload data in its temporary
|
|---|
| 179 | storage place, and then try again to file it.
|
|---|
| 180 | The stored upload header data for
|
|---|
| 181 | should be corrected to read:
|
|---|
| 182 | PATIENT SSN:
|
|---|
| 183 | CASE NUMBER:
|
|---|
| 184 | OPERATION DATE:
|
|---|
| 185 | Can't find stored upload record; see IRM
|
|---|
| 186 | You may now correct the stored upload data.
|
|---|
| 187 | Are you ready to file this data in the Surgery file
|
|---|
| 188 | OK, you can try again later.
|
|---|
| 189 | Filing Record//Resolving Error...
|
|---|
| 190 | Old error marked resolved; new error created. New error may take several more
|
|---|
| 191 | seconds to file, and may not be within current date/time range.
|
|---|
| 192 | Is this the Surgery record you wish to upload the transcribed data into?
|
|---|
| 193 | If not, answer NO and select a different record, or enter '^' to come back
|
|---|
| 194 | and resolve the filing error later.
|
|---|
| 195 | If you are sure that you have identified the correct Surgery record, and have
|
|---|
| 196 | corrected the stored header data accordingly, then answer YES to try again
|
|---|
| 197 | to upload the data into the Surgery record.
|
|---|
| 198 | If you answer NO, the corrected data will remain in temporary storage,
|
|---|
| 199 | the filing error alert will remain in place, and you can attempt to resolve
|
|---|
| 200 | the alert later.
|
|---|
| 201 | ICD(
|
|---|
| 202 | TIUPRLST(
|
|---|
| 203 | TIU/PXAPI RESOURCE
|
|---|
| 204 | TIU/PCE/AmbCare API Call
|
|---|
| 205 | You MUST enter one or more Procedures.
|
|---|
| 206 | Insufficient information for Workload Credit.
|
|---|
| 207 | Missing information will have to be captured by another method.
|
|---|
| 208 | Changes Discarded. Please Enter Corrected Workload Data...
|
|---|
| 209 | Do you wish to enter workload data at this time
|
|---|
| 210 | Visit on
|
|---|
| 211 | ACRP will not accept data for future Encounters.
|
|---|
| 212 | Workload questions won't be asked for this note.
|
|---|
| 213 | Editing Encounter Data...
|
|---|
| 214 | OTHER CPT^OTHER Procedure
|
|---|
| 215 | the Patient
|
|---|
| 216 | Please Indicate the Procedure(s) Performed on
|
|---|
| 217 | Select Procedures
|
|---|
| 218 | (<RETURN> to see next page of choices)
|
|---|
| 219 | How many times was the procedure performed?
|
|---|
| 220 | Please specify the number of repetitions for this procedure
|
|---|
| 221 | performed during this visit with the patient (1-99).
|
|---|
| 222 | Another Procedure
|
|---|
| 223 | (NOT from Above List)
|
|---|
| 224 | Nothing found for
|
|---|
| 225 | Please try another expression, or RETURN to continue:
|
|---|
| 226 | You MUST enter one or more Diagnoses.
|
|---|
| 227 | Posting Workload Credit...
|
|---|
| 228 | You have indicated the following data apply to this visit:
|
|---|
| 229 | DIAGNOSES:
|
|---|
| 230 | SERVICE CONNECTION:
|
|---|
| 231 | Service Connected?
|
|---|
| 232 | Agent Orange?
|
|---|
| 233 | Ionizing Radiation?
|
|---|
| 234 | Environmental Contaminants?
|
|---|
| 235 | MST?
|
|---|
| 236 | Head and/or Neck Cancer?
|
|---|
| 237 | OTHER ICD^OTHER Diagnosis
|
|---|
| 238 | Please Indicate the Diagnoses for which
|
|---|
| 239 | was Seen:
|
|---|
| 240 | Select Diagnoses
|
|---|
| 241 | OTHER ICD
|
|---|
| 242 | Please indicate which of the Diagnoses is the Primary Diagnosis:
|
|---|
| 243 | Select Diagnosis
|
|---|
| 244 | You must specify a Primary Diagnosis.
|
|---|
| 245 | You must install LEXICON UTILITY v2.0 for this function to work...Contact IRM.
|
|---|
| 246 | Another Diagnosis
|
|---|
| 247 | ICD CODE NOT FOUND FOR EXPRESSION.
|
|---|
| 248 | Selected user is not a known PROVIDER. Please choose another...
|
|---|
| 249 | Select PRIMARY PROVIDER:
|
|---|
| 250 | This CPT Modifier has already been selected.
|
|---|
| 251 | Current CPT Modifiers:
|
|---|
| 252 | CPT Modifier(s):
|
|---|
| 253 | Was this encounter related to any of the following:
|
|---|
| 254 | Service Connected Condition
|
|---|
| 255 | (Y)ES or (N)o Required.
|
|---|
| 256 | An '^' is not allowed.
|
|---|
| 257 | Agent Orange Exposure
|
|---|
| 258 | Ionizing Radiation Exposure
|
|---|
| 259 | Environmental Contaminants
|
|---|
| 260 | Enter 'Y' or 'N' if treatment was related to Military Sexual Trauma.
|
|---|
| 261 | Head and/or Neck Cancer
|
|---|
| 262 | Document.Title
|
|---|
| 263 | Document.Reference
|
|---|
| 264 | Document.Status
|
|---|
| 265 | Document.Author
|
|---|
| 266 | Document.Cosigner
|
|---|
| 267 | UNSIGNED,UNCOSIGNED
|
|---|
| 268 | You must select one or more TITLES...
|
|---|
| 269 | NOT PICKED
|
|---|
| 270 | No records found to satisfy search criteria.
|
|---|
| 271 | There are
|
|---|
| 272 | items (Interdisciplinary Notes, Addenda) to expand
|
|---|
| 273 | in a list of
|
|---|
| 274 | NO saves time building the list, but 'hides' relevant items under their parent until you expand the parent yourself.
|
|---|
| 275 | Shall I take the extra time to expand them before I list them
|
|---|
| 276 | LAST I/LAST 4
|
|---|
| 277 | SIG DATE
|
|---|
| 278 | Editing #
|
|---|
| 279 | No Printable Documents Remain in your List.
|
|---|
| 280 | Making an addendum for #
|
|---|
| 281 | Signers identified/edited
|
|---|
| 282 | IDENTIFY SIGNERS
|
|---|
| 283 | Do you Wish to Identify Additional Signers
|
|---|
| 284 | This Document Already has Additional Expected Signers.
|
|---|
| 285 | Do You Wish to Identify More Additional Signers
|
|---|
| 286 | Added as expected signer...
|
|---|
| 287 | You may change the expected cosigner, if you wish...
|
|---|
| 288 | Response Required.
|
|---|
| 289 | Specify other practitioners whose signatures will be expected:
|
|---|
| 290 | Encounter Data Edited
|
|---|
| 291 | Reviewing #
|
|---|
| 292 | Reviewing Item #
|
|---|
| 293 | You are completing the PARENT ENTRY of this interdisciplinary note.
|
|---|
| 294 | Refreshing the list.
|
|---|
| 295 | Removed from print list.
|
|---|
| 296 | Amending #
|
|---|
| 297 | Only SIGNED Documents may be amended.
|
|---|
| 298 | Before proceeding, please enter your Electronic Signature Code...
|
|---|
| 299 | Ok, no harm done...
|
|---|
| 300 | The ORIGINAL document will be RETRACTED, and a copy will be amended...
|
|---|
| 301 | Retraction of Original Document Failed.
|
|---|
| 302 | sent back
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
