| 1 | English French Notes Complete/Exclude
|
|---|
| 2 | HL7 Msg#
|
|---|
| 3 | contained an invalid STATION#
|
|---|
| 4 | for ICN#
|
|---|
| 5 | Unable to change CMOR in HL7 Msg#
|
|---|
| 6 | due to
|
|---|
| 7 | Error returned in GENERATE^HLMA
|
|---|
| 8 | ) array for this patient
|
|---|
| 9 | -1^Unknown Logical Link for Station #
|
|---|
| 10 | Unable to notify of Change of CMOR for patient
|
|---|
| 11 | No MPI Link defined
|
|---|
| 12 | Msg#
|
|---|
| 13 | Unable to add/update SC for facility IEN
|
|---|
| 14 | , for patient
|
|---|
| 15 | Missing new CMOR or Patient to be changed
|
|---|
| 16 | for change CMOR request HL7 msg
|
|---|
| 17 | Missing CMOR site number in Change CMOR message for ICN
|
|---|
| 18 | Missing Patient ICN in Change CMOR message HL7 msg#
|
|---|
| 19 | ICN
|
|---|
| 20 | not found from Change CMOR message HL7 msg#
|
|---|
| 21 | CMOR Site name is not on file for Station Number
|
|---|
| 22 | processing Change CMOR msg for ICN
|
|---|
| 23 | Unable to update CMOR for site
|
|---|
| 24 | . For DFN
|
|---|
| 25 | Processing CHANGE CMOR message
|
|---|
| 26 | Received CMOR Change Request for ICN
|
|---|
| 27 | ICN not Found. Request #
|
|---|
| 28 | MPI VISTA Package
|
|---|
| 29 | MPIF(1,
|
|---|
| 30 | New Coordinating Master Of Record (CMOR) request received for patient
|
|---|
| 31 | no mail group defined for CMOR requests
|
|---|
| 32 | CMOR Change Request #
|
|---|
| 33 | CMOR not sent in Change CMOR message for patient DFN=
|
|---|
| 34 | Unable to Change CMOR to
|
|---|
| 35 | in a CMOR Change Message for Patient DFN=
|
|---|
| 36 | Auto change - CMOR pushed here
|
|---|
| 37 | MPIF RESOLUTION
|
|---|
| 38 | CMOR Request #
|
|---|
| 39 | Does Not Exist attempting to generate approved/not approved msg
|
|---|
| 40 | MPIF CMOR APPROVE/DISAPPROVE
|
|---|
| 41 | for Approved/Not Approved msg HL Error
|
|---|
| 42 | -1^LINK FOR MPI NOT FOUND
|
|---|
| 43 | MPIF CMOR APP/DIS^
|
|---|
| 44 | Error Generating HL7 msg for Approve/Not Approved CMOR Request #
|
|---|
| 45 | Does Not Exist CMORs may be out of sync for ICN
|
|---|
| 46 | received CMOR request for
|
|---|
| 47 | Processed by:
|
|---|
| 48 | Select CMOR request to review:
|
|---|
| 49 | *** Request is not pending review ***
|
|---|
| 50 | **** There are other PENDING Requests for this patient. If you approve one the rest will automatically be disapproved. ***
|
|---|
| 51 | Select Review Action (
|
|---|
| 52 | APPROVE/
|
|---|
| 53 | DISAPPROVE, OR '^' to Exit)?
|
|---|
| 54 | ... No Action!
|
|---|
| 55 | Unable to change CMOR for Change CMOR Request for patient DFN=
|
|---|
| 56 | Problem Changing CMOR, resetting status to pending approval. May be duplicates in Institution file for new CMOR or Patient file entry was already being edited.
|
|---|
| 57 | Problem during Broadcast -
|
|---|
| 58 | Have others to Disapprove -- automatically
|
|---|
| 59 | *** No request to approve ***
|
|---|
| 60 | Do you want to approve by SITE
|
|---|
| 61 | *** No requests to approve for this site ***
|
|---|
| 62 | Remote Procedure from MPI^RPC from MPI for ICN Information
|
|---|
| 63 | No current ICN
|
|---|
| 64 | No Current ICN
|
|---|
| 65 | NATIONAL ICN
|
|---|
| 66 | ICN HISTORY
|
|---|
| 67 | CMOR HISTORY
|
|---|
| 68 | No Exceptions
|
|---|
| 69 | NO EXCEPTIONS
|
|---|
| 70 | with No Exceptions
|
|---|
| 71 | with Exceptions
|
|---|
| 72 | ICNS PROCESSED
|
|---|
| 73 | -1^No ICN Passed
|
|---|
| 74 | -1^Invalid ICN
|
|---|
| 75 | -1^ICN is not active
|
|---|
| 76 | -1^Missing Required fields
|
|---|
| 77 | -1^Unknown ICN
|
|---|
| 78 | -1^Unknown Institution
|
|---|
| 79 | -1^No SSN or DFN Passed
|
|---|
| 80 | -1^Invalid SSN
|
|---|
| 81 | SSN USED
|
|---|
| 82 | -1^No such DFN
|
|---|
| 83 | DFN USED
|
|---|
| 84 | already has an ICN, ICN=
|
|---|
| 85 | DFN
|
|---|
| 86 | Patient should not be sent to the MPI -- SSN has 5 leading 0s or name has been ZZ'd
|
|---|
| 87 | problem getting ICN assinged
|
|---|
| 88 | -1^Unable to get ICN
|
|---|
| 89 | Local ICN assigned
|
|---|
| 90 | -1^Local ICN assigned
|
|---|
| 91 | -1^Missing required parameter
|
|---|
| 92 | -1^No patient has that SSN at this site
|
|---|
| 93 | -1^More than one patient has that SSN at this site
|
|---|
| 94 | -1^Patient has a national ICN, ICN=
|
|---|
| 95 | -1^Problem building A24 (ADD TF) for Pt
|
|---|
| 96 | -1^Did not pass valid DFN
|
|---|
| 97 | If DOB is inexact or if SSN is not passed or if common name,
|
|---|
| 98 | this could take some time - please be patient....
|
|---|
| 99 | Could not connect to MPI or Time-out occured, try again later.
|
|---|
| 100 | Patient was not found in the MPI.
|
|---|
| 101 | Found potential matches
|
|---|
| 102 | Found One Match
|
|---|
| 103 | Continue to next Patient?
|
|---|
| 104 | <<THIS ICN IS ACTIVELY BEING WORKED ON - CASE #
|
|---|
| 105 | Case Worker:
|
|---|
| 106 | ICN :
|
|---|
| 107 | Name :
|
|---|
| 108 | SSN :
|
|---|
| 109 | DOB :
|
|---|
| 110 | Multiple Birth Indicator: Yes
|
|---|
| 111 | Sex :
|
|---|
| 112 | Claim # :
|
|---|
| 113 | Place of Birth:
|
|---|
| 114 | Mother's Maiden Name:
|
|---|
| 115 | POW Status:
|
|---|
| 116 | Is Patient in the PATIENT file
|
|---|
| 117 | DOB is missing - Required field
|
|---|
| 118 | Patient not found. Try Again
|
|---|
| 119 | PATIENT NAME (last,first middle)
|
|---|
| 120 | Name should be Last,first middle and at least 3 characters and no more than 30
|
|---|
| 121 | 9 Digit SSN (No Dashes)
|
|---|
| 122 | SSN should be 9 numbers
|
|---|
| 123 | MPIF_SEEDING
|
|---|
| 124 | A31 SEEDING FOR SITE
|
|---|
| 125 | CNT=
|
|---|
| 126 | SEEDING COMPLETED
|
|---|
| 127 | Seeding has been completed at site
|
|---|
| 128 | Round of seeding has been completed at site
|
|---|
| 129 | Site stats for seeding (total to date):
|
|---|
| 130 | AICN x-refs Processed:
|
|---|
| 131 | MPIF VISTA PACKAGE
|
|---|
| 132 | Seeding msg
|
|---|
| 133 | G.CIRN DEV@FORUM.VA.GOV
|
|---|
| 134 | MPIF SEEDING TASK
|
|---|
| 135 | MPIF SEEDING TASK doesn't exist in OPTION file
|
|---|
| 136 | MPIF SEEDING TASK isn't scheduled to run
|
|---|
| 137 | MPIF SEEDING TASK is scheduled to run at
|
|---|
| 138 | I WILL PAD TO 16!
|
|---|
| 139 | -1^No Mailgroup defined
|
|---|
| 140 | *** Patient not defined for this request ***
|
|---|
| 141 | *** Patient has not been assigned a CMOR Site ***
|
|---|
| 142 | *** Patient already has an open request (
|
|---|
| 143 | *** You must enter a site to send this request to ***
|
|---|
| 144 | *** You cannot send a request to your own site ***
|
|---|
| 145 | *** You cannot send a request to a site that isn't a treating facility for this patient ***
|
|---|
| 146 | -1^No Requests on File
|
|---|
| 147 | ) to change CMOR to
|
|---|
| 148 | -1^no encoding characters
|
|---|
| 149 | -1^invalid DFN
|
|---|
| 150 | -1^Patient merged
|
|---|
| 151 | -1^Patient being merged DFN=
|
|---|
| 152 | -1^ICN already assigned
|
|---|
| 153 | -1^5 zero SSN
|
|---|
| 154 | -1^EEE Patient
|
|---|
| 155 | -1^Missing Required Field(s)
|
|---|
| 156 | is Missing Required Field(s)
|
|---|
| 157 | *** Warning: this may be a missing patient, a message is being ***
|
|---|
| 158 | *** sent to notify the MPR Coordinators. Be prepared to answer ***
|
|---|
| 159 | *** questions from the MPR Coordinator about this patient. ***
|
|---|
| 160 | Press return key to continue
|
|---|
| 161 | This patient was reported as missing from
|
|---|
| 162 | . The National Missing Patient Register has
|
|---|
| 163 | listed as:
|
|---|
| 164 | MISSING PATIENT INFORMATION:
|
|---|
| 165 | MISSING PATIENT:
|
|---|
| 166 | RECORD REFERENCED BY:
|
|---|
| 167 | ..PHONE NUMBER:
|
|---|
| 168 | ..OPTION EMPLOYED:
|
|---|
| 169 | is determined to be a missing patient use the MPR option
|
|---|
| 170 | 'Enter/Edit Found Patient' to update the Local and National MPR data base.
|
|---|
| 171 | G.MPR COORDINATORS
|
|---|
| 172 | MPR FOUND PATIENT BULLETIN
|
|---|
| 173 | MPR*
|
|---|
| 174 | MPR FOUND PATIENT
|
|---|
| 175 | Missing Patient Register
|
|---|
| 176 | Select a NATIONAL MISSING PATIENT:
|
|---|
| 177 | ) has never been a patient
|
|---|
| 178 | at this facility.
|
|---|
| 179 | DATE PATIENT FOUND
|
|---|
| 180 | Enter the date that the patient was found
|
|---|
| 181 | Please enter the patient's condition when found
|
|---|
| 182 | Please enter a narrative describing how the patient was found.
|
|---|
| 183 | You have not answered all the necessary information associated with this
|
|---|
| 184 | found patient.
|
|---|
| 185 | Do you want to finish editing now
|
|---|
| 186 | If you do not finish editing, no information will be updated.
|
|---|
| 187 | MPR Found Patient Background Filer.
|
|---|
| 188 | created to file and transmit data to the National
|
|---|
| 189 | Missing Patient Register database.
|
|---|
| 190 | MPRFMSG(
|
|---|
| 191 | MPR Found Patient Data
|
|---|
| 192 | has NOT been added to the Missing Patient Register.
|
|---|
| 193 | has been added to the Missing Patient Register.
|
|---|
| 194 | MPR Missing Patient Background Filer.
|
|---|
| 195 | NO TASK
|
|---|
| 196 | created to transmit data to
|
|---|
| 197 | National Missing Patient Register Database.
|
|---|
| 198 | Someone is currently editing that patient, please try later.
|
|---|
| 199 | Next of Kin can not be notified before the patient was reported missing.
|
|---|
| 200 | PLEASE CONFIRM, IS THE PATIENT OF LOW RISK:
|
|---|
| 201 | NOW-72H
|
|---|
| 202 | Date the patient was discovered missing:
|
|---|
| 203 | Enter the date that the patient was discovered missing.
|
|---|
| 204 | Patient must be missing for 72 hrs. before entry to Missing Patient Register.
|
|---|
| 205 | The date must be before
|
|---|
| 206 | MPREMTSK Created on
|
|---|
| 207 | MPR LOCAL DATA MESSAGE
|
|---|
| 208 | MPRMSG(
|
|---|
| 209 | Acknowledgment string
|
|---|
| 210 | Missing/Found field
|
|---|
| 211 | is missing for this entry.
|
|---|
| 212 | Entry is not a ACKnowledgment entry.
|
|---|
| 213 | The IEN in this ACKnowledgment message is not in the ^MPR(850) database.
|
|---|
| 214 | This ACKnowledgment message is not a Missing or Found entry.
|
|---|
| 215 | Status for entry
|
|---|
| 216 | in file 850 is not a 'T'.
|
|---|
| 217 | in file 850 is not a 'T' or 'A'.
|
|---|
| 218 | The MPR Acknowledgment server has encountered an error.
|
|---|
| 219 | Sender:
|
|---|
| 220 | Option Name: MPRSACK
|
|---|
| 221 | MPRSACK Server Error
|
|---|
| 222 | G.MPR MESSAGES@
|
|---|
| 223 | MPRERR(
|
|---|
| 224 | Message is not proper format for the Missing Patient Register Server.
|
|---|
| 225 | Message data is not in proper format for the Missing Patient Register Server.
|
|---|
| 226 | UNABLE TO STORE DATA. INVALID SSN.
|
|---|
| 227 | The MPR Data server has encountered an error.
|
|---|
| 228 | Option Name: MPRSDATA
|
|---|
| 229 | MPRSDATA Server Error
|
|---|
| 230 | <attribute name>
|
|---|
| 231 | <attribute value>
|
|---|
| 232 | Invoking XML Parser...
|
|---|
| 233 | Parser Summary:
|
|---|
| 234 | Elements
|
|---|
| 235 | Non-markup Content
|
|---|
| 236 | Processing Instructions
|
|---|
| 237 | External Entities
|
|---|
| 238 | Notation Declarations
|
|---|
| 239 | Warning^Validation Error^Conformance Error
|
|---|
| 240 | Line
|
|---|
| 241 | <?xml version=
|
|---|
| 242 | E3R Entry Number :
|
|---|
| 243 | Suspense Date:
|
|---|
| 244 | Priority :
|
|---|
| 245 | Functional Category:
|
|---|
| 246 | Status :
|
|---|
| 247 | Resolved Date:
|
|---|
| 248 | Submitted By :
|
|---|
| 249 | Submitted Date:
|
|---|
| 250 | Responsible Package:
|
|---|
| 251 | Message #:
|
|---|
| 252 | Impact:
|
|---|
| 253 | Recommendation:
|
|---|
| 254 | Arbitrator Comments:
|
|---|
| 255 | EP/ARG Comments:
|
|---|
| 256 | Package/Developer Comments:
|
|---|
| 257 | Final Resolution:
|
|---|
| 258 | SHORT DESCRIPTION
|
|---|
| 259 | Do you want to enter a new request
|
|---|
| 260 | You must enter a Description before you can transmit this
|
|---|
| 261 | E3R request to the Package/Developer.
|
|---|
| 262 | Do you want to re-edit this request now
|
|---|
| 263 | You currently have no E3R's under development for you to edit.
|
|---|
| 264 | You have no 'under development' E3R's to cancel or are not authorized to
|
|---|
| 265 | cancel E3R's assigned or under arbitration.
|
|---|
| 266 | NTSE ARBITRATOR
|
|---|
| 267 | Are you sure you want to cancel this E3R report
|
|---|
| 268 | Would you like to review the existing data for this E3R report
|
|---|
| 269 | Is this E3R ready to be transmitted to the package/developers for action
|
|---|
| 270 | You may select E3R
|
|---|
| 271 | to edit it later, or choose the cancel option
|
|---|
| 272 | to dispose of it.
|
|---|
| 273 | E3R requests may be selected by entering one of the following:
|
|---|
| 274 | 2. The beginning of the short description.
|
|---|
| 275 | 3. The namespace of the related package or the namespace, a hyphen and the
|
|---|
| 276 | version number (e.g., DENT or DENT-1.14).
|
|---|
| 277 | Select E3R ENTRY NUMBER:
|
|---|
| 278 | This entry is already being edited by someone. Try again later.
|
|---|
| 279 | Are you sure you want to refer this E3R to the arbitrator
|
|---|
| 280 | This E3R has been referred to the arbitrator (DBIC) for assignment
|
|---|
| 281 | to the appropriate responsible package.
|
|---|
| 282 | This report was assigned to your package by the arbitrator.
|
|---|
| 283 | You are not allowed to refer it back to the arbitrator.
|
|---|
| 284 | If you do not agree with this assignment, you may discuss it further with
|
|---|
| 285 | the arbitrator (DBIC).
|
|---|
| 286 | Is this E3R report considered assigned to the responsible package
|
|---|
| 287 | This option can only be used by EP members. You are not designated as an EP
|
|---|
| 288 | member for any of the packages in the package file.
|
|---|
| 289 | Is this E3R report now considered resolved
|
|---|
| 290 | The user representative or developer,
|
|---|
| 291 | has resolved the E3R request #
|
|---|
| 292 | Package/Developer comments:
|
|---|
| 293 | EP Comments:
|
|---|
| 294 | NTSE MASTER
|
|---|
| 295 | ELECTRONIC ERROR & ENHANCEMENT REPORT
|
|---|
| 296 | Package Prefix:
|
|---|
| 297 | under development
|
|---|
| 298 | under arbitration
|
|---|
| 299 | Resolved
|
|---|
| 300 | DELETE CONDITION
|
|---|
| 301 | ARBITRATOR COMMENTS
|
|---|
| 302 | PACKAGE/DEVELOPER COMMENTS
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
