CPRS GUI v.30A (Patch OR*3.0*385)
Department of Veterans Affairs
Office of Information & Technology (OI&T)
Product Development (PD)
Below is a list of patches that you must verify are properly installed on your system before OR*3.0*385 can be installed:
Although not required for the patch to install, there are many other patches that will need to be installed so that this version of the CPRS GUI will run properly. Please see the CPRS GUI 30.A Installation Guide for further instructions.
CPRS GUI v.30A consists of patch OR*3.0*385 and a GUI executable (cprschart.exe). It is part of the larger effort to change from using ICD-9 codes to using ICD-10 codes. The ICD-10 project requires a large number of patches from numerous packages to make the change from the ICD-9 coding system to the ICD-10 coding system.
The ICD-10 program will oversee the release of all patches on a schedule that enables the complete change to ICD-10 prior to the official implementation date. The patches will be released in groups so that sites are not overwhelmed with more than 30 patches that must be installed all at once. All of the necessary patches will be installed on the affected VA systems, but will not start using ICD-10 codes until the specified ICD-10 activation date arrives. On the specified date, the change should happen seamlessly.
CPRS GUI v.30.A will have a deployment schedule in which groups of sites (sometimes called "waves") will install according to a schedule. Grouping sites for installation ensures that the CPRS development team can appropriately support sites that installing during the specified time period. The CPRS Deployment Manager will contact each site with further details at the time for national release and deployment approach.
For specific information on the CPRS GUI v.30.A installation, please see the CPRS GUI version 30.A Installation Guide.
When the user first runs the executable after the CPRS 30.A installation, it may take several minutes for CPRS to come up. With CPRS GUI v.30.A, CPRS configures itself when the user double-clicks the icon, which is a change from past versions. Unfortunately, there is no indicator to tell the user that CPRS is getting ready to run the new version. Users must be patient and let CPRS run through the set up for the new version. If the user continues to click on the icon, multiple CPRS sessions could be launched and the machine may not be able to handle all the sessions.
The Department of Veterans Affairs in compliance with a mandate from the federal government is implementing the new International Classification of Diseases, Tenth Revision (ICD-10) coding system for diagnoses relating to billing purposes and other data capture. The new ICD-10 revision is a much more detailed coding system with new codes, new definitions, and more detailed concepts of medical treatment, such as whether items are a follow-up visit and if the patient is progressing in their treatment or not.
The change to the new ICD-10 system is mandated currently to occur on October 1, 2015. The change will affect any codes related to billing of medical expenses. It is a huge undertaking and there are over 30 patches involved in making this change.
In CPRS, users will see changes in the areas where ICD codes are displayed or entered—especially in encounters and how it relates to the problem list.
Cover Sheet Active Problems Pane
On the Active Problems pane, the hash symbol or pound sign (#) for inactive codes is no longer used. The information will still be available in the detailed display, but CPRS no longer displays this symbol as an identifier in the list of problems.
ICD-10 codes if linked to problems display in the detailed display when the user selects a problem from the Cover Sheet.
Prior to the ICD-10 implementation date (October 1, 2015), the Problem List software within CPRS GUI 30.A will function as it currently does in CPRS v.29. However, once the ICD-10 implementation date becomes active, the ICD features of the Problem List will be enabled. New problems added to the Problems List by default are assigned an ICD-10 code of R69, which is equivalent to the 799.9 code in ICD-9. If the provider assigns a more specific code to a problem during Encounter checkout, the specified ICD-10 code will display in the Detail view of the problem. There is no direct mapping of SNOMED codes by which problems are defined on the Problem List and ICD-10 codes that are used for encounter checkout and billing purposes. The provider will have to manually assign the ICD-10 code to the problem during Encounter checkout.
Providers can select one or more problems from the Problem List as a diagnosis for the visit, but if the problem is expressed as a SNOMED term and code, the provider must select an ICD-10 code for the diagnosis. All new problems entered on the Problem List are expressed as SNOMED terms and codes and given a default ICD-10 code of R69 (illness, unspecified), which is equivalent to the 799.9 code in ICD-9. The R69 code must be changed to a more specific ICD-10 code. When the user selects a SNOMED code, CPRS brings up the Lexicon Look Up dialog so that the provider can look up and select a specific ICD-10 code for the diagnosis.
After the provider selects and ICD-10 code, CPRS again brings up the Lexicon Look Up dialog so that the provider can look up and select a specific SNOMED code for the problem so that the Problem List is updated with the new ICD-10 code.
On the Consults tab, providers often use the Lexicon search to look up a provisional diagnosis. After the ICD-10 activation date, those Lexicon searches will now use ICD-10.
On some Clinical Reminder dialogs, providers can make selections that will use diagnosis codes. After the ICD-10 activation date, those codes will now be ICD-10 codes.
Some Health Summary components display ICD codes. As new codes are added in the new coding system, those codes will display in health summaries with the ICD description, the coding system, and the code.
Resolution: CPRS developers corrected the problem and the order is displayed correctly only once.
Resolution: CPRS developers corrected this problem. If the user begins the signature process but does not enter their PIV PIN, the orders requiring the PIN will not be signed and the unsigned order alert will now be generated correctly.
Resolution: Developers correctly the problem and the Icon Legend now displays correctly. If your site chose to use the workaround and put an item on the Tools menu to reach the web page with the icon legends, you may want to remove the items from the tools menu. Instructions for this can be found in the CPRS Technical Manual: GUI Version.