============================================================================= Run Date: DEC 20, 2017 Designation: WEBP*1*15 Package : WEBP - PATIENT CENTERED MANAGEMENT Priority: Mandatory Version : 1 SEQ #15 Status: Released Compliance Date: JAN 19, 2018 ============================================================================= Subject: PCMM WEB V1.15 CONFIGURATION UPDATES Category: - Informational Description: ============ The Patient-Centered Management Module (PCMM) Web application version WEBP*1*15 will implement the following configuration changes to current functionality that will reduce errors received by users and allow the system to function more efficiently. Configuration and Software Changes: =================================== 1. RTC 456006 - The Primary Care - Home Based Primary Care (PC-HBPC) care type needs to add the Primary Care Provider (PCP) team role to the Centralized Patient Record System (CPRS) window display when a patient is explicitly assigned to the Associate Provider (AP) team role. The Java code for "patient summary builder" was updated to add non-persistent PCP assignment to display in CPRS window even if the patient is not explicitly assigned to the PCP team role but to the AP team role. CA-SDM Ticket: No associated helpdesk tickets for this issue. 2. RTC 455951 - The Nurse Practitioner Associate Provider (NPAP) and the Physician Assistant Associate Provider (PAAP) team roles were displaying in the team Position List out of order. The PCMM-Web database has been updated so that the sort order in table pcmm.pcm_std_team_care_type_team_role table is now the requested sort order. CA-SDM Ticket: No associated helpdesk tickets for this issue. 3. RTC 455945 - The NPAP and PAAP team roles are not displaying in the correct order in the CPRS window. The sort has been corrected in PCMM-Web so that the team roles for NPAP and PAAP are displayed below the PCP team role if assigned to a patient. CA-SDM Ticket: No associated helpdesk tickets for this issue. 4. RTC 271096 - The CPRS Window needs to display "No PACT assigned at any VA location" for patients with no PACT team assignments at any VA location instead of displaying the label of "PACT: No Local PACT Assigned" for all local divisions. The Velocity template in the database was changed to not display "PACT: No Local PACT Assigned" per site if there is no PACT assignments anywhere. CA-SDM Ticket: No associated helpdesk tickets for this issue. 5. RTC 611715 - The R25 Alert Rule for Multi-PACT (MPACT) patient relocation sent as a PCMM Web alert when the patient completes relocation needs to be clearer for the PCMM Coordinators. (i.e. The patient "xxx" has completed the relocation to station "xxx". The patient must be unassigned from all PACT assignments at all stations other than station "xxx". The Multiple PACT request for this patient at station "xxx" is being WITHDRAWN.) The R25 Alert Rule verbiage in the configuration file was updated as requested so this alert is clearer to the users in PCMM Web. (i.e. The relocation to station "LAKE BALDWIN VA CLINIC (#675GG)" for the patient "Doe, John M." has completed. The patient must be unassigned from all PACT assignments at all stations other than station "LAKE BALDWIN VA CLINIC (#675GG)".) CA-SDM Ticket: No associated helpdesk tickets for this issue. 6. RTC 578628 - The query for the "View Team Attributes Change History" link on the team profile screen was using the Java Persistence Query Language (JPQL) and not performing at optimal speed. The JPQL was replaced with a Structured Query Language (SQL) query to optimize query performance. CA-SDM Ticket: No associated helpdesk tickets for this issue. 7. RTC 411473 - The Inpatient provider data displays in the CPRS window but the verbiage message stating "Patient was not found for local site!" when a patient is not pulled into PCMM Web needs to be clarified. The verbiage in CPRS window was changed as recommended when the patient is not pulled into PCMM Web for the station the user is viewing the CPRS patient chart. CA-SDM Ticket: No associated helpdesk tickets for this issue. 8. RTC 542040 - Fortify Scans suggested a security update for the Java Server Pages (JSP) parameter not being initialized. Fortify suggested correcting it by adding the initialization of JSP parameter to default value which is FALSE. The suggested correction caused the team list being returned during the patient assignment process to be restricted to the station the user was logged into. Changed the JSP parameter value to TRUE to display all teams within the same 3 digit station during the patient assignment process. CA-SDM Ticket: No associated helpdesk tickets for this issue. 9. RTC 625600 - The CPRS Header Sync job needs to update a patient's Primary Care assignment when the Direct Care Provider (DCP) team roles have a staff change. DCP team roles include PCP, AP, NPAP and PAAP team roles for primary care. A new Java Data Access Object (DAO) method was created with a simplified specialized query that marks VistA patient records for CPRS Header updates when the DCP staff members change. Then the Java code that called the old method was updated to call the new method for staff assignment/unassignment/reassignment for the DCP positions. NOTE: This defect is not a retro fix for current tickets but should correct the issue moving forward. To fix current tickets, the CPRS Header Sync job will have to be run manually per patient or possibly per team based on ticket/user information. CA-SDM Ticket: I17542701FY18 I17251691FY18 R17232892FY18 I17209300FY18 I16986514FY18 I16950434FY18 I16933653FY18 R16928242FY18 I16927384FY18 I16925563FY18 I16587227FY17 I15675712FY17 10. RTC 631001 - When a user tries to assign a patient to the same primary care team by clicking the ASSIGN button, a DB error message appears that is not readable to the user. A validation rule was added to prevent the DB error from displaying and provide a message to the user that this is not the correct process when the user tries to assign patient to the same team by clicking the ASSIGN button. The verbiage of the message should be: "The patient "{0}" is assigned to the team "{1}" more than once for the same time range." CA-SDM Ticket: No associated helpdesk tickets for this issue. 11. RTC 631031 - Need to create a validation rule to prevent a user from changing the PCP staff role that would break the preception rules for existing AP(s) with direct patient assignments on the team. A validation rule was added to the staff assignment code that will display a validation error to prevent a user from changing the PCP staff role that would break perception with existing AP(s) with direct patient assignments on the team. The verbiage of the message should be: "The patient "{0}" is assigned to the position "{1}" from xx/xx/xxxx xx:xx EDT onward, but this position's preceptor is not active over this date range." CA-SDM Ticket: No associated helpdesk tickets for this issue. Implementation: =============== The PCMM Web WEBP*1*15 is a centrally managed web-based application and will be implemented and deployed to a central web server. No installation is required by sites. Implementation Files: ===================== None Patch Components: ----------------- Files & Fields Associated: N/A Forms Associated: N/A Mail Groups Associated: N/A Options Associated: N/A Protocols Associated: N/A Security Keys Associated: N/A Templates Associated: N/A Additional Information: ----------------------- N/A New Service Requests (NSRs): ----------------------------- 20070415 - Rehost/Reengineer PCMM Patient Safety Issues (PSIs): ------------------------------ N/A CA-SDM Ticket(s): ----------------- 1. I17542701FY18 - PCMM Web / CPRS Header Update / Canandaigua VA 528A5 & Rochester CBOC 528GE I17251691FY18 - Discrepancy in CPRS Header R17232892FY18 - VISN 6 Station 565GL Provider Not Showing in CPRS Banner I17209300FY18 - PCMM Web - CPRS header - PCP not updated I16986514FY18 - remedy ticket station 618 - CPRS header not showing changed information / Minneapolis VA 618 I16950434FY18 - CPRS Header not updating I16933653FY18 - PCMM not crossing over to CPRS issue / Orlando VAMC 675 R16928242FY18 - CPRS Header Delay I16927384FY18 - PCMM WEB - 20171012 - CPRS BANNER UPDATE LAGGING Memphis VAMC | 614 I16925563FY18 - FW: PCMM Web - CPRS banner heading not updating Tucson 678 I15675712FY17 - PCMM Web / CPRS Update / Fresno CA 570 Problem: The CPRS Header Sync job needs to update a patient's Primary Care assignment when the Direct Care Provider (DCP) team roles have a staff change. DCP team roles include PCP, AP, NPAP and PAAP team roles for primary care. Resolution: A new Java Data Access Object (DAO) method was created with a simplified specialized query that marks VistA patient records for CPRS Header updates when the DCP staff members change. Then the Java code that called the old method was updated to call the new method for staff assignment/unassignment/reassignment for the DCP positions. Test Sites: ----------- 691 - West LA VAMC 618 - Minneapolis VA HCS 626 - Nashville VAMC Documentation: ============== Documentation Retrieval Instructions: ------------------------------------- Updated documentation describing the new functionality introduced by this patch is available. The preferred method is to retrieve files from download.vista.domain.ext. This transmits the files from the first available server. Sites may also elect to retrieve files directly from a specific server. Sites may retrieve the software and/or documentation directly using Secure File Transfer Protocol (SFTP) from the ANONYMOUS.SOFTWARE directory at the following OI Field Offices: Hines: domain.ext Salt Lake City: domain.ext Documentation can also be retrieved from the VA Software Documentation Library (VDL) on the Internet at the following address: http://www.domain.ext/vdl. File Description File Name SFTP Mode -------------------------------------------------------------------------- Patient-Centered Management PCMM WEB VDD WEBP_1_15.DOCX BINARY Module(PCMM) Web Patient-Centered Management PCMMR_POM.DOCX BINARY Module (PCMM) Web Project Operations Manual Patient-Centered Management PCMM_WEB_USER_GUIDE.DOCX BINARY Module (PCMM) Web User Guide Patch Installation: =================== There is no local VistA installation for PCMM Web. All installations will be done on the national web server. Pre/Post Installation Overview: ------------------------------- N/A Pre-Installation Instructions: ------------------------------ N/A Installation Instructions: -------------------------- N/A Post-Installation Instructions: ------------------------------- N/A ADDITIONAL INFORMATION: ======================= If you have any questions concerning the implementation of this application, please contact the VA Service Desk at 1-888-596-4357 or directly log a CA SDM ticket using the category: NTL.APP.HealtheVet VistA.PCMM Web. Routine Information: ==================== No routines included. ============================================================================= User Information: Entered By : Date Entered : NOV 17, 2017 Completed By: Date Completed: DEC 13, 2017 Released By : Date Released : DEC 20, 2017 ============================================================================= Packman Mail Message: ===================== No routines included