| 1 | English French Notes Complete/Exclude
|
|---|
| 2 | Error in Process
|
|---|
| 3 | Request Sent
|
|---|
| 4 | Awaiting Response
|
|---|
| 5 | - No patient data query exists for this patient.
|
|---|
| 6 | No Data Returned Due To:
|
|---|
| 7 | There were no exceptions found.
|
|---|
| 8 | Enter an exception type to view:
|
|---|
| 9 | Not a valid selection.
|
|---|
| 10 | exceptions that need processing.
|
|---|
| 11 | The following exception types are handled by this option:
|
|---|
| 12 | Required field(s) Date of Birth or Name missing
|
|---|
| 13 | SSN Match Failed
|
|---|
| 14 | Name Doesn't Match
|
|---|
| 15 | Death Entry on MPI not in VISTA
|
|---|
| 16 | Death Entry on Vista not in MPI
|
|---|
| 17 | Death Entries on MPI and Vista DO NOT MATCH
|
|---|
| 18 | Potential Matches Returned
|
|---|
| 19 | no exceptions found
|
|---|
| 20 | MISSING MSH SEGMENT
|
|---|
| 21 | ICN:
|
|---|
| 22 | From Station:
|
|---|
| 23 | APPLICATION ACKNOWLEDGMENT TO MSGID:
|
|---|
| 24 | MISSING PARAMETER
|
|---|
| 25 | RG FACILITY INTEGRATION SERVER
|
|---|
| 26 | ERROR ENCOUNTERED BY HL7 WHILE SENDING FACILITY INTEGRATION MESSAGE:
|
|---|
| 27 | MISSING PARAMETER NEEDED TO BUILD FACILITY INTEGRATION MESSAGE
|
|---|
| 28 | UNABLE TO SEND FACILITY INTEGRATION MESSAGE - PATIENT LACKS ICN
|
|---|
| 29 | SITE NOT FOUND IN INSTITUTION FILE
|
|---|
| 30 | Facility Integration Message not sent to station #
|
|---|
| 31 | RG FACILITY INTEGRATION CLIENT^
|
|---|
| 32 | LEGACY STATION NUMBER NOT FOUND UNIQUELY IN THE INSTITUTION FILE!
|
|---|
| 33 | PRIMARY STATION NUMBER NOT FOUND UNIQUELY IN THE INSTITUTION FILE!
|
|---|
| 34 | RG FACILITY INTEGRATION CLEANUP
|
|---|
| 35 | Looking for patients with legacy site as CMOR ...
|
|---|
| 36 | Looking for patients with legacy site as treating facility ...
|
|---|
| 37 | Returned mail message number:
|
|---|
| 38 | HL7 Message sent:
|
|---|
| 39 | *** HL7 Message NOT sent! :
|
|---|
| 40 | Patient DFN:
|
|---|
| 41 | Patient ICN:
|
|---|
| 42 | Treating Facilities:
|
|---|
| 43 | Process patient
|
|---|
| 44 | ** Patients with Legacy Site as CMOR **
|
|---|
| 45 | ** Patients with Legacy Site as Treating Facility **
|
|---|
| 46 | ** END OF MPI/NDBI SITE CLEANUP REPORT **
|
|---|
| 47 | MPI/NDBI SITE CLEANUP REPORT FROM
|
|---|
| 48 | Primary Station:
|
|---|
| 49 | Legacy Station:
|
|---|
| 50 | Count of Patients Found with Legacy Site as CMOR:
|
|---|
| 51 | MPI/PD at
|
|---|
| 52 | G.MPIF EXCEPTIONS
|
|---|
| 53 | MPI/NDBI SITE CLEANUP
|
|---|
| 54 | INPUT PARAMETER MISSING, TAG=XCHANGE,RTN=RGFIPM
|
|---|
| 55 | INSTITUTION LOOKUP FAILED, STATION# =
|
|---|
| 56 | ERROR CHANGING CMOR TO
|
|---|
| 57 | FAILURE TO DELETE TREATING FACILITY =
|
|---|
| 58 | FAILURE TO ADD SUBSCRIPTION FOR STATION# =
|
|---|
| 59 | FACILITY INTEGRATION ERROR:
|
|---|
| 60 | STATION#
|
|---|
| 61 | PATIENT LOOKUP BASED ON ICN FAILED
|
|---|
| 62 | LOCAL DATABASE HAS INCORRECT ICN CHECKSUM
|
|---|
| 63 | SENT INCORRECT ICN CHECKSUM
|
|---|
| 64 | ERROR ENCOUNTERED WHILE PROCESSING FACILITY INTEGRATION MESSAGE
|
|---|
| 65 | SITE INTEGRATION MSG TO CMOR NOT FROM LEGACY SITE
|
|---|
| 66 | SITE INTEGRATION MSG NOT FROM CMOR, CMOR IS
|
|---|
| 67 | MISSING STATION NUMBER IN MSH SEGMENT FOR SENDING SITE
|
|---|
| 68 | EVENT REASON CODE NOT 51
|
|---|
| 69 | MISSING ICN IN PID SEGMENT
|
|---|
| 70 | MISSING LEGACY STATION # IN NTE SEGMENT
|
|---|
| 71 | MISSING PRIMARY STATION # IN NTE SEGMENT
|
|---|
| 72 | From Station:
|
|---|
| 73 | MISSING SEGMENT:
|
|---|
| 74 | ERROR ENCOUNTERED WHILE PROCESSING FACITLIY INTEGRATION MESSAGE: MISSING CMOR
|
|---|
| 75 | Facility Integration Message not sent to MPI, no MPI link identified in CIRN SITE PARAMETER file (#991.8)
|
|---|
| 76 | Facility Integration Message not sent to primary site, station #
|
|---|
| 77 | RG FACILITY INTEGRATION CLIENT
|
|---|
| 78 | HL7 Message Exception Report
|
|---|
| 79 | MPI/PD Exception:
|
|---|
| 80 | MPI/PD exception notification
|
|---|
| 81 | RGMSH(773,
|
|---|
| 82 | RG MPI SERVER EXCEPTION
|
|---|
| 83 | **MPI/PD EXCEPTION**
|
|---|
| 84 | EXCEPTION TYPE
|
|---|
| 85 | OPTIONAL TEXT
|
|---|
| 86 | SITE OF OCCURRENCE
|
|---|
| 87 | SITE REPORTING
|
|---|
| 88 | DATE/TIME REPORTED
|
|---|
| 89 | **PATIENT DATA**
|
|---|
| 90 | TREATING FACILITY
|
|---|
| 91 | DATE LAST TREATED
|
|---|
| 92 | EVENT REASON
|
|---|
| 93 | S.MPI EXCEPTION SERVER@
|
|---|
| 94 | MPI/PD EXCEPTION
|
|---|
| 95 | MESSAGE ID
|
|---|
| 96 | EVENT TYPE
|
|---|
| 97 | LOGICAL LINK
|
|---|
| 98 | -1^INVALID ICN CHECKSUM
|
|---|
| 99 | RGSEG(RGPC)
|
|---|
| 100 | RGSEG(RGPC,RGPC1)
|
|---|
| 101 | RGSEG(RGPC,RGPC1,RGPC2)
|
|---|
| 102 | SCN_REQ
|
|---|
| 103 | Bad DFN,
|
|---|
| 104 | See the Exception Handling document on the MPI/PD web site.
|
|---|
| 105 | Mismatched SSN,
|
|---|
| 106 | Bad CMOR
|
|---|
| 107 | for DFN#
|
|---|
| 108 | Mismatched CMOR,
|
|---|
| 109 | Does not exist in patient database.
|
|---|
| 110 | Unable to send Subscription Request from
|
|---|
| 111 | . This is not a MPI/PD site.
|
|---|
| 112 | Unable to send Subscription Request to
|
|---|
| 113 | REQUIRED PARAMETERS MISSING IN STUB
|
|---|
| 114 | RG PT SUBSCRIPTION REQUEST
|
|---|
| 115 | RG PT SUBSCRIPTION RECEIVER^
|
|---|
| 116 | SUBSCRIPTION REGISTRY
|
|---|
| 117 | Unable to send Subscription. Duplicate station number of
|
|---|
| 118 | in Institution file.
|
|---|
| 119 | Unable to send Subscription from
|
|---|
| 120 | . This is not a MPI/PD Site.
|
|---|
| 121 | Unable to send Subscription to
|
|---|
| 122 | Unable to send Subscription Request from,
|
|---|
| 123 | Unable to send Subscription Request to,
|
|---|
| 124 | Identify this account as 'Production' or 'Test'.
|
|---|
| 125 | This installation is taking place in which account?
|
|---|
| 126 | Enter 'P' for Production or 'T' for Test
|
|---|
| 127 | HL*1.6*39
|
|---|
| 128 | You must have patch HL*1.6*39 installed.
|
|---|
| 129 | Environment check is ok.
|
|---|
| 130 | Enter 'P' if this installation is taking place in your
|
|---|
| 131 | PRODUCTION account. This will require patch HL*1.6*39.
|
|---|
| 132 | Enter 'T' if this installation is taking place in your
|
|---|
| 133 | TEST account. HL*1.6*39 should NOT be installed in any
|
|---|
| 134 | test account.
|
|---|
| 135 | This option prints information from the AUDIT file (#1.1) for a
|
|---|
| 136 | selected patient and date range.
|
|---|
| 137 | For the PATIENT file (#2) entry selected, the report prints the
|
|---|
| 138 | patient name and DFN, date/time the field was edited, the user who
|
|---|
| 139 | made the change, the field edited, the old value, and the new value.
|
|---|
| 140 | The option or protocol (if available) will also be displayed.
|
|---|
| 141 | This patient has no audit data available for any date.
|
|---|
| 142 | Enter date range for data to be included in report.
|
|---|
| 143 | Beginning Date:
|
|---|
| 144 | MPI/PD - Print AUDIT File Data for a Specific Patient
|
|---|
| 145 | No audit data found in this date range for this patient.
|
|---|
| 146 | PATIENT AUDIT LIST at
|
|---|
| 147 | Date/Time Edited
|
|---|
| 148 | Field Edited
|
|---|
| 149 | Edited By
|
|---|
| 150 | Old Value / New Value
|
|---|
| 151 | Option/Protocol
|
|---|
| 152 | This option prints a customized report of information stored in the AUDIT
|
|---|
| 153 | file (#1.1) for fields being audited in the PATIENT file (#2). For a
|
|---|
| 154 | specified date range, you can view all audited fields or selected fields.
|
|---|
| 155 | You can also opt to print only edits that were done by a specific user.
|
|---|
| 156 | - If selected fields are viewed, you can choose to see data for all or
|
|---|
| 157 | selected patients.
|
|---|
| 158 | - If ALL audited fields are viewed, you must choose patients to examine.
|
|---|
| 159 | No fields are currently being audited in the PATIENT file (#2).
|
|---|
| 160 | Do you want to see (A)LL or (S)ELECTED audited fields?
|
|---|
| 161 | to see ALL audited fields in the PATIENT file (#2).
|
|---|
| 162 | to select specific audited fields.
|
|---|
| 163 | Select FIELD NUMBER of audited field (enter
|
|---|
| 164 | for list):
|
|---|
| 165 | Do you want to see audited data for (A)LL or (S)ELECTED patients?
|
|---|
| 166 | to see audited fields for ALL patients.
|
|---|
| 167 | to select specific patients(s).
|
|---|
| 168 | Do you want to find only the edits made by a specific user
|
|---|
| 169 | Because you selected ALL patients, you MUST queue this report.
|
|---|
| 170 | FLD(
|
|---|
| 171 | MPI/PD - Print AUDIT File Data from the PATIENT file
|
|---|
| 172 | CUR DFN
|
|---|
| 173 | NO AUDIT
|
|---|
| 174 | has no audit data available for any date.
|
|---|
| 175 | has no audit data available for selected parameters.
|
|---|
| 176 | Select a FIELD NUMBER from the audited field(s) in the PATIENT file:
|
|---|
| 177 | Duplicate Record File Statistics Scan
|
|---|
| 178 | Your user identification is not set. Please D ^XUP and try again.
|
|---|
| 179 | Duplicate Record Statistics Search
|
|---|
| 180 | queued to run.
|
|---|
| 181 | DUPLICATE RECORD CHECK
|
|---|
| 182 | CURR IEN
|
|---|
| 183 | Duplicate Record (^DPT) Statistics
|
|---|
| 184 | Counts by: Merge Status and Match Percentile:
|
|---|
| 185 | NOT READY
|
|---|
| 186 | Merge Status:
|
|---|
| 187 | Counts by: Verification Status and Match Percentile:
|
|---|
| 188 | POTENTIAL DUP., UNVERIF
|
|---|
| 189 | VERIFIED, NOT A DUPLICATE
|
|---|
| 190 | VERIFIED DUPLICATE
|
|---|
| 191 | VERIF. IN PROGRESS
|
|---|
| 192 | REQUIRES RESOLUTION
|
|---|
| 193 | Verification Status:
|
|---|
| 194 | Duplicate Record Counts:
|
|---|
| 195 | The option, Start/Restart CMOR Score Calculation
|
|---|
| 196 | [RG CMOR START], needs to be run before this option.
|
|---|
| 197 | DUP. RECORD REPORT BY CMOR SCORE
|
|---|
| 198 | NO SCORE
|
|---|
| 199 | TOTAL Potential Duplicates (15):
|
|---|
| 200 | TOTAL Patients (2):
|
|---|
| 201 | TOTAL Potential Duplicates (15)
|
|---|
| 202 | TOTAL Patients (2)
|
|---|
| 203 | Duplicate Record Count by CMOR Score
|
|---|
| 204 | This report is drawn from the Duplicate Record file (#15) with
|
|---|
| 205 | CMOR scores from the PATIENT file, CMOR ACTIVITY SCORE field.
|
|---|
| 206 | - If both members of a pair have a score of zero the pair is
|
|---|
| 207 | counted in the '0' group.
|
|---|
| 208 | - If one or both members of the pair have a score greater than
|
|---|
| 209 | zero, that pair is counted in the group for the higher score.
|
|---|
| 210 | - If neither member of the pair have a CMOR score, the pair is
|
|---|
| 211 | counted in the 'NO SCORE' group.
|
|---|
| 212 | Score Range
|
|---|
| 213 | Duplicate Records by CMOR Score:
|
|---|
| 214 | Exception Totals for
|
|---|
| 215 | TOTAL EXCEPTIONS:
|
|---|
| 216 | At this point it is necessary for you to increase the right margin.
|
|---|
| 217 | At the DEVICE prompt enter=> ;255
|
|---|
| 218 | DOWNLOAD ABORTED!
|
|---|
| 219 | Data string=Site;Run Date;Date CIRN Installed;Exceptions 200-229
|
|---|
| 220 | Data string:
|
|---|
| 221 | Site;Sta#;;;LocICNs,209,213,214,215,216,217,218,219,223,225,226,227,229
|
|---|
| 222 | ...purging duplicate Potential Match Exceptions
|
|---|
| 223 | VAFC HFS SCRATCH
|
|---|
| 224 | RGMT_
|
|---|
| 225 | Subscribers:
|
|---|
| 226 | ICN History:
|
|---|
| 227 | CMOR History:
|
|---|
| 228 | CMOR Change Request History:
|
|---|
| 229 | and deleted
|
|---|
| 230 | Site;Sta#;
|
|---|
| 231 | This utility searches the HL7 MESSAGE TEXT (#772) file for a selected
|
|---|
| 232 | date range. Each HL7 message in the date range is examined. If the
|
|---|
| 233 | RELATED EVENT PROTOCOL field contains the MPI/PD protocols (e.g.,
|
|---|
| 234 | ) data is compiled into the ^XTMP(
|
|---|
| 235 | A cross-reference is built on patient ICN and DFN for faster data retrieval
|
|---|
| 236 | for the associated reports.
|
|---|
| 237 | The Compile MPI/PD HL7 Data compilation is already running!
|
|---|
| 238 | Compile MPI/PD HL7 Data
|
|---|
| 239 | last ran to completion on
|
|---|
| 240 | => Data has been compiled for
|
|---|
| 241 | (D)elete existing data and recompile.
|
|---|
| 242 | (A)ppend new data after last date of existing data
|
|---|
| 243 | D if you want to delete exiting data and recompile.
|
|---|
| 244 | A or <RET> to append new data after last date of existing data.
|
|---|
| 245 | to HALT.
|
|---|
| 246 | Enter date range for data to be compiled.
|
|---|
| 247 | Beginning Date for Report:
|
|---|
| 248 | Beginning Date for Report:
|
|---|
| 249 | Ending Date for Report:
|
|---|
| 250 | Compile MPI/PD HL7 Data (bi-directional)
|
|---|
| 251 | FORCE STOP
|
|---|
| 252 | NOW PROCESSING DATE
|
|---|
| 253 | (Look at ^HL(772,
|
|---|
| 254 | Stop HL7 Message Compile.
|
|---|
| 255 | << No compile is currently running >>
|
|---|
| 256 | A compile is currently running for
|
|---|
| 257 | Do you want to stop this compile
|
|---|
| 258 | Show status of HL7 Message Compile.
|
|---|
| 259 | Compile range
|
|---|
| 260 | The compile was started
|
|---|
| 261 | The compile is now processing
|
|---|
| 262 | The compile was stopped
|
|---|
| 263 | The option
|
|---|
| 264 | must have
|
|---|
| 265 | run to completion before this report can be printed!
|
|---|
| 266 | is currently running.
|
|---|
| 267 | This report cannot be generated until the compile has run to completion.
|
|---|
| 268 | Data has been compiled for
|
|---|
| 269 | option if this range is not sufficient.
|
|---|
| 270 | This option allows you to search for activity related to a specific protocol in
|
|---|
| 271 | the HL7 MESSAGE TEXT (#772) file for a patient during a selected period of time.
|
|---|
| 272 | This search is accomplished using data set into a temporary global built by the
|
|---|
| 273 | Select TYPE
|
|---|
| 274 | Patient lookup can be done by (P)atient Name/SSN or by (I)CN.
|
|---|
| 275 | Select LOOKUP
|
|---|
| 276 | The right margin for this print is 80.
|
|---|
| 277 | MPI/PD - Print HL7 Message Data for Patient/Single Protocol
|
|---|
| 278 | No data found for this patient.
|
|---|
| 279 | HL7 TRANSMISSION DATA at
|
|---|
| 280 | File #772 IEN
|
|---|
| 281 | Batch Msg #
|
|---|
| 282 | This patient does not have an ICN!
|
|---|
| 283 | Select ICN
|
|---|
| 284 | No patient match can be found for this ICN!
|
|---|
| 285 | This option allows you to search for ALL activity in the HL7 MESSAGE TEXT
|
|---|
| 286 | (#772) file for a specific patient during a selected period of time. This
|
|---|
| 287 | search is accomplished using data set into a temporary global built by the
|
|---|
| 288 | HL7 TRANSMISSION PATIENT DATA at
|
|---|
| 289 | Related Event Protocol
|
|---|
| 290 | No patient DFN match can be found for this ICN!
|
|---|
| 291 | This patient has no HL7 messaging activity in the current compiled data set.
|
|---|
| 292 | Select TYPE of Report - (D)etailed or (S)ummary:
|
|---|
| 293 | This option allows you to print information found during the
|
|---|
| 294 | Compile MPI/PD
|
|---|
| 295 | HL7 Data
|
|---|
| 296 | compilation. The report is sorted by RELATED EVENT PROTOCOL, date,
|
|---|
| 297 | transmission type, and status. The total number of messages for each date,
|
|---|
| 298 | transmission type, and status are displayed.
|
|---|
| 299 | MPI/PD - Print HL7 Message Status (SUMMARY)
|
|---|
| 300 | MPI/PD HL7 MESSAGE STATUS REPORT - SUMMARY (
|
|---|
| 301 | RELATED EVENT PROTOCOL
|
|---|
| 302 | transmission type, and status. Detailed information for each HL7 message is
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
