| [604] | 1 | English French Notes Complete/Exclude
|
|---|
| 2 | 1) Setup active primary care team(s)
|
|---|
| 3 | 2) Setup active PC Practitioner position(s)
|
|---|
| 4 | 3) Setup any necessary preceptor/preceptee relationships
|
|---|
| 5 | 4) Assign practitioner to position(s)
|
|---|
| 6 | A patient can only have one PC team and one
|
|---|
| 7 | PC Position assignment on a given day. The patient must be
|
|---|
| 8 | assigned to a position's team to be assigned to the position.
|
|---|
| 9 | Note: You must the use the PCMM GUI if the patient was:
|
|---|
| 10 | o unassigned from PC assignment today or in the future
|
|---|
| 11 | o assigned to a future PC assignment.
|
|---|
| 12 | Checking PC Team and Position Status...
|
|---|
| 13 | No current PC Team/PC Practitioner Assignments
|
|---|
| 14 | Press enter to continue.
|
|---|
| 15 | This patient has future assignments for Primary Care
|
|---|
| 16 | Team and/or Practitioner
|
|---|
| 17 | You must use PCMM's Graphical User Interface to change
|
|---|
| 18 | This patient has NO active Primary Care Team, but does have
|
|---|
| 19 | an active PC Position Assignment
|
|---|
| 20 | No position defined
|
|---|
| 21 | About to Unassign
|
|---|
| 22 | Position Unassignment
|
|---|
| 23 | NOT made.
|
|---|
| 24 | is associated with the
|
|---|
| 25 | Patient has restricted consults due to team assignment(s):
|
|---|
| 26 | This patient may only be enrolled in clinics via
|
|---|
| 27 | Edit Clinic Enrollment Data option
|
|---|
| 28 | Do you wish to enroll the patient from this clinic on
|
|---|
| 29 | Clinic Enrollment
|
|---|
| 30 | NOT made
|
|---|
| 31 | is enrolled in the associated
|
|---|
| 32 | Do you wish to discharge the patient from this clinic on
|
|---|
| 33 | AND from
|
|---|
| 34 | PC assignment unassigned.
|
|---|
| 35 | Future/Current Patient-Position Assignment exists
|
|---|
| 36 | Team Unassignment
|
|---|
| 37 | Checking for other position assignments to team...
|
|---|
| 38 | Unassignment date already exists or unassignment after assignment date
|
|---|
| 39 | - Correct via PCMM GUI
|
|---|
| 40 | current/future position assignment(s)
|
|---|
| 41 | About to unassign the above patient-position assignments
|
|---|
| 42 | Problem with unassignment, correct via PCMM GUI
|
|---|
| 43 | About to Assign
|
|---|
| 44 | to a primary care team
|
|---|
| 45 | ********** This patient is 50 percent or greater service-connected ************
|
|---|
| 46 | This assignment will reach or exceeded the maximum set for this team.
|
|---|
| 47 | Maximum set for team:
|
|---|
| 48 | Team Assignment
|
|---|
| 49 | to PC Position Assignment
|
|---|
| 50 | POSITION's Current PRACTITIONER:
|
|---|
| 51 | POSITION's Name:
|
|---|
| 52 | Maximum set for position:
|
|---|
| 53 | Position Assignment
|
|---|
| 54 | Do you wish to continue with the assignment (Yes/No)?
|
|---|
| 55 | Are you sure (Yes/No)
|
|---|
| 56 | Choose way to select PC POSITION Assignment:
|
|---|
| 57 | Unassignment
|
|---|
| 58 | TODAY-1
|
|---|
| 59 | Service Connected %:
|
|---|
| 60 | Are you seeking Primary Care panel assignment
|
|---|
| 61 | for your service connected disability
|
|---|
| 62 | Do you wish to place the patient on the wait list (Yes/No)?
|
|---|
| 63 | Patient Placed on Wait List
|
|---|
| 64 | points to an INSTITUTION that is not NATIONAL.
|
|---|
| 65 | Team Selection
|
|---|
| 66 | Position Selection
|
|---|
| 67 | Positons:
|
|---|
| 68 | This report is formatted for standard letter size output
|
|---|
| 69 | Teams:
|
|---|
| 70 | Do you want a page break as the
|
|---|
| 71 | TEAM PROFILE REPORT
|
|---|
| 72 | SCTEAMS(
|
|---|
| 73 | NO POSITIONS
|
|---|
| 74 | NO STANDARD ROLE
|
|---|
| 75 | Team Name:
|
|---|
| 76 | Team Telephone:
|
|---|
| 77 | Provides Patients
|
|---|
| 78 | Standard Role
|
|---|
| 79 | Allowed
|
|---|
| 80 | Team Settings:
|
|---|
| 81 | Maximum Patients:
|
|---|
| 82 | This team can provide primary care.
|
|---|
| 83 | This is not a primary care team
|
|---|
| 84 | This team is closed to further patients.
|
|---|
| 85 | This team is still accepting patients.
|
|---|
| 86 | Team Description:
|
|---|
| 87 | No Information for the Team Profile report
|
|---|
| 88 | Primary Care Management Team Profile Report
|
|---|
| 89 | Patient-Team Assignment Message
|
|---|
| 90 | PATIENT-TEAM ASSIGNMENT for Patient (
|
|---|
| 91 | Current Patient Team Data:
|
|---|
| 92 | Previous Patient Team Data:
|
|---|
| 93 | Fields:
|
|---|
| 94 | Previous Data: Current Patient Data:
|
|---|
| 95 | Multiple PATIENT-TEAM ASSIGNMENT for
|
|---|
| 96 | Sending Multiple Patient-Team Assignment Message
|
|---|
| 97 | Team:
|
|---|
| 98 | Effective Date:
|
|---|
| 99 | There has been a new team assignment for the following patients:
|
|---|
| 100 | There has been NO new team assignment for the following patients:
|
|---|
| 101 | IF $D(^SCTM(404.57,
|
|---|
| 102 | Activation must be defined before Discharge
|
|---|
| 103 | Team Not Active
|
|---|
| 104 | Already an activation for patient/team on this date
|
|---|
| 105 | Existing active patient/team assignment already
|
|---|
| 106 | Activation must be before discharge
|
|---|
| 107 | Existing future activation before this inactivation
|
|---|
| 108 | SCMC ENCOUNTER CONVERSION EVENTS
|
|---|
| 109 | Patient-Position Assignment Message
|
|---|
| 110 | PATIENT-POSITION ASSIGNMENT for Patient (
|
|---|
| 111 | Previous Data: Current Patient Data:
|
|---|
| 112 | Multiple PATIENT-POSITION ASSIGNMENT for
|
|---|
| 113 | Sending Multiple Patient-Position Assignment Message
|
|---|
| 114 | Position:
|
|---|
| 115 | There has been a new position assignment for the following patients:
|
|---|
| 116 | There has been NO new position assignment for the following patients:
|
|---|
| 117 | Duplicate Criteria Not Allowed for Same Report
|
|---|
| 118 | Duplicate SORT BY TEXT Not Allowed for Same Report
|
|---|
| 119 | Duplicate Team Positions Not Allowed
|
|---|
| 120 | Bad input data
|
|---|
| 121 | Inactivation date is after this date
|
|---|
| 122 | Position Not active on this date
|
|---|
| 123 | No active Patient Team Assignment on this date
|
|---|
| 124 | No activation date in Pt Team Assignment
|
|---|
| 125 | Activation date is after this date
|
|---|
| 126 | Inactivation date must be when position is active
|
|---|
| 127 | Team Position Must be from Team in Pt Team Assignment
|
|---|
| 128 | Undefined Patient Team Data
|
|---|
| 129 | PC Roles only allowed if Pt Team Assignment is for Primary Care
|
|---|
| 130 | Position Assignment
|
|---|
| 131 | This task will send a MailMan message to you containing
|
|---|
| 132 | the results of the position assignment review.
|
|---|
| 133 | Patient Team Position Assignment Review
|
|---|
| 134 | SCTMLST(
|
|---|
| 135 | SCTP DANGLERS
|
|---|
| 136 | >>> Press RETURN to continue:
|
|---|
| 137 | In order to correct the following active positions with discharged team
|
|---|
| 138 | assignments, please refer to the documentation for the Patient Team
|
|---|
| 139 | Position Assignment Review option found in the Stand-alone Options
|
|---|
| 140 | Section of the PCMM User Guide.
|
|---|
| 141 | Diagnostic Only
|
|---|
| 142 | Fix
|
|---|
| 143 | Teams Reviewed:
|
|---|
| 144 | Patient Team Position Assignments Reviewed:
|
|---|
| 145 | Number of Assignments with Problems :
|
|---|
| 146 | Error: Position Assigned Date is BEFORE Team Assigned Date
|
|---|
| 147 | Position Assigned Date:
|
|---|
| 148 | Team Assigned Date:
|
|---|
| 149 | Error: Position Unassigned Date is AFTER Team Unassigned Date
|
|---|
| 150 | Team Unassigned Date:
|
|---|
| 151 | Position Unassigned Date:
|
|---|
| 152 | Deleting Traditional ASTAT CROSS REFERENCE from FILE 404.43
|
|---|
| 153 | SD*5.3*264
|
|---|
| 154 | Removing Patients with Date of Death from Team/Position Assignments
|
|---|
| 155 | Starting with Dates of Death in
|
|---|
| 156 | Setting up GUI to VistA mapping
|
|---|
| 157 | SD*5.3*278
|
|---|
| 158 | PCMM CLIENT LIST
|
|---|
| 159 | -1^not a valid server name
|
|---|
| 160 | -1^Server variable not defined.
|
|---|
| 161 | -1^This server is not in the PCMM SERVER PATCH file.
|
|---|
| 162 | -1^This server is not active.
|
|---|
| 163 | -1^No clients found for this Server.
|
|---|
| 164 | -1^Client variable not defined.
|
|---|
| 165 | -1^Client not defined in PCMM CLIENT PATCH file.
|
|---|
| 166 | PCMM ACTIVE SERVERS
|
|---|
| 167 | SC1(1)
|
|---|
| 168 | SC2(1)
|
|---|
| 169 | Wait list entry deleted
|
|---|
| 170 | 3;ON WAITLIST TEAM:
|
|---|
| 171 | RESIDENT (PHYSICIAN)
|
|---|
| 172 | SCPATIENT LIST
|
|---|
| 173 | SCTMP LIST
|
|---|
| 174 | SC*
|
|---|
| 175 | Multiple PATIENT-TEAM REASSIGNMENT FAILURES for
|
|---|
| 176 | Sending Multiple Patient-Team Reassignment Failures Message
|
|---|
| 177 | There has been NO new team reassignment for the following patients:
|
|---|
| 178 | PCMM Reassignment
|
|---|
| 179 | Multiple PATIENT-POSITION REASSIGNMENT FAILURES for
|
|---|
| 180 | Total Processed:
|
|---|
| 181 | From Team:
|
|---|
| 182 | From Position:
|
|---|
| 183 | There has been NO new position reassignment for the following patients:
|
|---|
| 184 | The following position reassignments did not complete processing:
|
|---|
| 185 | Updating of all clinics contained in the HOSPITAL LOCATION
|
|---|
| 186 | file (#44) to require provider and diagnosis for checkout
|
|---|
| 187 | completed on
|
|---|
| 188 | HOSPITAL LOCATION UPDATE COMPLETED
|
|---|
| 189 | >>> Setting parameters contained in SCHEDULING PARAMETER file (#404.91)
|
|---|
| 190 | *** Unable to create/find entry in Scheduling Parameter file
|
|---|
| 191 | *** Unable to store parameters relating to Ambulatory Care
|
|---|
| 192 | Parameters relating to Ambulatory Care have been stored
|
|---|
| 193 | >>> Attaching mail group to Ambulatory Care transmission summary bulletin
|
|---|
| 194 | ** MAS PARAMETER file (#43) does not have a value for
|
|---|
| 195 | the OPC GENERATE MAIL GROUP field (#216)
|
|---|
| 196 | ** Unable to attach mail group to the SCDX AMBCARE
|
|---|
| 197 | TO NPCDB SUMMARY bulletin
|
|---|
| 198 | ** Mail group must be added to bulletin manually
|
|---|
| 199 | ** Unable to find entry for SCDX AMBCARE TO NPCDB
|
|---|
| 200 | SUMMARY in BULLETIN file (#3.6)
|
|---|
| 201 | ** Bulletin must be manually entered
|
|---|
| 202 | Mail group contained in the OPC GENERATE MAIL GROUP
|
|---|
| 203 | field (#216) of the MAS PARAMETER file (#43) has
|
|---|
| 204 | been attached to the SCDX AMBCARE TO NPCDB SUMMARY bulletin
|
|---|
| 205 | >>> Installing correct version of routine SDM
|
|---|
| 206 | SD*5.3*41
|
|---|
| 207 | PCMM has NOT been installed. Will install a version
|
|---|
| 208 | of routine SDM that DOES NOT have the PCMM changes
|
|---|
| 209 | applied to it.
|
|---|
| 210 | MSM sites must copy the SDM routine to all appropriate UCIs
|
|---|
| 211 | ********** PLEASE NOTE THE FOLLOWING ***********
|
|---|
| 212 | * After installing PCMM, call the routine *
|
|---|
| 213 | * SCMSP at theline tag SDM (i.e. D SDM^SCMSP) *
|
|---|
| 214 | * in order to install a version of routine SDM *
|
|---|
| 215 | * with the ACRP & PCMM changes applied to it. *
|
|---|
| 216 | * MSM sites will then need to copy the updated *
|
|---|
| 217 | * SDM routine to all appropriate UCIs. *
|
|---|
| 218 | PCMM has been installed. Will install a version
|
|---|
| 219 | of routine SDM that has the PCMM changes applied
|
|---|
| 220 | to it
|
|---|
| 221 | >>> Creating entry for Z00 in HL7 EVENT TYPE CODE file (#779.001)
|
|---|
| 222 | 2///Ambulatory Care transmission to/from NPCDB
|
|---|
| 223 | Existing entry found - support of HL7 v2.2 will be added/verified
|
|---|
| 224 | Entry created - support of HL7 v2.2 will be added
|
|---|
| 225 | ** Unable to create entry for Z00
|
|---|
| 226 | Support for HL7 v2.2
|
|---|
| 227 | ** Unable to add support for HL7 v2.2
|
|---|
| 228 | ** Support for HL7 v2.2 must be added manually
|
|---|
| 229 | >>> Creating entries in HL APPLICATION file (#771)
|
|---|
| 230 | AMBCARE-DHCP
|
|---|
| 231 | ** Entries for AMBCARE-DHCP and NPCD-AAC in the HL
|
|---|
| 232 | APPLICATION file (#771) can not be created
|
|---|
| 233 | Creating entry for sending application (AMBCARE-DHCP)
|
|---|
| 234 | Entry for AMBCARE-DHCP successfully created
|
|---|
| 235 | Existing entry for AMBCARE-DHCP found - current values not overwritten
|
|---|
| 236 | ** Unable to create entry for AMBCARE-DHCP
|
|---|
| 237 | ** Sending application must be added manually
|
|---|
| 238 | NPCD-AAC
|
|---|
| 239 | Creating entry for receiving application (NPCD-AAC)
|
|---|
| 240 | Entry for NPCD-AAC successfully created
|
|---|
| 241 | Existing entry for NPCD-AAC found - current values not overwritten
|
|---|
| 242 | ** Unable to create entry for NPCD-AAC
|
|---|
| 243 | ** Receiving application must be added manually
|
|---|
| 244 | >>> Creating entry in MAIL GROUP file (#3.8)
|
|---|
| 245 | SCDX AMBCARE TO NPCDB
|
|---|
| 246 | Mail Group used by the Ambulatory Care Reporting Project to
|
|---|
| 247 | transmit data to the National Patient Care Database via HL7
|
|---|
| 248 | Entry for SCDX AMBCARE TO NPCDB successfully created
|
|---|
| 249 | ** Unable to create entry for SCDX AMBCARE TO NPCDB
|
|---|
| 250 | Adding National Patient Care Database (NPCDB) to Mail Group
|
|---|
| 251 | XXX@Q-ACS.MED.VA.GOV
|
|---|
| 252 | XXX@Q-ACS.MED.VA.GOV successfully added as REMOTE MEMBER
|
|---|
| 253 | ** Unable to add XXX@Q-ACS.MED.VA.GOV as REMOTE MEMBER
|
|---|
| 254 | ** Remote member must be added manually
|
|---|
| 255 | >>> Creating entry in HL LOWER LEVEL PROTOCOL PARAMETER file (#869.2)
|
|---|
| 256 | .02///MAILMAN;100.01///SCDX AMBCARE TO NPCDB
|
|---|
| 257 | Entry for AMB-CARE created
|
|---|
| 258 | Entry for AMB-CARE found
|
|---|
| 259 | Existing information will not be overwritten
|
|---|
| 260 | ** Unable to create entry for AMB-CARE
|
|---|
| 261 | >>> Creating entry in HL LOGICAL LINK file (#870)
|
|---|
| 262 | >>> Enabling Ambulatory Care event handler
|
|---|
| 263 | SCDX AMBCARE EVENT
|
|---|
| 264 | ** Unable to find SCDX AMBCARE EVENT in PROTOCOL file (#101)
|
|---|
| 265 | ** Entry must be manually created
|
|---|
| 266 | >>> Correcting entry in PROTOCOL file (#101) for server protocol
|
|---|
| 267 | ** Unable to find SCDX AMBCARE SEND SERVER FOR ADT-Z00
|
|---|
| 268 | in PROTOCOL file (#101)
|
|---|
| 269 | ** Unable to find AMBCARE-DHCP in HL7 APPLICATION file (#771)
|
|---|
| 270 | ** Entry must be manually created and attached to
|
|---|
| 271 | the SCDX AMBCARE SEND SERVER FOR ADT-Z00 protocol
|
|---|
| 272 | SCDX AMBCARE SEND CLIENT FOR ADT-Z00
|
|---|
| 273 | ** Unable to find SCDX AMBCARE SEND CLIENT FOR ADT-Z00
|
|---|
| 274 | ** Unable to find NPCD-AAC in HL7 APPLICATION file (#771)
|
|---|
| 275 | the SCDX AMBCARE SEND CLIENT FOR ADT-Z00 protocol
|
|---|
| 276 | ** Unable to find AMB-CARE in HL LOGICAL LINK file (#870)
|
|---|
| 277 | Background job to activate AMBCARE validation checker at
|
|---|
| 278 | Check-Out for all clinics will be queued for
|
|---|
| 279 | *** Unable to queue task ***
|
|---|
| 280 | Queued as task number
|
|---|
| 281 | Removing AMBCARE event handler from Scheduling event driver item list.
|
|---|
| 282 | Adding AMBCARE event handler to the exit action of SDAM APPOINTMENT EVENTS
|
|---|
| 283 | Re-indexing the four new cross references in the Transmitted Outpatient Encounter Error file.
|
|---|
| 284 | Re-indexing completed!
|
|---|
| 285 | file (#44) to run the AMBCARE validator at Check-Out was
|
|---|
| 286 | Removal of SCDX AMBCARE EVENT protocol from the Scheduling Event driver
|
|---|
| 287 | was not completed. Please review the installation instructions of this patch.
|
|---|
| 288 | was completed.
|
|---|
| 289 | The protocol 'SDAM APPOINTMENT EVENTS' could not be found.
|
|---|
| 290 | Please review the installation instructions for this patch.
|
|---|
| 291 | The AMBCARE event handler call exists in the Scheduling event driver exit action!
|
|---|
| 292 | SCMS(
|
|---|
| 293 | Updating of 'SDAM APPOINTMENT EVENTS' exit action complete!
|
|---|
| 294 | The exit action for 'SDAM APPOINTMENT EVENTS' on your system was:
|
|---|
| 295 | An attempt was made to replace it, but failed.
|
|---|
| 296 | It has been replaced with D EN^SCDXHLDR
|
|---|
| 297 | You will need to edit this protocol's exit action to restore your changes.
|
|---|
| 298 | Checking for installation of PCE version 1.0 ...
|
|---|
| 299 | Installation of Ambulatory Care requires that PCE version
|
|---|
| 300 | 1.0 be installed - you have version
|
|---|
| 301 | XU*8.0*27
|
|---|
| 302 | XU*8.0*27 be installed. Install will be aborted at end of
|
|---|
| 303 | #################### #################### ####################
|
|---|
| 304 | #################### #################### ####################
|
|---|
| 305 | #################### #################### ####################
|
|---|
| 306 | #################### #################### ####################
|
|---|
| 307 | #################### #################### ####################
|
|---|
