qcpr 6.0.1 defect resolution report · 2019. 9. 2. · quadramed corporation 1 defects resolved in...

QCPR 6.0.1.45

Defect Resolution Report

Client Support

Phone: 877.823.7263

E-Mail: [email protected]

QuadraMed Corporation Proprietary Statement This material constitutes proprietary and trade secret information of the QuadraMed Corporation, and shall not

be disclosed to any third party, nor used by the recipient except under the terms and conditions prescribed by

the QuadraMed Corporation.

The trademarks, service marks, and logos of QuadraMed Corporation and others used herein are the property

of QuadraMed or their respective owners.

QuadraMed Corporation Copyright Statement This material is also protected by Federal Copyright Law and is not to be copied or reproduced in any form,

using any medium, without the prior written authorization of the QuadraMed Corporation. However, the

QuadraMed Corporation allows the printing of the Adobe Acrobat PDF files for the purposes of client training

and reference.

Contents copyright © 2015 QuadraMed Corporation. All rights reserved.

QUADRAMED CORPORATION® All Rights Reserved. i

Table of Contents

DEFECTS RESOLVED IN 6.0.1 UPDATE 45 ........................................................................................................................ 1



DEFECTS RESOLVED IN 6.0.1 UPDATE 42 ...................................................................................................................... 11





















DEFECTS RESOLVED IN 6.0.1 UPDATE 21 .................................................................................................................... 101








QUADRAMED CORPORATION 1

Defects Resolved in 6.0.1 Update 45

CASE NUMBER DESCRIPTION

857216 Summary

Background job errors occurred when entering orders for new visits.

Symptoms

When a new visit was created during patient registration and subsequently the Order Entry menu function or application was used to enter orders on the newly created visit, the orders for new visits occasionally did not file. When this occurred, the System generated the message: Empty err msg at: dofv+12^noe3 for program %zu2c%zer in the Error Log Display menu function. When users entered the order again, no error was generated.

Cause

Recent InterSystems Caché changes to better handle how record locking and unlocking were performed, introduced a scenario where a newly created visit during patient registration may not have completed filing to the database when orders in order entry attempted to file for the newly created visit. In this scenario, the QCPR Audit Log attempted to log the addition of orders to a visit which had not completed filing to the database. This resulted in the Empty Error message as no visit was identified by the System.

Resolution

The Order Entry menu function and application have been updated to verify that a visit record has been filed and is not locked before attempting to log the activity.

857551

Summary

A checkerboard pattern displayed in place of patient data in the Patient List application after a refresh.

Symptoms

When a provider viewed the list of patients in the Patient List application, they initially saw all the patients. However, after the provider reviewed an item on the patient level, closed the record, accessed the Main desktop, and refreshed the list of patients, the line where patient information displayed previously only displayed a checkered pattern.

Cause

After refresh, the Patient List application was attempting to display an entry for a patient that was already processed (i.e., trying to display outdated information that no longer existed).The resulting Clinical Desktop Application default display was the checkerboard.

Resolution

The Patient List application now refreshes properly when accessed after patient processing and displays current patient information.


QUADRAMED CORPORATION® All Rights Reserved. 2


857568 858031

Summary

Users were unable to launch the latest version of the Clinical Desktop Application (CDA) when installed with the Microsoft Installer.

Symptoms

When the Microsoft Installer (MSI) was used to install the Clinical Desktop Application, some menu functions and applications, such as Media Manager and eFile generated error messages when CDA was installed with this method.

Cause

When the MSI installed was used, the QUADRAMED CPR.LAX file contained malformed entries in the following sections:

# LAX.CLASS.PATH

# LAX.NL.CURRENT.VM

The following CDA builds were affected:

6.0.1

-6.0.1 builds 124-128

Resolution

The Microsoft Installer (MSI) for CDA has been updated to install with the appropriate directory paths for the installation files in the following sections:

# LAX.CLASS.PATH

# LAX.NL.CURRENT.VM

857683 Summary

Print queue code missing! errors occurred for specific print jobs.

Symptoms

When viewing the Error Log Display menu function, many Print queue code missing! errors displayed. The error messages also displayed in the user’s QCPR mailbox.

Cause

A Print queue code missing! error message is logged when a report is printed which does not obtain a valid print queue ID. When the Print Utility encountered a report which had an expression to designate to a specific print queue, the print queue ID was not identified properly.

Resolution

The Print Utility has been updated when print jobs for reports which print to a specific printer or print queue now obtain the proper print queue ID.

NOTE: When a report continues to generate a Print queue code missing! error message after this update is applied, then the Print Queue expression in the Report Definition may require review.




857903 Summary

Yes/No buttons for order, result and assessment Choose data elements displayed in English on non-English Systems.

Symptoms

In QCPR, questions are constructed that determine the following:

Whether the Yes/No buttons display for the question

The text that displays on the Yes/No buttons at the transaction line

A previous change to the System included Yes/No transaction line buttons which were excluded. In this scenario, Yes/No buttons for order entry, result entry or assessment Choose data elements have been included.

Cause

When a Choose data element is constructed, values are associated for each response. When the Alternate Language Translation utility processed the response for a non-English language and the letter did not match the English equivalent (e.g., O for Oui versus Y for Yes), the translation aborted.

Resolution

The above Choose data elements now identify the mapping from English to non-English values and process the language translation accordingly.

AF Loop, Screen Rebuild, UDD & Report Change Information

There are no screens that need to be built with this update.

There are no AF Loops that need to be run with this update.

Defects Resolved in 6.0.1 Update 45 (CDA Build 128) (QCPR Build 81) (ISDID Build 38) (PAM Build 6.0.13.607)





840064 Summary

Criteria engine evaluations created using the Criteria Engine Table, ^nt(“ce”), incorrectly routed patients from one facility to management queues of another facility.

Symptoms

A site with two facilities had management queues in both facilities showing patients from both facilities, despite each facility using different management queues, criteria engines, desktop, applications, and separate criteria engine lists.

Cause

There was no internal identifier for the facility, visit, or registration criteria. The criteria engine lists were created for both facilities instead of being separated.

Resolution

The Criteria Engine Table, ^nt(“ce”), now supports a facility key. For System-specific criteria, a type key is added to differentiate between visit and registration data. Also, when the criteria searches for criteria engine lists, facility-specific criteria displays appropriately for separate facilities.

842117

Summary

The Document Editor application generates a NullReferenceException error when creating a Continuity of Care Document (CCD).

Symptoms

When creating a Continuity of Care Document (CCD) using the Document Editor application, a NullReferenceException error is generated.

Cause

In the Clinical Desktop Application (CDA) that required an instance of an object, a null value was found. This generated a NullReferenceException error.

Resolution

This issue has been resolved. The Document Editor application now creates the CCD without error.

847915 Summary

Management queues were not populating based on settings in the Criteria Engine Table, ^nt(“ce”).

Symptoms

A criteria engine evaluation was defined to populate a management queue with the patients who have been discharged for X number of days. The discharged patients did not populate the management queue.

Cause

Any criteria defined in the Criteria Engine Table, ^nt(“ce”), that has aging operators such as “since x days”, are pushed into a queue for further evaluation when the time criteria meets. When the specified time passes, a background process further picks these criteria from the queue and re-evaluates them. In this logic, the evaluating criteria failed to re-evaluate the criterion properly and failed this aging criterion. As a result, the queues did not get updated with the specified data.

Resolution

This issue has been resolved. When requested criteria pass during re-evaluation, the data appropriately populates the management queue.




849732 Summary

Users were unable to document an associated procedure prior to its super-procedure’s first event.

Symptoms

Users could not select to administer an associated procedure in the Medication Administration menu function. The procedure could have a PRN frequency or scheduled events.

Cause

The start time of the sub-procedure is relative to the first event of the super-procedure. The System does not allow an associated PRN procedure to be documented until the time of the first event of the super-procedure. This rule also applies to scheduled sub-procedures. The System currently checks for date/times in the past (or before the base time) so users cannot enter a relative start date/time for the associated procedure. The start time of the associated procedure would be considered in the past, based on the time of the first event of the super-procedure.

The following are examples of the current time-check restriction:

● A super-procedure scheduled daily at 2200 does not allow a user to document a PRN event for a sub-procedure prior to 2200.

● A super-procedure scheduled for tomorrow at 0600 with a sub-procedure scheduled for NOW means the NOW order cannot be documented until tomorrow at 0600. With the current System check in place, it is not possible to schedule the NOW order as now-24h.

Resolution

The System now allows users to define a start time for sub-procedures before the first event of the super-procedure. For example, for the sub-procedure to start an hour before the super-procedure, the proper frequency is “prn start at now-1h” or “today-1”.

852369 Summary

Wild card search did not work correctly on screen drivers of reports containing employee-related data elements.

Symptoms

When executing a screen-driven report containing a data element(s) referencing the Employee/Provider Table, ^ae, searches using the wild card “-” displayed incorrect results.

Cause

The lookup routine for the employee-related data elements was incorrect.

Resolution

The Report Formatter Data Dictionary Table, ^arfd, has been updated to use the correct lookup routine when the affected data elements are used in screen driver reports.




853519 Summary

The Concept Mapping Tool application displayed incomplete search results for problem codes.

Symptoms

When searching for problems using the Concept Mapping Tool application, the search did not return all of the expected codes for the selected problems

Cause

When new entries are added in the Coding Scheme Table ^nt("cs"), Java enumerations also need to be updated in the code for the Clinical Desktop Application. Java enumerations were not updated in the Clinical Desktop Application when new entries were added in the Coding Scheme Table, ^nt(“cs”).

Resolution

Searching for problems in the Concept Mapping Tool application now returns all appropriate codes.

854537 Summary

Completed events still appeared in the Results to Complete column of the Provider Inbox Across Patients application.

Symptoms

In the Provider Inbox Across Patients application, completed events remained in the inbox when they should have been removed. When the user selected the event, the error Lock event error: Event does not exist displayed.

Cause

An error occurred between the System lock and background job mechanisms, which produced a misalignment of event pointers.

Resolution

Events to be resulted now display appropriately in the Provider Inbox Across Patients application.

855081 Summary

Users were unable to merge problems using the Clinical Information Reconciliation application.

Symptoms

In the Clinical Information Reconciliation application, when selecting all problems to merge, only the free-text allergies merged successfully.

Cause

The problems that were imported using the Clinical Information Reconciliation application were missing important information such as the code from a coding scheme, problem type, and problem name. This in turn caused the merge to fail.

Resolution

Problems are now imported with the required information.




855483 Summary

Report query was truncating data when viewing from the Chart Review menu function.

Symptoms

When a user selected the report query option for an event in the Chart Review menu function, the data was truncated.

Cause

The report query in the Chart Review menu function was incorrectly interpreting reserved HTML characters such as < and >.

Resolution

The report query now correctly interprets reserved HTML characters.


Rebuild any screen drivers for reports containing employee-related data elements when having the problems described in Case 852369.

Run 6.0 AF loop 68 “rebuild criteria engine ntce table inversions”

Any hook reports based on the Accession Interface hook need to be rebuilt for this change to take effect.






852772

Summary

Users were unable to access subfolders in the Order Entry application.

Symptoms

When users attempted to open a subfolder defined in the Procedure Selection Tree Table, ^nt(“ps”), in the Order Entry application, the folders would not expand to allow access.

Cause

The System did not add procedure selection trees to subfolder(s) when module links were not defined appropriately in the Customer Table, ^afc.

Order sets/procedure selection trees are available from the following two tables:

Evidence Based Order Set Table, ^nt(“oset”)

Procedure Selection Tree Table, ^nt(“ps”)

Order sets from the Evidence Based Order Set Table, ^nt(“oset”), require a module link defined in the Customer Table, ^afc. Procedure selection trees from the Procedure Selection Tree Table, ^nt(“ps”), do not require a module link.

Resolution

Procedure selection trees defined in the Procedure Selection Tree Table, ^nt(“ps”), now display with subfolders without additional licensing.

*Note: Issue resolved with CDA build 119 or greater

854145 Summary

Order entry selection screen items were being truncated in the Order Entry menu function.

Symptoms

In the Order Entry menu function, the order names displaying in the list of orders were being truncated and replaced with an ellipsis (…).

Cause

This was a formatting issue introduced with a new bookmark feature. When a bookmark was not present, the screen did not provide adequate space for the full name of the procedure to display.

Resolution

A space has been implemented before and after the procedure name so that the procedure name no longer cuts off.





854657 Summary

Incorrect block headers displayed in evidence-based order sets in the Order Entry application. Symptoms

Whenever an evidence-based order set from the Evidence Based Order Set Table, ^nt(“oset”), was selected in the Order Entry application, the header name displaying in the block header was different than the order set folder names that displayed below the order options.

Cause

The block header name was pulled from the Procedure Selection Tree Table, ^nt(“ps”), instead of the Evidence Based Order Set Table, ^nt(“oset”). This caused the incorrect header to display.

Resolution

The System now retrieves the correct header name from the Evidence Based Order Set Table, ^nt(“oset”).


825930 Summary

The Allergy Assessment data element in the Criteria Engine Table, ^nt(“ce”), did not have a match in the Allergy Definition Table, ^pt(“ad”).

Symptoms

Users could not select options from the Allergy Definition Table, ^pt(“ad”), or the Allergy Symptom Definition Table, ^pt(“ads”), when defining criteria using the Assessment Multiple Fields data elements.

Cause

When defining a constant from the Allergy Definition Table, ^pt(“ad”), or a constant from the Allergy Symptom Definition Table, ^pt(“ads”), the constant could not be selected because the Allergy Definition Table, ^pt(“ad”), and the Allergy Symptom Definition Table, ^pt(“ads”), are facility dependent and facilities were not being defined for the non-facility specific Criteria Engine Table, ^nt(“ce") and the Interactive Criteria Table, ^nt("ice").

Resolution

1. The non-facility specific Criteria Engine Table, ^nt(“ce") and the Interactive Criteria Table, ^nt("ice") were enhanced with the option to select the facility for the Assessment Multiple Field Allergy and Allergy Symptom data elements.

2. An af loop was created to restructure existing criteria definitions in the non-facility specific Criteria Engine Table, ^nt(“ce") and the Interactive Criteria Table ^nt("ice") with the Assessment Allergy and Allergy Symptom data elements.

854784 Summary

Care plans set to auto-resolve at discharge were remaining active.

Symptoms

When the Problem List Master Table, ^nt(“plm”), Auto Resolve Definition field, Auto Resolve Delay subfield was defined as 1 day, all care plans resolved 1 day after a patient discharge. However, patient care plans stayed active in the patient chart.

Cause

The System attempted to create an auto resolve inversion for the problem list and attempted to search every problem on the patient record. However, when a problem was not linked to the Problem List Master Table, ^nt(“plm”), the search stopped prematurely and ignored the rest of the patient's problems.

Resolution

When a problem is not linked in the Problem List Master Table, ^nt(“plm”), the System now skips the problem entry and continues searching through the remaining problems.




855537 Summary

Physician inboxes were freezing and orders were re-appearing.

Symptoms

When users signed off orders in his/her inbox, the screen froze with Java errors, forcing users to terminate the session. Once users logged back in, the signed orders remained in the inbox.

Cause

When users elected to sign off items in several large groups, several locks were generated. This caused the screen to freeze.

Resolution

The Clinical Desktop Application (CDA) now only files one batch of orders at a time instead of all orders at once.









852772

Summary


Symptoms

When users attempted to open a subfolder defined in the Procedure Selection Tree Table, ^nt(“ps”), in the Order Entry application, the folders would not expand to allow access.

Cause

The System did not add procedure selection trees to subfolder(s) when module links defined in the Customer Table, ^afc, were not defined appropriately.

Order sets/procedure selection trees are available from the following two tables:



Order sets from the Evidence Based Order Set Table, ^nt(“oset”), require a module link defined in the Customer Table, ^afc. Procedure selection trees from the Procedure Selection Tree Table, ^nt(“ps”), should not require a module link.

Resolution


854145 Summary

Order entry selection screen items were being truncated in the Order Entry menu function.

Symptoms

In the Order Entry menu function, the order names displaying in the list of orders were being truncated and replaced with “…”.

Cause

This was a formatting issue introduced with a new bookmark feature. When a bookmark was not present, the screen did not provide adequate space for the full name of the procedure to display.

Resolution

A space has been implemented before and after the procedure name so that the procedure name no longer cuts off.




854657 Summary

Incorrect block headers displayed in evidence-based order sets in the Order Entry application. Symptoms

Whenever an evidence-based order set from the Evidence Based Order Set Table, ^nt(“oset”), was selected in the Order Entry application, the header name displaying in the block header was different than the order set folder names that displayed below the order options.

Cause

The block header name was pulled from the Procedure Selection Tree Table, ^nt(“ps”), instead of the Evidence Based Order Set Table, nt(“oset”). This caused the incorrect header to display.

Resolution


854840 Summary

Users received a Global subscript length error in the field created from the Result Entry Profile Table, ^nt(“rp”), Multiple Field Screen Definitions subfile or the Result Entry Profile Definitions subfile, Free-Text data element.

Symptoms

While documenting in a field created from the Result Entry Profile Table, ^nt(“rp”), Multiple Field Screen Definitions subfile or the Result Entry Profile Definitions subfile, Free-Text data element, the System returned a Global subscript length error.

Cause

The System displayed an error due to a large amount of documentation text in the Free-Text data element field. This occurred due to a missing program that helps retrieve data from the global subscript.

Resolution

The System is now able to handle large documentation text in the Result Entry Profile Table, ^nt(“rp”), Free-Text data element field.

854973 Summary

Weight-based dosages that began with a decimal point did not display a preceding zero in the Patient Order Review Queue menu function.

Symptoms

Weight-based dosages (mcg/kg, mL/kg, mEq/kg, mcg/kg/hr, etc.) entered with numeric values that start with a decimal point displayed without a preceding zero in the Patient Order Review Queue menu function. This is a violation of The Joint Commission requirements.

Cause

The dosage conversion code was not properly used in this scenario.

Resolution

The dosage is now converted properly and shows the preceding zero for decimals.




855223 Summary

The Physician Review Queue menu function displayed inaccurate queue counts.

Symptoms

In the Physician Review Queue menu function, the review queue count at the top level showed a numeric value indicating there were items to be reviewed in the queue. When the user selected one of these items, the System did not display anything at the sublevel that needed to be reviewed.

Cause

The Clinical Desktop Application (CDA) was not properly handling PAR Review Hold entries. This review queue type contains special logic whereby entries are filtered out from the display when the originating order is discontinued. In these instances, the orders were appropriately removed but the count was not properly updated.

Resolution

The System now updates the queue count and removes the appropriate items from the review queues.

855468

Summary

Changing the frequency time on an order during order entry would remove the originating order time from the Chart Review menu function. Symptoms

When users entered a radiology order and an MRI as the procedure with a specific date in the Frequency field and then changed the order to unscheduled, the new time disappeared in the Chart Review menu function and the edit time displayed instead.

Cause

This issue was due to the scheduler’s perspective of an unscheduled single event as it is scheduled like a now event. The base time for single events is the order block time so the interpretation of now was before the effective time and no event was scheduled.

Resolution

The algorithm was modified to use the effective time as the base for unscheduled single events.




This CR will force the load utility to recompile approximately 450 classes on build load.






851423

Summary

Results were not appropriately filing to a lab interface.

Symptoms

When a micro culture had a reportable organism resulted through a lab interface and there was a comment attached to that organism that filed in the Result Entry Profile Table, ^nt(“rp”), Multiple Field Screen Definitions subfile or the Result Entry Profile Definitions subfile, Word Processor date element, it did not route to the proper queue to file to the interface.

Cause

The criteria engine failed to appropriately trigger, depending on the data elements used for documentation. This had to do with the underlying data model that was stored in the database. Word Processor data elements and multiple fields specifically were stored differently. In some cases they were stored in a tree structure as opposed to a node value. The algorithm in this case did not appropriately consider the differences between the two structures. Therefore the data was not being loaded correctly in this case and caused the criteria engine to fail.

Resolution

The criteria engine algorithm now appropriately considers the two structures that store Word Processor data element data.

853905 Summary

System Management Portal displayed an error when the user attempted to run certain queries.

Symptoms

When attempting to run queries through the Systems Management Portal, the user would receive the error: Error Message:SQL Error (ERROR #5540).

Cause

This error occurred when queries were run on the shadow server. The System currently does not support running queries to collect certain statistics on the shadow server. These are internal statistics and have nothing to do with typical data accessed by the client.

Resolution

System-level statistics are now excluded when queries are run on the shadow server.




847398

848382

849598

Summary

When using the Drug Query (API) application and selecting the option to print drug information, the patient gender did not default in the print dialogue window.

Symptoms

When printing drug information in the Drug Query (API) application from the main desktop, the print dialogue window had no value for gender even when patient gender was defined as Male or Female.

When running the Drug Query (API) application from the visit desktop for a male patient, the print dialogue window showed gender as Unknown. This only occurred for male patients.

Cause

QCPR was not using the gender of the patient indicated on the main Drug Query (API) window when printing drug information.

Resolution

A new ISDID update now uses the gender of the patient as indicated in the main Drug Query (API) window as the default gender in the print dialogue window when printing drug information in the Drug Query (API) application.

854596 Summary

User received a Java error when attempting to access the Interactive Care Grid application on the Clinical Desktop Application (CDA).

Symptoms

When the user accessed the Interactive Care Grid application at the patient level, the screen froze, displaying an hour glass, and eventually generated a Java error.

Cause

This was caused by a display issue where the Java code interpreted a particular combination of characters inappropriately. This in turn resulted in the application not loading the data and causing the error.

Resolution

The interpretation of these characters has been changed to display this application and its data appropriately.

855223 Summary

The Physician Review Queue menu function displayed inaccurate queue counts.

Symptoms

In the Physician Review Queue menu function, the review queue count at the top level showed a numeric value indicating there were items to be reviewed in the queue. When the user selected one of these items, the System did not display anything at the sub-level that needed to be reviewed.

Cause

The Clinical Desktop Application (CDA) was not properly handling PAR Review Hold entries. This review queue type has special logic whereby they are filtered out from the display if the originating order is discontinued. In these instances, the orders were appropriately removed but the count was not being properly updated.

Resolution

The System now updates the queue count and removes the appropriate items from the review queues.




845989

846093

Summary

Calculated dose did not display in the Department Order Review Queue menu function or Department Order Review Queue application.

Symptoms

When a provider inputs a telephone or written order, the dose displays as mL instead of mg during product selection in the Department Order Review Queue menu function or Department Order Review Queue application.

Cause

The Department Order Review Queue menu function or Department Order Review Queue application failed to convert the dose in product information in the internal product.

Resolution

The Department Order Review Queue menu function and Department Order Review Queue application properly converts the product strength/unit to order units.

837996

Summary

The (A) Accept processing option did not display after changing a product from floor stock to department during product selection in the Order Entry menu function. Symptoms

During product selection, the (A) Accept processing option did not display after the user selected a multiple component medication. When the System prompted if the product was floor stock? and the user selected no, only the OK button displayed.

Cause

The System only considered a portion of the information as complete during product selection and did not allow the (A) Accept processing option to display. Resolution

The Order Entry menu function has been corrected to move down the full length of the structured order and now includes the product source information for product selection processing to be accepted.

854657

Summary

Incorrect block headers displayed in evidence-based order sets. Symptoms

Whenever an evidence-based order set from the Evidence Based Order Set Table, ^nt(“oset”), was selected in the Order Entry application, the header name displaying in the block header was different than the order set folder names that displayed under the order options.

Cause

The block header name was being pulled from the Procedure Selection Tree Table, ^nt(“ps”), instead of the Evidence Based Order Set Table, nt(“oset”). This caused the incorrect header to display.

Resolution





818125 836612 847657

Summary

Error message displayed when accessing SQL tables via the Caché System Management Portal. Symptoms

When the user attempted to open a certain table in the Caché System Management Portal, the user would receive a Missing Routine Error. Cause

The issue was caused by the classes not being capable of distinguishing the difference between types of results (assessment versus result profile and such). Resolution

A change has been made so that the classes can now distinguish between the result types.

852449 853891 852878

Summary

Medications without a defined NDC were not sent to DrFirst. Symptoms

When investigating report issues, it was discovered that the number of eRx Pending prescriptions in DrFirst was lower than the number of eRx Pending prescriptions reported in QCPR.

Cause

The current rule to not send “uncoded (No NDC)” medications to DrFirst caused a mismatch and QCPR prescriptions remained with a status of eRx Pending. Since the prescriptions were not posted in DrFirst, there was no prescription to sign and submit to the retail pharmacy. A code restriction did not allow prescriptions from QCPR to be sent to DrFirst when an NDC was not defined in the order.

Resolution

*Changes related to this issue have been included in 6.0.1 Update 40 and higher releases.

The restricted code has been changed to allow prescriptions that are not coded to go from QCPR to DrFirst.

In the ePrescribing Portal Launch application, the status of Schedule Unknown, under the Serial # field, indicates a prescription is uncoded. The System prompts Drug Type? allowing the user to choose Yes, No, or Not Sure. The Not Sure option does not allow the prescription to be sent electronically.

The user can also choose the Change Drug option. This allows the user to go to the Prescribe a Medication field. There, the user can select the form and update any dispensing instructions to match the new product before using the Continue option to transmit the prescription electronically.


This update will force the Load Utility to recompile approximately 1 class upon build load.

There are 20-30 SQL Connect classes that will be compiled.

Report Writer (ARFD) reports must be rebuilt with this update.







837970

Summary

Reports using the visit:event:result:result profile field:multimedia object code record definition generated errors.

Symptoms

When the user attempted to build a report within the Hierarchical Filing Structure menu function, reports defined to use the visit:event:result:result profile field:multimedia object code record definition received a build error message, Field ‘multimedia object code’ not available!

Cause

The visit:event:result:result profile field:multimedia object code record definition had been retired inappropriately in the 5.3.0 releases and higher. QuadraMed Development had updated the Report Formatter Data Dictionary Table, ^arfd, to enforce usage of the visit:event:result:result profile field:primary multimedia object code record definition by limiting the availability of the visit:event:result:result profile field:multimedia object code record definition.

Resolution

The visit:event:result:result profile field:multimedia object code record definition has been reinstated as the recommended record for multimedia data element primary key access.

844453

846769

845763

Summary

Calculated dose/labels for premix or diluents displayed incorrectly in the Department Order Review Queue menu function.

Symptoms

When doing change orders for IV premix drips in the Department Order Review Queue menu function, the first label printed with the previous premix as the product and labels printed incorrectly with mL instead of mg.

Cause

The premix and diluents were not being calculated correctly with the appropriate volume, resulting in incorrect values printing on the labels.

Resolution

The System now properly calculates the strength and units with the appropriate volume.

850242 Summary

When the user deleted an allergy, transaction lines displayed in the incorrect language.

Symptoms

When deleting an allergy from a documented allergy procedure, transaction lines displayed in English on a French system. This transaction line did not show up to be translated in the translation utility.

Cause

The noted hard-coded lines were not marked to be translated.

Resolution

The hard-coded items now display to be translated.




852110

Summary

Documenting free-text home medications generated a Minimum of 2 characters required error message.

Symptoms

When the user chose the (F) Free-Text processing option in the Home Medication Editor menu function, the Minimum of 2 characters required error message displayed when adding a medication.

Cause

A previous translation modification introduced a translation issue within the Alternate Language Translator utility. This translation generated a Minimum of 2 character required error message when the user chose the (F) Free-Text processing option when adding a home medication.

Resolution

The Home Medication Editor menu function now provides the appropriate translations in the Alternate Language Translator utility and the error message no longer displays.

853656

851447

Summary

Events were not displaying in the physician’s inbox as expected.

Symptoms

Events that should have displayed in the physician’s inbox did not display.

Cause

When using the Result Entry (Multiple Events) menu function or the Result Verification menu function in the context of shared result events, the logic governing whether the result should be sent to a review queue was not working in all cases. When a user makes changes to a result, the System keeps track of the specific fields in question that were changed. However, if the user changed some of the fields, went on to the next screen, and then went back in to the result profile, the System lost track of the fields that were changed.

There was also an issue in the Result Entry (Multiple Events) menu function related to physician queue routing when a procedure was defined to suppress partial results and not route them to the physician inbox in a partial status. When the result was first documented as partial, the event did not get routed to the physician's inbox, as expected. When the user documented the result a second time, the result status changed to complete. At this point, the result failed to route to the physician's inbox.

Resolution

The Physician Inbox application now correctly identifies the events that should route to a queue based on the definition of the Procedure Table, ^t, Chart Review screen, Result Suppression field.




854212 Summary

An incorrect user displayed in the audit trail of a documented procedure.

Symptoms

When a physician signed multiple orders in a batch in the Physician Inbox application and immediately logged off the Clinical Desktop Application (CDA), the audit trail mistakenly displayed the name of an unrelated user instead of the physician who had previously signed off on the data.

Cause

The background job that files the data can take a while depending on the amount of data or because of a lock. When another user logs on to the same device immediately after the physician, the background filing job's $$$Vu (user) special variable is changed to the newly logged-on user. At this point, if the background filing job is still running, the audit trail mistakenly includes the unrelated user.

Resolution

The message Background filing in progress… now displays when users try to log off CDA and background filing is still in progress. This message displays until the background filing completes. Only after filing completes, is a user able to log on again as someone else. This does not permit the logged-on user to change in the middle of filing, preventing the wrong user from displaying in the audit log.

854274 Summary

An error occurred in the Deficiency Manager menu function.

Symptoms

When the user selected a visit date for a specific patient in the Deficiency Manager menu function, the user was kicked out of the session.

Cause

The creation of a very long miscellaneous procedure name caused an error in the Deficiency Manager menu function. The System uses an array to sort one of the Deficiency Manager menu function displays. The miscellaneous procedure name is used as an index for an array. When the name exceeded 255 characters (Caché index maximum length), the error was generated.

Resolution

A change has been made to the way the array of characters is stored in order to prevent the maximum character limit from being reached.

854155

851897

Summary

IVBP labels from the solution preparation queue printed with an incorrect generic name.

Symptoms

Labels printed from the Solution Preparation Queue menu function did not display the correct alias name (generic product) for some IVBP medications. The initial dose label printed correctly for IVPB solutions, but subsequent orders in the Solution Preparation Queue menu function displayed with mismatched generic and brand names.

Cause

The problem occurred with the intermediate file from which the labels were printed. If two different bottles from different orders for the same visit were present in the batch, the intermediate file was overwritten, causing the labels to be lost. In addition, if the first label had a generic name and the second did not, then the System printed the label for the second order with the first order’s generic name.

Resolution

A new expression has been created so that the System now uses the System-generated IV ID as a key. The genc.ivpb_solq_z2.h label report has been enhanced to allow this new key.




Assessment Screen Table, ^nt(“as”), screens must be rebuilt with this update.







825930 Summary

System error prevented allergies from the Allergy Definition Table, ^pt(“ad”), from displaying for selection in the Criteria Engine Table, ^nt(“ce"), and Interactive Criteria Engine Table, ^nt(“ice”) tables.

Symptoms

When users tried to define criteria containing expressions for allergy data, the allergy options in the Allergy Definition Table, ^pt(“ad”), did not display in the following places:

Criteria Engine Table, ^nt(“ce”), Criteria field, Comparison Expression(s) subfield

Interactive Criteria Engine Table, ^nt(“ice”), Criteria field, Comparison Expression(s) subfield

This caused some allergies to not trigger an alert.

Cause

When defining criteria, matching entries from the Allergy Definition Table, ^pt(“ad”), or the Allergy Symptom Definition Table, ^pt(“ads”), could not be selected because those tables are facility-dependent. Facilities are not defined for the Criteria Engine Table, ^nt(“ce"), and Interactive Criteria Engine Table, ^nt(“ice”), tables and this was causing a System error.

Resolution

To resolve this issue, 6.0 AF Loop 68 – populate ntce non-facility specific and ntice assessment allergy and symptom constants was created to restructure existing criteria definitions in the Criteria Engine Table, ^nt(“ce"), and Interactive Criteria Engine Table, ^nt(“ice”), tables. This loop must be run with this update.

816753 Summary

Even though physician group processing was disabled, results reviewed by one provider in the group were no longer available during provider inbox processing for the attending or ordering provider to review in the same provider group.

Symptoms

Physician group processing is enabled when the System Parameter Table, ^%z, Order Comm System Parameters subfile, Facility-specific level, Physician Parameters screen, Group Physician Queue Processing? field is defined as yes. When this field is defined as no, results reviewed by a provider in the same group as an attending provider remain present in the Provider Inbox and Provider Inbox Across Patients applications until they have been reviewed by the attending provider.

When a physician’s provider group was defined at the facility level in the Employee/Provider Table, ^ae, Facility-specific level, Provider Group field, results remained available for the attending provider as expected. However, when the provider group was defined at the employee level, in the Employee/Provider Table, ^ae, Employee-specific level, Physician Parameters field, Provider Group subfield, results did not remain in these applications after being reviewed by another provider in the group.

Cause

When the provider group was defined at the employee level and a provider in the same provider group without any other association to the patient reviewed results, the results were being removed from the attending physician review queue instead of the general review queue. Upon review of the result, the item was removed from the attending physician review queue. When the assigned provider accessed the inbox, the results were no longer available to review.

Resolution

When physician group processing is disabled for a facility and provider groups are defined at the employee level, provider group-reviewed results are no longer removed from the assigned provider queue. Instead, they are removed from the general review queue leaving results available for the attending provider to review.




851501 Summary

An error occurred during the creation of a Consolidated Clinical Document Architecture (C-CDA) Visit Summary document.

Symptoms

Providers were unable to create a visit summary in the Document List application and received subscript errors when refreshing document creation.

Cause

This issue occurred when the documentation for the patient exceeded 260 characters for any particular field of the visit summary.

Resolution

Subscripts are now limited to 210 characters to avoid the max length of subscript error.

849783 841891 854294

Summary

Memory errors occurred when creating new C-CDA documents.

Symptoms

An Out of Memory error displayed when the user attempted to create new C-CDA documents. This problem usually occurred after the user had created multiple new C-CDAs in the same QCPR session.

Cause

This issue was caused by high memory usage during the document creation process and from the duration of the application window opened by the user.

Resolution

The memory used for each generated document has been reduced and memory now becomes free once the user closes the application window.

852115 Summary

The face sheet displayed all providers in fields created from the Registration Screen Sequence Table, ^rt(“rs”), Patient Care Providers data element instead of the single provider type linked to the face sheet.

Symptoms

When the Registration Screen Sequence Table, ^rt(“rs”), Patient Care Providers data element, Face Sheet Constants field was defined with a Face Sheet Data Element Option defined to display only a certain provider type, the Face Sheet Data Element Option would display the provider type but not clear any other patient assigned provider types. When the user reviewed the Face Sheet field, the linked Face Sheet Data Element Option would display all patient assigned providers instead of the provider linked to the Face Sheet field. Face Sheet data elements are defined in the Face Sheet Table, ^nt(“fs”).

Cause

The Registration Screen Sequence Table, ^rt(“rs”), Patient Care Providers data element can be defined with more than one care provider and Face Sheet Table, ^nt(“fs”), data elements can be linked with more than one provider. The Face Sheet data element that was linked was not honoring the care provider types related to that particular field.

Resolution

The System now stores the associated provider type only. Data documented using the Patient Care Providers data element with defined face sheet storage now displays correctly in the Order Entry Profile Table, ^nt(“op”), and Result Entry Profile Table, ^nt(“rp”), Display Only (Face Sheet) data elements, Face Sheet screen sequences, order/result review screens, bedside screen displays, and information desk screen sequences.




832216 Summary

Blank lines displayed on the IV Summary in the IV Administration menu function in the Clinical Desktop Application (CDA).

Symptoms

Blank lines displayed on the IV Summary in IV Administration menu function in CDA only. (Ultiview displayed the information properly.) The missing information displayed in the Modify Active Orders menu function.

Cause

When too many events existed, the maximum node length was exceeded.

Resolution

In the IV Administration menu function, when exceeding 10 events, an ellipsis displays at the end to represent more events are available to view.


Face Sheet Table, ^nt(“fs”), screens must be rebuilt with this update.

The 6.0 AF Loop 68 – populate ntce non-facility specific and ntice assessment allergy and symptom constants needs to be run with this update:

The 6.0 AF Loop 69 rebuilds all user-defined screen drivers that contain a literal $c(0) character and needs to be run with this update. The loop itself should run in only a couple of minutes, but the loop queues up the following individual jobs to rebuild the affected screen drivers:

assessment.U/QCPR.68 - Rebuild - Assessment Screen Table, ^nt("as")

assessment multiple fields.U/QCPR.24 - Rebuild - Assessment Screen Table, ^nt("as")

order entry.U/QCPR.95 - Rebuild - Order Entry Profile Table, ^nt("op")

result entry.U/QCPR.126 - Rebuild - Result Entry Profile Table, ^nt("rp")

result entry multiple fields.U/QCPR.19 - Rebuild - Result Entry Profile Table, ^nt("rp")






EHN 833655

This enhancement assists in preventing the Provider Inbox Across Patients application from freezing when a display limit is reached. The new System Parameter Table, ^%z, Reg/ADT System Parameters subfile, System-specific level, Miscellaneous Parameters screen, Physician Parameters field, Inbox Item Initial Load Count subfield defines the number of physician review queue items that can display in the Provider Inbox Across Patients application. Once that limit is reached, the System displays a message informing the user of the limit and prompts whether to continue loading items in the inbox.

The Clinical Desktop Application (CDA) will continue to allow items from a single visit to be loaded, even if that visit exceeds the number defined in this subfield. So although the System will continue to load items, only the number of items defined in this subfield will display to the user.

The message consists of the following information:

Number of items loaded - The number defined in the Inbox Item Initial Load Count subfield.

Visit count - Number of visits that contain the initial load of physician review queue items to be displayed in the Provider Inbox Across Patients application.

Total visit count - Total number of remaining visits that contain physician review queue items to be displayed in the Provider Inbox Across Patients application.

For example, the System can display the following message: 13256 items have loaded from the 4 most recent visits. Continue loading from the remaining 22 visits?

The message prompts the user to click Yes or No:

Yes – Indicates the System continues to load the remaining physician review queue items. Continuing to load may cause the System to freeze and cause the CDA to become inaccessible.

No – Indicates the System stops loading physician review queue items and allow processing. The message defaults to no. Exiting the message window without selecting yes or no is interpreted as clicking no. Clicking no also displays the following message in bold, red font:

Additional Inbox items are available for loading. Refresh or Update List to display additional items.

NOTE: Only a refresh of the Provider Inbox Across Patients application by clicking the Refresh icon (as opposed to exiting the application or using another method to re-display the screen), will load physician review queue items.

847973

Summary

Watch list items did not display when patients had multiple provider assignments.

Symptoms

When multiple Residents were linked to a patient in the Provider Assignment Editor menu function, the second residents’ watch list items defined in the Order Entry application, Facility Parameters, Scheduled Procedure Watch List field did not display during order entry.

Cause

QCPR uses a display routine that formats the physicians for a particular patient/visit. When multiple physicians have the same type, the type displays for the first physician. However, the display for the subsequent physicians include only spaces in the same amount of characters as the type of the first physician. The watch list items then did not display appropriately.

Resolution

The display is now updated to replace the blank space with the respective provider type defined in the Provider Assignment Editor menu function.




844358

Summary

The System schedules events after the Surgery Discontinue menu function is used to discontinue orders.

Symptoms

IV Hang events were scheduled even after a patient's orders were all discontinued in the Surgery Discontinue menu function. A procedure can be discontinued using the Surgery Discontinue menu function when the procedure has the Procedure Table, ^t, DC/ASO Information screen, Surgery DC field defined as DC.

Cause

Upon discontinuing the procedure in order entry, there was a screen driver that collected DC information from the user and the appropriate DC time entered by the user was stored in the order. When the user performed an IV hang during IV administration processing, the System appropriately displayed the predicted action as “down/discontinue” as the DC time in the procedure was taken from information entered by the user on DC screen driver.

However, when using the Surgery Discontinue menu function, there is no screen driver for the user to enter DC information so the System uses the DC time from the definition of the Procedure Table ^t , DC/ASO Information screen, ASO Definition field, ASO Time subfield. This caused the System to schedule all the new events upon the IV hang, as the System interpreted the DC time to be in the future.

Resolution

The order definition has been corrected to properly reflect the order DC Time of now based on the surgery discontinue. Performing an IV hang on the order changes the Predicted Action to Check, the status displays as Down/Discontinue, and no further events are scheduled in the IVAR.

851447

Summary

Events were not routing to the physician’s inbox as appropriate.

Symptoms

Events/procedures that where defined in the Procedure Table ^t, Result Review Information screen to route to a physician’s inbox were not routing to the physicians inbox as they should.

Cause

There were two issues found when utilizing either of the following menu functions:

Result Entry (Multiple Events)

Result Verification An issue occurred in the logic for routing shared result events. When a user made changes to a result, the System tracked the specific fields changed. When the user changed some of the fields and proceeded to the next screen, but later returned to the result profile, the System lost track of what fields were changed.

There was also an issue in the Result Entry (Equiv Results) menu function regarding physician queue routing when the Procedure Table ^t, Result Review Information screen was defined to suppress partial results and not route them to the physicians inbox in a partial status.

When the result was first documented as partial, the event, as expected, was not routed to the physician’s inbox. However, when the user returned to document the result as complete but did not make any changes to the event, the documented result failed to route to the physician's inbox.

Resolution

The Procedure Table, ^t, Chart Review Information screen, Result Suppression field was modified to correctly route events to the appropriate provider queue.




851618

Summary

Unknown allergies were not sent to DrFirst.

Symptoms

When a medication allergy was documented and the reaction type, symptom(s) and severity were unknown, it was not sent out by QCPR to DrFirst in the eRx interface. This occurred when previously documented fields had been created from Assessment Category/Data Element Table, ^nt(“ac”), data elements that had been inactivated.

Cause

For ePrescribing, patient allergies are transmitted to DrFirst using face sheet links. The allergy links are defined in the System Parameter Table, ^%z, Order Comm System Parameters subfile, System-specific level, Pharmacy Parameters screen, Drug Allergy Assessment Link(s) field.

The System attempts to find the assessment category/data element that was used to document the allergy data. This is required in order to provide additional meaning to the data, which is done through the Concept Mapping Tool application.

When multiple assessment category/data elements are linked to the same face sheet category, and an allergy previously documented using a data element from the Assessment Category/Data Element Table, ^nt(“ac”), is canceled, the System ignored the cancellation and interpreted it as a duplicate.

Resolution

QCPR now sends each documented allergy regardless of its inactivity status.

852772

Summary


Symptoms

When users attempted to open in the Order Entry application, a subfolder defined in the Procedure Selection Tree Table, ^nt(“ps”), the folders would not expand to allow access to them.

Cause

The System did not add procedure selection trees to subfolder(s) when Customer Table, ^afc, module links were not defined appropriately.

Procedure selection trees are available from two tables:



Procedure selection tree order sets from the Evidence Based Order Set Table, ^nt(“oset”), require the module link in the Customer Table, ^afc. Procedure selection trees from the Procedure Selection Tree Table, ^nt(“ps”), should not require the module link.

Resolution





852874

Summary

The Clinical Desktop Application (CDA) would occasionally freeze when a user selected a “Reason for Orders” during order entry.

Symptoms

The CDA would sometimes freeze when a user was either trying to enter prescriptions and orders, or when selecting “Reason for Orders” to select the patient’s problem.

Cause

The issue occurred when a very generic ICD-9 code was crossed-walked to hundreds of ICD-10 codes in a patient‘s problem record. This issue caused the problem record to become well over 32kB in size. The communications between the CDA and the Caché server erred due to the maximum length string, so only part of the long string was sent to the CDA. When this occurred, the CDA waited for the rest of the string, which was never sent.

Resolution

QCPR now uses the maximum string length to transmit all the data in a large record between the CDA and the Caché server.

853446

Summary

User's screen freezes when accessing the Provider Inbox Across Patients.

Symptoms

When a user attempted to access the Provider Inbox Across Patients application from the Clinical Desktop Application (CDA), the Inbox would begin to load and the loading bar would display as if loading was occurring.

However, the loading bar would continue to display but never open. If the user attempted to close the application, the screen would freeze.

Cause

An issue occurred when the System was loading additional data for inbox items. Instead of displaying the referring physician's name defined in the Employee/Provider Table, ^ae, Employee-specific level, Employee Name field, the System attempted to load a non-existent kardex group, resulting in the error message:

A subscript has an illegal value or a global reference is too long

Resolution

Modifications have been made to use the employee code from the Employee/Provider Table, ^ae, when an employee code is entered by free text in an order block event.









853249 Summary

The Transfer in Background Update for Visit job does not complete & creates visit locks for the user.

Symptoms

Users could not access a patient visit when the Transfer in Background Update for Visit job, generated when a patient is transferred, was not complete in the Queue Display menu function, for background jobs.

Cause

There was an infinite loop in the update default schedule algorithm run by the Transfer in Background Update for Visit job that updates all orders and events for the schedule times, as specified in the Order Schedule Table, ^nt(“os”).

Resolution

The loop that updates the Order Schedule Table, ^nt(“os”), for Daily periods now calculates the new time forward into the next day.

ENH

In the Electronic Clinical Quality Measures (eCQM) debug log or within a Consolidated Clinical Document Architecture (C-CDA) document, the surgery start date/time showed the date/time of the Surgery procedure documentation.

For Quality Measures evaluating Surgical Procedures, qualifying patients were failing to make the Initial Patient Population (IPP).

QCPR was using the Archive Event Date/Time for evaluating the procedure and comparing it to the start and end date/time of the visit. When procedures were documented after the visit was discharged, the procedures failed to be evaluated as occurring in the visit.

An enhancement has been made for documented surgical procedures to use the Start Date/Time of the procedure instead of the date/time of the documented event. The Result Entry Profile Table, ^nt(“rp”), Date/Time data element needs to be mapped to SNOMED Code 398201009 using the Concept Mapping Tool application for this data element to be properly evaluated for Clinical Quality Measures. This enhancement also allows the start date/time of the procedure to be properly reflected in the Continuity of Care Document created from the Document List application.




847094 Summary

Electronic Clinical Quality Measures (eCQM) evaluation within the Clinical Quality Measures Run menu function did not recognize the Onset Date/Time of a problem when the problem was added after discharge.

Symptoms

When the Clinical Quality Measures Run menu function evaluated the problem start date/time for a problem related to a visit, visits were not passing the quality measure when the problem was added after discharge.

Cause

QCPR only used the date and time the problem was filed (archive date and time) when evaluating the problem for the quality measure.

Resolution

The following logic is now used for evaluating Problem Start Date/Time in the Clinical Quality Measures Run menu function.

- Check Problem Onset date against problem archive date - If they are the same date, use problem archive date and time Else - Check problem onset date against visit start date or transfer to non-ED location - If they are the same date, use visit admit date + 1 minute Else - Use problem onset date and 0000 as time

838871 Summary

Users need the ability to report two of the same synoptic checklists on a surgery.

Symptoms

Once a synoptic checklist is selected and documented, it is greyed out in the list of checklists that are available to be selected.

Cause

The field created from the Result Entry Profile Table, ^nt(“rp”), Documentation Form data element only allowed a synoptic checklist to be documented once per procedure.

Resolution

The Result Entry Profile Table, ^nt(“rp”), Documentation Form data element has been modified. When the Allow multiple forms Constants field is defined as yes, the same form is available for selection even when it has been previously documented.




852456 Summary

When the Interactive Care Grid (ICG) application is accessed on a Clinical Desktop tab, the CDA session would freeze when the row name in the Interactive Care Grid Table, ^nt(“vgr”), Row Name field was configured with a number in conjunction with backslash characters and quotation marks. Rows defined in the Interactive Care Grid Table, ^nt(“vgr”) are linked to the Interactive Care Grid (ICG) application.

Symptoms

Freezing of the CDA session after accessing the Clinical Desktop tab containing the Interactive Care Grid (ICG) application forced the user to use Windows Task Manager to end the CDA process and the user would then have to log back in to CDA.

Cause

The issue was found to be a problem with the ICG row name as it contained a number in conjunction with the quote and backslash characters (e.g. “/1/”). This combination of number and symbols together has special meaning to the CDA code and caused the session to freeze/hang.

Resolution

The System has been updated to interpret these characters differently when in a naming convention of an ICG row.









851277 Summary

The QCPR Clinical Quality Measures Run menu function was unable to produce any results for ED Stratum 3 for clinical quality measures.

Symptoms

The QCPR Clinical Quality Measures Run menu function was not recognizing any patient visits for Stratum 3 of the ED clinical quality measures (ED-1, ED-2, ED-3).

Cause

When a patient is transferred to another facility, the Visit Type Table, ^rt(“vt”), Transfer discharge type is documented on the Discharge procedure. This caused the Transfer To Quality Measure data element and the ED encounter to have the same start and stop times. The QCPR Clinical Quality Measures Run menu logic was not recognizing the ED visit because the measure requires the transfer to occur after the ED visit ends.

Resolution

When a Visit Type Table, ^rt(“vt”), Discharge Type is mapped to the Transfer To marker in the Clinical Concept Layer application, one extra event will be created for the Transfer To Quality Measure data element which will default the event time as the Discharge procedure event time + 1 minute.

850491

Summary

When a patient was transferred, orders with a default schedule would schedule extra events.

Symptoms

Extra events would be scheduled when a patient was transferred to a new location with default schedule defined for the location in the Order Schedule Table, ^nt(“os”).

Cause

When a patient is transferred, any orders with a default schedule (i.e., using a location-specific schedule defined in the Order Schedule Table, ^nt(“os”), would have their events rescheduled using the new location’s default schedule. There is an algorithm that attempts to make sure that the right number of events gets rescheduled for the day in which the transfer occurred. For example, if an order was written with a frequency of q4h x5, then a default schedule would be applied. During a transfer, the new location’s default schedule can’t simply be substituted for the previous schedule, as this may cause an extra event to be scheduled or an event to be dropped because of the way that the starting point for the frequency is calculated and the way the schedules overlap. If one of the previous parent events has been documented or cancelled, the algorithm did not always update the pointer and caused extra events to be scheduled.

Resolution

The algorithm has been improved to update events when a patient is transferred to a new location.




ENH

In result entry, when an allowed additional procedure(s) is added at the time of result entry, a link between the allowed additional procedure and the original order can now be created and is available in order review. This is available in the following menu functions:

Result Entry (Equiv Results w/Selection)

Result Entry (Equiv Results)

Result Entry (Specimen First)

Previously, the linkage between the allowed additional procedure and the associated order was not available, making reporting such information impossible.

With this enhancement, the Procedure Table, ^t, Specimen Information Screen, Allowable Additional Procedure(s) field has been enhanced with the following new options when defining an allowed additional procedure:

(L) always link – Indicates the System automatically creates a link between the allowed additional procedure and the original order without user intervention.

(N) never link – Indicates the System does not create the link between the allowed additional procedure and the original order. This is existing functionality.

849565 Summary

The Product Table, ^pt(“p”) or the Product Category Table, ^pt(”pc”), contains blank records when searching within the tables.

Symptoms

When searching in either the Product Table, ^pt(“p”) or the Product Category Table, ^pt(”pc”), and performing a wildcard search with a dash, the search would return a list of blank records.

Cause

The deletion of a category in the Product Category Table, ^pt(”pc”), was not clearing its pointer in the Product Table, ^pt(“p”). This caused empty entries or blank records.

Resolution

The 6.0 af loop, Clean Product and Product Category Invalid records has been created and will clear the Product Table, ^pt(“p”), and Product Category Table,

^pt(”pc”), tables invalid records. This loop needs to be run as a pre-live loop during the update process when users are not in the system.




There are no screens to be rebuilt with this update.

The 6.0 AF Loop 67 – Clean Product and Product Category Invalid records needs to be run with this update:

The following reports need to be rebuilt with this update.

gen.pat_audit_sort

gen.pat_lvl_audit

gen.user_lvl_audit

gen.user_lvl_audit_in

gencore.cf.cartsd






837602 Summary

The Interactive Care Grid (ICG) application only displayed three digits instead of four digits for newborn weights.

Symptoms.

The measuring units for newborn weights with “0’s” in the thousandths place (i.e.”0.000”) did not display in Interactive Care Grid (ICG) application. When a newborn’s daily weight is documented and the weight is displaying in kg, the weight was only displaying three digits instead of four when viewing the ICG. Weights displayed correctly everywhere else within the System.

Cause

The algorithm for result values was not properly checking and identifying the correct decimal format.

Resolution

The algorithm for result values now appropriately checks and displays the measurement according to its decimal format in the Interactive Care Grid (ICG) application.




847943 Summary

While defining reports in the Site-Specific Autostart Job Table, ^%zbgj or in the Desktop Application Table,ât(“dta”) , the System did not consider date ranges that spanned multiple years.

Symptoms Reports defined in the Site-Specific Autostart Job Table, ^%zbgj, or in the Desktop Application Table,ât(“dta”) did not correctly interpret values entered in the Start Date and Stop Date report screen driver fields and did not allow dates for the next year to be defined. However, reports could still be run manually without errors in the Hierarchical Filing System menu function.

Cause

The dates were interpreted as a programming format in Site-Specific Autostart Job Table, ^%zbgj or in the Desktop Application Table,ât(“dta”), by the month and day without considering the year.

Resolution

The System now correctly interprets date ranges that span multiple years when defining reports in Site-Specific Autostart Job Table, ^%zbgj or in Desktop Application Table,ât(“dta”), using set up mode (using pre-defined parameters).

However, configuration is needed when setting up reports to be run automatically using set up mode. The Data Element Dependency (DED) in the Start Date and Stop Date fields in the report screen driver needs to be modified to include hook.setup_mode? as shown in the screen below.

For modification of GEN reports, please create a Support case with specific reports that need to be modified.

For non-GEN reports, please work with the report author to add these screen driver Data Element Dependency (DED) modifications.




849741 Summary

An error occurred when exporting concepts in the Concept Mapping Tool application.

Symptoms

The error: Last export failed, with error of... ERROR #5521:SQLError occurred when exporting concepts in the Concept Mapping Tool application.

Cause

The length of the concepts name was greater than 1024 characters due to leading spaces.

Resolution

The leading spaces of the concept name have been removed when performing an export of concepts in the Concept Mapping Tool application.

850408 Summary

The Terminate All Foreground Jobs processing option in the Auto Rollover Load Utility menu function was not working during the System shutdown to IPL Level 2 stage of a Database Rollover.

Symptoms

The Terminate All Foreground Jobs processing option did not successfully terminate all sessions during the System shutdown to IPL Level 2 stage of a Database Rollover in the Auto Rollover Load Utility menu function. It also did not prevent users from logging back on. This was evident because users were able to create orders during the downtime.

Cause

The Clinical Desktop Application (CDA) sessions were not being halted when terminated during a rollover when the Terminate All Foreground Jobs processing option was used.

Resolution

All Clinical Desktop Application (CDA) instances are now halted during a rollover and with all other termination commands.


The following AF Loops need to be run for this update:

6.0 AF Loop 18 – Rebuild (arf) report screen drivers

6.0 AF loop 65 – Clean Product and Product Category Invalid records






ENH QCPR now manages patient transfers more efficiently to avoid deadly embrace occurrences.

ENH

The new Review Item Close Visit Status field has been added to the System Parameter Table, ^%z, Reg/ADT System Parameters subfile, Facility-specific level, Physician Data Screen to enable client sites to define whether visits can close when outstanding review items exist in a physician review queue.

Also, the Midnight visit and order update job has been updated to search for physician review items.

850637 Summary

Ordering a procedure generated the Global subscript length error in the error log.

Symptoms

Users received a Global subscript length error when trying to order a procedure with multiple associated procedures. The order did not file.

Cause

An issue occurred with the program that schedules orders for a procedure with multiple associated procedures.

Resolution

The System now appropriately schedules orders for procedures with multiple associated procedures.

849753

Summary

Result profiles that have built successfully in the past were generating errors during a screen rebuild.

Symptoms

After a new release was installed, result profiles were not rebuilt, resulting in build errors.

Cause

The program building the screens was incorrectly interpreting the result profile data.

Resolution

The 6.1 AF loop 6 Rebuild User Defined Screen Drivers with Modified Dictionaries should be run and result profiles now build without errors.




850952

Summary

Issue occurred with order event scheduling, causing patient information to take a long time to load.

Symptoms

Patient information took a prolonged time to display in the IV Administration (IVAR) tab of the IV Administration menu function.

Cause

The delay in loading time was caused by an order that inadvertently created a large number of events. The order frequency was not a valid IV order rate and the System was not able to convert it properly to mL/min. Instead of scheduling many events, the invalid rate scheduled an event every day for 6945 days. When the documented rate is different than the ordered rate, the System assumes that the documented rate will continue to the end of the bottle and that subsequent bottles will use the ordered rate.

Resolution

The System now performs an additional check for instances when minimal rate is used. Any “stop specification” instances causes the scheduler to stop after the first bottle.

849709 Summary

Users did not see the “Verify SIGN OFF (Y) (N)” prompt when exiting Ultiview.

Symptoms

In Ultiview, the prompt “Verify SIGN OFF (Y) (N)" did not display when the Back Up (F9) key was pressed multiple times to exit. Instead of prompting the user to verify sign off, the System automatically ended the session, bringing the user back to the login screen.

Cause

Previous changes to the audit log functionality removed the “Verify SIGN OFF (Y) (N)" prompt in Ultiview.

Resolution

The System now invokes the “Verify SIGN OFF (Y) (N)" prompt when a user exits Ultiview using the F9 key.

849408

Summary

Incorrect sorting occurred in the Location column of the Patient List application.

Symptoms

In the Patient List application, when the user selected to sort by location, the application did not display the locations in alphabetical order for visits entered prior to QCPR Release 5.4.1 update 52.

Cause

An AF loop was run previously to update the order subscripts in the area global from two digits to four digits, but the subscripts information in the visit global was not updated with that loop.

Resolution

An AF loop now updates the location order subscript information in the visit global structures to match the new updated standard.




838385 845763 844453 846769

Summary

Edits to default product selection for IV medication orders did not apply to the first bag of solution.

Symptoms

An IV medication order has default suggested products edited by Pharmacy before any bags are dispensed to the unit. On the IV administration record (IVAR), the correct products dispensed by pharmacy would display at the order level. However, when the first bag was selected to hang, the default product selected by QCPR displayed for documentation for the first bag. Since the product displayed on screen could not be changed, incorrect products were documented as administered. The Administration History showed the same incorrect products for the first IV solution. IV labels were incorrect and showed the defaulted products either for the initial dose label or when labels were generated as a result of IV Solution Queue processing.

IV medication procedures are procedures with the Procedure Table, ^t, Department Processing screen, Procedure Type field defined as “medication”. Additional configuration is completed in the Procedure Table, ^t, Product Information screen, for IV Definition. When an order for this procedure is placed with a rate, an order for an IV Medication is created.

Cause

QCPR product selection changes are effective at the time the order is processed in the Department Order Review Queue menu function or application. Even though the first bag of solution had not been dispensed or hung, the System did not make the change retroactive to the date/time of the start of the IV order.

Resolution

A new prompt now displays to the user when selecting the Manual Product Selection processing option in the Order Entry menu function and application during drug product selection. The prompt, Affect Past Events, allows users to define whether the product selection is applied to past events. Answering yes to the prompt indicates the product selection changes are applied to all solutions created for the order. This allows the IV Administration menu function, IV Labels, and Administration history to display correct product information.

Selecting no indicates the changes in product selection apply only to the IV bags created after the change in product selection is made.

847655

Summary

Incorrect statistics generated for the Exclusive Breast Milk Feeding measure in the Clinical Quality Measures Run menu function (eCQM).

Symptoms

When generating the report for the Exclusive Breast Milk Feeding clinical measure, patients were incorrectly included in the exception category.

Cause

When two administered substances were documented on the same result profile, the first administered substance negation indicator was overwritten by the second administered substance negation field. As a result, the System did not find any administered substance documented as “not done”.

Resolution

When calculating the measure statistics, the System now adds a temporary notation to both substances to keep the values unique. When the calculation data is later written to permanent storage, the notation is removed.




850697

Summary

Result profiles that had built successfully in the past generated errors during a screen rebuild.

Symptoms

After a new release was installed, result profiles had to be rebuilt. This generated many build errors.

Cause

The program building the screens was incorrectly interpreting the result profile data.

Resolution

This issue is resolved. Result profiles now build without errors.

851239 Summary

Dispensable Drug Identifier (DDID) for historical products could not be edited in a predefined typical order.

Symptoms

Predefined default order definitions can be defined in many places in the System, including typical orders and the Procedure Selection Tree Table, ^nt(“ps”). As part of this definition, a product can be linked into a Product data element on the order profile. Products with a historical DDID were rejected by Dr. First. However, the System did not allow users to change the product field on the order profile. Instead, users had to redefine the order again and choose a product with another DDID. The same issue occurred when trying to rebuild the typical orders in the Procedure Selection Tree Table, ^nt(“ps”).

Cause

With Medi-Span API implementation, drug information links directly from the Medi-Span database and the System stores the product link as a DDID. When the user attempts to redefine the product link, the error Error: historical DDID displayed and prevented the user from linking in a product.

Resolution

The System now warns the user that the current default DDID is historical and allows the user to select a new product on the order profile when placing an order.

850770 Summary

The Initial Patient Population (IPP) was incorrectly calculated in the Clinical Quality Measures Run menu function (eCQM).

Symptoms

Patients who were previously included in the IPP were no longer included. When generating a run in the eCQM, the System displayed errors for those patients.

Cause

The prescription discharge medication's start and stop time were not converted to the correct format and thus were excluded.

Resolution

The Clinical Quality Measures Run menu function now correctly recognizes the start and stop times for prescription discharge medications.




850708 Summary

An error occurred when performing a partial name search for an employee in the Staff Scheduling menu function.

Symptoms

When the System prompted the user to enter a partial name search of an employee in the Staff Scheduling menu function, the System displayed the error message Invalid Physician Consultant.

Cause

When selecting an employee from the search results, the System used the selected employee’s external ID number as the identifying number instead of the employee’s internal ID number.

Resolution

The Staff Scheduling menu function now recognizes employee partial search selections when the employee is selected.

847943 807145 850521

Summary

Reports defined as background jobs did not consider date ranges that spanned multiple years.

Symptoms

Reports defined in the Site-Specific Autostart Job Table, ^%zbgj, did not correctly interpret values entered in the Start/Stop Date screen driver fields and did not allow dates for the coming year to be defined.

Cause

The dates were interpreted as a programming format in certain areas of the System by the month and day without considering the years.

Resolution

The System now correctly interprets date ranges that span multiple years.

824001

Summary

Field created from the Result Entry Profile Table, ^nt(“rp”), Employee (Single Selection) data element did not retain user documentation.

Symptoms

When documenting an adult primary care progress note, the provider’s name populated into the appropriate field created from the Result Entry Profile Table, ^nt(“rp”), Employee (Single Selection) data element. However, when the note was completed, the provider was prompted to re-enter their name in the provider field.

Cause

The issue was caused by the inversion used to identify the user. The inversion did not exclude special characters such as “-” or “.”, which removed the provider’s name from the field.

Resolution

The inversion has been updated to remove any special characters within the employee name.




847463

Summary

Lab collection labels printed out of sequence.

Symptoms

Room numbers on inpatient phlebotomy labels did not print in defined reverse hierarchical order from high to low. Instead, they printed out of sequence.

Cause

An AF loop was previously run to update the order subscripts in the area global from two digits to four digits. However, the subscripts information in the visit global was not updated with the same loop.

Resolution

This is resolved with QCPR Release 6.0.1 AF loop #64 "Update visit record sub/sub-sub area location order subscript”, which updates the information in the visit global.

847363

Summary

Generated output in the Clinical Quality Measures Run menu function (eCQM) was not consistent with QRDA report statistics for the same measures.

Symptoms

The percentages displayed in the Performance Rate column of the Clinical Quality Measures Run menu function (eCQM) were not consistent with the performance rate calculated in the Quality Reporting Document Architecture (QRDA III) summary report. The numbers for the denominator, exclusions, expectations, and numerators were the same on both reports; however, some of the actual percentage breakdowns differed.

Cause

An error in the program caused this mismatch and resulted in the difference in actual count between the Clinical Quality Measures Run menu function (eCQM) and the Quality Reporting Document Architecture (QRDA III) report.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated to resolve the mismatch.



6.0 AF loop 13 – Rebuild all order profiles






827721 Summary

Checksum error occurred when scanning IV Solution barcode labels.

Symptoms

Users would receive a "Checksum error" when scanning IV Solution Barcode labels in the Prep Queue, Check Queue, and Release Queue menu functions when the push parameter for "Scanable?" was defined as "Scan Only". This checksum error would only occur when the calculated checksum digit was a blank space. Closing the menu function and re-launching it allowed the same barcode label to be scanned successfully.

Cause

When a Solution Barcode label was successfully scanned and the identified solution was presented, the solution that displayed was a list function even though only one IV solution was presented. Whenever a list appeared before a barcode scan, QCPR was removing the blank space.

Resolution

Scanning of Solution ID Barcode Label in Prep Queue, Check Queue, and Release Queue menu functions where the parameter "Scanable?" is defined as "Scan Only" will now be successful when the checksum digit is a blank space regardless of display previous to scanning the barcode.

841941

Summary

The ability to redact patient information was not available in the Document List application when creating a CCDA document.

Symptoms

When the user created a new document in the Document List application, the user was not able to redact information entries by right-clicking on the entry in the Vital Signs or Social History sections.

Cause

The ability to redact patient information from the right-click menu for the Social History or Vital Signs sections was not previously available in the Document List application.

Resolution

The Document List application now allows the user to redact patient information when right-clicking entries in the Social History and Vital Signs sections of CCDA documents.




848340

Summary

Device timeouts occurred while actively working in Microsoft Word within the Clinical Desktop Application (CDA).

Symptoms

When the user documented a field created from Word Processing data element types on any screen driver within the CDA, an inactivity alert window displayed if the user exceeded the time-out parameters for the device. If the user did not close the Microsoft Word application window, the device timed out and closed the user’s session even though the user was actively working in the window.

Cause

Microsoft Windows has a native Dynamic Link Library (.dll) file called IdleTime.dll that is included in the installer. It uses a Windows hook to track mouse and keyboard activity. This .dll file detects user activity and does not timeout the CDA session when the user is using any application on the workstation. This .dll file was missing when CDA was installed for some versions of Windows.

Resolution

The .dll file is now included in all versions of the Clinical Desktop Application installer.

849242

Summary

PRN orders with “start at” in the future, display in the in the Medication/IV Administration menu function (eMAR) Scheduled Orders

Symptoms

PRN orders with “start at” time defined in the future, display in the ‘scheduled orders’ section in the in the Medication/IV Administration menu function.

Cause

If no events at all were encountered in the main algorithm because of a future ‘Start At’ time, it caused the order to go to the “Scheduled Orders” section instead of the “PRN Section”

Resolution

PRN orders with future start time now display under “PRN orders” section in the Medication/IV Administration menu function.

849685

Summary

The Specimen Collection menu function allowed the input of a specimen number beyond the defined range of downtime specimen numbers.

Symptoms

During downtime, the user manually reset the specimen/accession numbers by entering a 12-digit arbitrary number into the Specimen Collection menu function. The specimen numbers incremented according to the new sequence.

Cause

During downtime, when the user manually reset the specimen/accession numbers, the Specimen Collection menu function did not validate that the number was within the range of acceptable specimen numbers.

Resolution

The Specimen Collection menu function has been updated to validate any manually entered specimen/accession number within the defined range of downtime specimen numbers. If an entry is not within the range, a message now displays Specimen Number out of range.




849711

Summary

Error of "Address is not valid" received when executing an HTML (Hyper Text Markup Language) report to a web browser when it is launched from the Object Desktop via the Patient List application.

Symptoms

When trying to execute an HTML report via the Patient List application, the user received an error stating that the "Address is not valid". However, when the same ARF report was accessed through a Patient Search, the web address content could be displayed. The application having an issue is a Generic Web Application that has a Desktop Application Class of Web Application Launch.

Cause

The data returned from the Patient List application was a different format than the data returned from a Patient Search. This resulted in an extra piece of information from Patient List application being passed causing the Generic Web Application to fail to launch.

Resolution

The Clinical Desktop Application (CDA) was modified to correct this issue.

850017

Summary

Outbound prescription order messages sent to DrFirst were delayed when new physicians were being registered for ePrescribing.

Symptoms

Outbound prescription order messages were delayed, causing other outbound physician registration messages using the ePrescribing interface to be sent first.

Cause

ePrescribing can take up to 30 minutes to file the physician addition messages when checking common names. As a result, this delayed any prescription order messages sent.

Resolution

The ePrescribing interface has been updated to use two separate outbound interfaces. One interface sends physician registration messages while the other sends prescription messages. Changes to the ePrescribing interface must be contracted through QuadraMed Professional Services.

850175 Summary

A language syntax error generated (on the screen) when attempting to generate any Audit Log report from the Audit Record Administration menu function

Symptoms

When attempting to print the GEN - Patient Level Audit report from the Audit Record Administration menu function, an error that said, “Right edge of field is beyond window width!” would display on a dialog box. The report would not print. In addition, when attempting to regenerate the report an error would display that said, “Data dictionary field does not exist!”

Cause

The Report Formatter Data Dictionary (^arfd) had a syntax issue in the “audit log” data record.

Resolution

The syntax issue has been resolved. The GEN - Patient Level Audit report must be rebuilt for changes to take effect.




848229,

848238 Summary

The Clinical Quality Measures Run menu function (eCQM), reports were not correctly considering the Emergency Patient discharge date/time that was mapped the Concept Mapping Tool application.

Symptoms

The eCQM report for Median Admit Decision Time to ED Departure Time for Admitted Patients (ED2 measure) and Thrombolytic Therapy (Stroke 4) seemed to be using the patient transfer time as the emergency patient discharge time instead of looking at the emergency patient discharge time shown in the Clinical Quality Measures Run menu function (eCQM).

Cause

The Clinical Quality Measures Run menu function (eCQM) was not properly recognizing the third-party Emergency Patient Transfer date/time mapped in the Concept Mapping Tool application.

Resolution

The code has been changed to properly consider 3rd party transfer procedure events. Also, the code was changed to use the Transfer marker mapped at the Date/Time data element level instead of mapping the Transfer marker at the top level of result profile.









844717 Summary

Errors occurred in the Media Manager after the Clinical Desktop Application (CDA) was installed using the .MSI installer.

Symptoms

After upgrading CDA using the .MSI installer, an error occurred in the Media Manager. When the user attempted to review or import data using a field created from any of the following data elements, the data was not displayed or imported:

Registration Screen Sequence Table, ^rt("rs"), Generic Multimedia data element

Visit Type Table, ^rt("vt'), Generic Multimedia data element

Order Entry Profile Table, ^nt("op"), Multimedia data element

Result Entry Profile Table, ^nt("rp"), Multimedia data element

CDA displayed the error message, Failed to launch client, when the fields were accessed.

Cause

When CDA was installed, the QUADRAMED CPR.LAX file was not created with the required definitions for the Media Manager server ports and connections, disallowing communication with the multimedia server. The .MSI installer did not update the installation path when creating the QUADRMED CPR.LAX file.

Resolution

The CDA .MSI installer has been updated to generate Media Manager server connection information and default installation path.

844542 Summary

Page breaks occurred incorrectly on the printed GEN – HTML Patient Medication Discharge Instructions Report (rev3.1) report.

Symptoms

When the Medication Reconciliation report was printed, page breaks occurred in the middle of medications.

Cause

When a result profile contained the Result Entry Profile Table, ^nt(“rp”), Multimedia data element, and the HTML Report(s) Constants field was defined with the GEN - HTML Patient Medication Discharge Instruction Report (rev3), the data displayed for a medication was printed at a page break. The report used a (CSS) stylesheet that allowed table columns within the HTML report to break across a page.

Resolution

The (CSS) stylesheet used by the report has been updated to prevent rows from breaking across a page.

The GEN – HTML Patient Medication Discharge Instructions Report (rev3.1) must be rebuilt once the update has been applied. Any customized versions of this report should be edited to include these changes.




847125

849926

850013

Summary

Users were able to log on to multiple devices in Ultiview even when the Employee/Provider Table, âe, Employee-specific level, Allow Multiple Connections? field and the System Parameter Table, ^%z, Utility Parameters subfile, System-specific level, Logon Parameters screen, Multiple Connections Default field were both defined as no.

Symptoms

Users were able to log on to multiple devices in Ultiview even though configurations in the Employee/Provider Table, âe, and the System Parameter Table, ^%z, did not allow for multiple connections. At other times, users were unable to log into multiple sessions, even though the Employee/Provider Table, âe, Employee-specific level, Allow Multiple Connections? field was defined as yes.

Cause

User logins were being incorrectly evaluated against the configuration in the Employee/Provider Table, âe. An additional issue was identified where user logins were not being reset at the system level when a new login was attempted.

Resolution

Logins now correctly evaluate the user’s configuration settings in the Employee/Provider Table, âe, Employee-specific level, Allow Multiple Connections? field and allow or disallow multiple sessions based on that definition.

847501 Summary

Events with a status of review hold changed to a status of review after check-in or transfer to another area.

Symptoms

When an order was placed in a status of review hold in the Department Order Review Queue application and the patient was checked in to a bed or transferred to a new area using a transfer procedure, the order event status changed to display a status of review within the Chart Review and Patient Schedule menu functions. However, when the order was viewed in the Department Order Review Queue application, it still displayed a status of review hold.

Cause

The issue occurred when transferring a patient to a new location. When a transfer procedure is processed, any orders are re-created in the new area using the defined parameters for that area. When an order was placed in a status of review hold in the Department Order Review Queue application, the status did not remain defined when the order was re-created by the System in the new area and therefore displayed a status of review.

Resolution

The transfer procedure and Department Order Review Queue application have been updated to maintain statuses when a transfer occurs.









807942 Summary

When the user looked up an employee in the Staff Scheduling menu function using an employee external number, the System displayed the error No option currently defined.

Symptoms

When the Staff Scheduling menu function is accessed, the System prompts the user to select an employee to edit or to add an employee by entering the Employee ID. If an Employee ID (employee external number) was entered, the error No Option Currently Defined displayed.

Employee external numbers are defined in the Employee External Number Type Table, âet(“en”), and defined for individual employees in the Employer/Provider Table, âe, Facility-specific level, Employee Number(s) field.

When searching for an employee using an external employee number, the user must enter the prefix, followed by the number. The prefix is defined in the Employee External Number Type Table, âet(“en”), External Number Type Options level, Prefix field.

Cause

The search functionality in the Staff Scheduling menu function did not recognize the employee external number.

Resolution

The Staff Scheduling menu function now recognizes employee external number types when the number is preceded by the employee external number type prefix in the search dialogue.

847125 Summary

Users were able to log on to multiple devices in Ultiview even when the Employee/Provider Table, âe, Employee-specific level, Allow Multiple Connections? field and the System Parameter Table, ^%z, Utility Parameters subfile, System-specific level, Logon Parameters screen, Multiple Connections Default field were both defined as no.

Symptoms

Users were able to log on to multiple devices in Ultiview even though configurations in the Employee/Provider Table, âe, and the System Parameter Table, ^%z, did not allow for multiple connections. At other times, users were unable to log into multiple sessions, even though the Employee/Provider Table, âe, Employee-specific level, Allow Multiple Connections? field was defined as yes.

Cause

User logins were being incorrectly evaluated against the configuration in the Employee/Provider Table, âe.

Resolution

Logins now correctly evaluate the user’s configuration settings in the Employee/Provider Table, âe, Employee-specific level, Allow Multiple Connections? field and allow or disallow multiple sessions based on that definition.




847809 Summary

Discharge medications failed to be correctly evaluated for clinical quality measures when edits were made to the discharge medications after a patient was discharged.

Symptoms

When the Clinical Quality Measures Run menu function (eCQM) was run for measures evaluating discharge medications and an edit occurred for any of the discharge medications for the patient after the patient was discharged, the patient would fail the measure. One example of an edit would be when a product was selected for a previously documented discharge medication.

Cause

When an edit was made to a discharge medication, the System used the Last Edit Date/Time to compare to the Discharge Date/Time. The patient would fail the measure since the Discharge Medication event was after the patient's discharge.

Resolution

When the Last Edit Date/Time for a Discharge Medication is after the patient's Discharge Date/Time, the System now uses the patient's Discharge Date/Time minus 1 minute for the Discharge Medication Date/Time. If the Discharge Medication Date/Time is before the patient's Discharge Date/Time, the System uses the Archive Event Date/Time.

848910 Summary

Users were unable to edit existing Kardex Group options in the Kardex Group File Table, ^nt("kg").

Symptoms

When the user tried to edit an existing Kardex Group option in the Kardex Group File Table, ^nt("kg"), the screen would close and the Kardex Group option could not be edited. When a new Kardex Group option was added to the table, the new entry was accepted.

Cause

The Kardex Group File Table, ^nt("kg"), Kardex Group Short Name field caused an issue in the screen for the existing Kardex Group option.

Resolution

Edits are now accepted without issue for existing Kardex Group options in the Kardex Group File Table, ^nt("kg").







Defects Resolved in 6.0.1 Update 30 NOTE: The following enhancements are applicable only to clients who have purchased the ePrescribing module:


ENH The Include MRN #? and MRN # Interface Label fields have been added to System Parameter Table, ^%z, Order Comm System Parameters screen, Facility-specific level, ePrescribing Parameters screen. The MRN # Interface Label field displays only when the Include MRN #? field is defined as yes (The System defaults to no).

The MRN # Interface Label field must be defined to match the Options, Preference – Location, External ID system name to require for each patient, if any: field within the ePrescribing Portal Launch application,.

When the Include MRN #? field is defined as yes and configured properly, the QCPR Medical Record Number (MRN) displays in the ePrescribing Portal Launch application after the patient’s name.

ENH The ePrescribing receipt now includes the provider’s supervising physician. Resident Physicians and Nurse Practitioners can define their supervising physician within the ePrescribing Portal Launch application. If a supervising physician is defined at the time the prescription is signed and submitted to a retail pharmacy, the supervising physician’s name is captured and displays on the unscheduled procedure defined for ePrescribing Receipt in the Chart Review menu function.

ENH The Order Entry Profile Table, ^nt(“rp”), eRx Disposition data element has been enhanced to default the field value based on the patient’s home location. When the System Parameter Table, ^%z, Order Comm System Parameters screen, Facility-specific level, ePrescribing Parameters screen, Activate ePrescribing? field is defined as yes, the field created from the eRx Disposition data element defaults to send electronically.

When the Activate ePrescribing? field is defined as no, the field created from the eRx Disposition data element defaults to local/handwritten.

The ePrescribing Portal Launch application has also been enhanced to allow provider access based on the patient’s home location instead of the device’s location. For example, if Facility A is active with ePrescribing, and Facility B is inactive, a provider at Facility B can access a patient at Facility A, and sign and submit discharge prescriptions. This is contingent on whether the physician has security to access patients at both Facility A and Facility B.

ENH The ePrescribing Add_User API now allows for an ePrescribing Provider to have their state license number defined as none in the Employee/Provider Table, âe, Facility-specific level, Employee Number(s) field, State License No and Expiration option, as defined in the Employee External Number Type Table, âet(“en”). Resident Providers may not have state license numbers, but are allowed to submit discharge prescriptions electronically.

ENH The GEN – ePrescribing EPCS Registration Download Report has been enhanced to include users with ePrescribing Member Types of Dentist, Physician Assistant and Nurse Practitioner. The ePrescribing Member Type is defined in the Employer/Provider Table, âe, Employee-specific level, ePrescribing Parameters field, ePrescribing Member Type subfield.




808720 Summary

When modifying results in a field created from a multiple field data element in the Result Verification menu function, and one of the values was marked as “internal”, the overall result would display as normal, even when there were values for other fields in the multiple field data element that contained abnormal values.

Symptoms

When the user modified a result and accepted the changes in the Result Verification menu function, the edited result would file with a status of “complete”. This would occur even if abnormal results were defined to be sent back to a result verification queue or a status of “unverified” should have displayed. Result verification routing is defined in the Procedure Table, ^t, Result Review Information screen, Result Verification Routing field, Path Entry(s) subfield, Result Queue and Send Criteria sub-subfields. The definition of these fields determines the routing of results based on the result event and status.

Cause

Marking a value documented in the field created from the multiple field data element as “internal” caused the abnormality flag to be set to normal for all results in the multiple field data element, regardless of abnormality status for each value.

Resolution

When a value in a field created from a multiple field data element is marked as “internal”, the abnormality value is no longer ignored when one of the values documented in the multiple field data element is abnormal.

828946

835698

Summary

Converted IV rates did not display correctly on result profiles throughout the System.

Symptoms

When an IV is ordered with a weight-based or unit-based rate, the System converts that rate to a volume-based rate, such as mL/hr. This converted rate typically displays in parentheses after the ordered rate. This did not occur for events that displayed in the Admin History or Event History processing options of the Result Entry Profile Table, ^nt(“rp”), IV Maintenance data element, Rate display in the procedure's result profile.

Event History or Admin History processing options, both which display the same information, can be found within several menu functions, such as Medication Summary, Chart Review, Patient Schedule, Medication/IV Administration and IV Administration.

Cause

The IVAR did not use the unit rate defined in the System Parameter Table, ^%z, Order Comm System Parameters subfile, System-specific level, Pharmacy Parameters screen, Unit/Rate Definition field, ml/hr unit subfield for weight-based IV unit conversions. The rate correctly calculated and displayed during IV administration.

Resolution

Admin or Event History displays now display converted IV rates in documented events according to the definition of the System Parameter Table, ^%z, Order Comm System Parameters subfile, System-specific level, Pharmacy Parameters screen, Unit/Rate Definition field, ml/hr unit subfield.




838215

845319

Summary

White Board reports either stopped refreshing or would no longer display when refreshing.

Symptoms

When White Board reports were open on a desktop for an extended period of time (greater than 24 hours), the reports would stop refreshing or would no longer display.

White Board reports are defined in the Hierarchical Filing System menu function, HFS Directory/Item push parameter. This issue occurred when the Hierarchical Filing System menu function, Execute Parameters push parameter, Processing Method field was defined as screen display, the Automatically Refresh? field was defined as yes, and the Refresh Rate field was defined with a refresh rate time.

Cause

A memory leak in the CDA code caused the report display refresh to stop displaying after several hours.

Resolution

CDA has been updated to resolve the memory leak when refreshing HTML White Board reports.

841295 Summary

The Clinical Quality Measures Run menu function (eCQM) did not correctly evaluate Emergency Department (ED) departure times when evaluating ED patients that became inpatients.

Symptoms

When running the eCQM for quality measures that evaluated when patients were converted from Emergency Department (ED) to Inpatient, expected patients were not included in the Initial Patient Population (IPP).

Cause

QCPR was using the patient transfer event time to set the non-ED start time instead of the checkin time for the Inpatient visit. Because the ED Discharge Time was the same as the checkin time for Inpatient units, patients were failing the quality measure since the ED encounter was not ending before the start time of the Inpatient encounter.

Resolution

QCPR now evaluates ED departure times for eCQM measures that evaluate when the patient visit was changed from an ED visit to an Inpatient visit by using the Inpatient checkin time and adding one minute to that time.




843946 Summary

Users were unable to see corrected/supplemented Visit Summary documents in the Chart Review menu function.

Symptoms

When a provider updated an already documented Visit Summary document in the Document List application, the updated Visit Summary was not viewable in the Chart Review menu function. Instead, only the originally documented Visit Summary would display.

Cause

When the user corrected/supplemented a clinical document procedure that had already been documented as either “partial” or “complete”, the System was not properly loading the correct result definition.

Resolution

When a previously completed document is edited in the Document List application, the edited document now properly loads and files the updated result, allowing the edited document to display correctly in the Chart Review menu function. 6.0 AF Loop 65 – correct malformed corrected/supplemented Clindoc events must be run with this update to correct previously corrected or supplemented documents.

844358 Summary

The System continued to schedule IV Hang events even after orders were discontinued using the Surgery Discontinue menu function.

Symptoms

IV Hang events were scheduled even after the Surgery Discontinue menu function had been used to discontinue all the orders on a patient. This occurred for procedures defined to discontinue at surgery in the Procedure Table, ^t, DC/ASO Information screen, Surgery DC field.

Cause

When orders are discontinued from the Order Entry menu function or application, a screen driver collects discontinue information from the user and the appropriate discontinue time entered by the user is stored in the order. When the user completes a hang event, the System appropriately displays the predicted action as “down/discontinue” since the discontinue time in the procedure is taken from information entered by user.

However, when an order is discontinued using the Surgery Discontinue menu function, there is no screen driver for the user in which to enter discontinue information, so the System takes the discontinue time from the Procedure Table, ^t, DC/ASO Information screen, ASO Definition field, ASO Time subfield. This caused the System to schedule all the new events after the user completed the hang, since the System considered the discontinue time to be in the future.

Resolution

The order definition has been corrected to properly reflect the order discontinue time of “now” based on the Surgery DC. Performing a hang on the order causes the Predicted Action to change to “Check”, statuses now display as Down/Discontinue, and no further events are scheduled in the IVAR.

844623 Summary

PRN orders with “start at” in the future displayed in the Scheduled Orders section of the Medication/IV Administration menu function.

Symptoms

PRN orders with “start at” time defined in the future displayed in the Scheduled Orders section of the Medication/IV Administration menu function.

Cause

The System displayed the order in the Scheduled Orders section instead of the PRN Orders section of the Medication/IV Administration menu function because it did not encounter any events due to the future “start at” time.

Resolution

PRN orders with future start times now display in the PRN Orders section of the Medication/IV Administration menu function.




845275 Summary

Result Entry Profile Table, ^nt(“rp”), Anatomical Pathology Gross Room data element data did not display when the user reviewed results in the Result Entry (Equiv Results w/Selection), Result Entry (Equiv Results), Result Entry (Multiple Events), Result Entry (Specimen First), and Result Verification menu functions.

Symptoms

When reviewing or viewing a result prior to editing or completing the result, if a Result Entry Profile Table, ^nt(“rp”), Anatomical Pathology Gross Room data element was present on the result profile for the procedure, the data element and any currently documented information did not display. The data element and documented information displayed once the user was able to edit the result profile.

Result profiles are linked to procedures in the Procedure Table, ^t, Documentation Information screen, Result Profile/Link Information field, Result Profile subfield.

Cause

The problem was caused by a recent enhancement related to event display for unsupported data elements. The display criteria for the Anatomical Pathology Gross Room data element were incorrect.

Resolution

Display criteria for the Anatomical Pathology Gross Room data element have been updated so that the field created from the data element displays when reviewing results.

846498 Summary

The Clinical Quality Measures Run menu function (eCQM) was not evaluating unscheduled medication documentation.

Symptoms

The eCQM was not evaluating unscheduled medication procedure documentation. This problem occurred for quality measures SCIP Inf1 - Prophylactic Antibiotic Received Within One Hour Prior to Surgical incision and SCIP Inf2 - Prophylactic Antibiotic Selection for Surgical Patients. The results did not show that the unscheduled medication was part of the measure evaluation.

Cause

The eCQM was not initially designed to evaluate administered medication events without orders.

Resolution

The eCQM now includes unscheduled medication procedures in measure evaluation.




846501

839486

Summary

In quality measures evaluating surgical procedures, qualifying patients were failing to make the Initial Patient Population (IPP).

Symptoms

When viewing the Clinical Quality Measures Run menu function (eCQM) debug log or viewing patient data in a Continuity of Care Document (CCD), the surgery procedure date/time displayed the time of the documentation of the procedure rather than the indicated date/time of the procedure.

Cause

QCPR was using the archive event date/time for evaluating procedures and comparing that to the start and end date/time of the visit. When procedures were documented after the visit was discharged, the procedures failed to be evaluated as occurring within the visit.

Resolution

Documented surgical procedures now use the start date/time of the procedure instead of the date/time of the documented event. The Result Profile Table, ^nt("rp"), data element used to document start date/time needs to be mapped to SNOMED Code 398201009 using the Concept Mapping Tool application for this data element to be properly evaluated for clinical quality measures. The start date/time of the procedure is now properly reflected in the CCD created in the Document List application.

846702 Summary

An error occurred when the user attempted to print Krames patient education documents in English for patients with names containing Arabic characters.

Symptoms

The issue occurred when the user documented results for a procedure in a result profile containing an Assessment Category/Data Element Table, ^nt("ac"), Patient Education data element, selected the English language for the patient education document, and chose the document and accepted it. When the event was selected in the Chart Review menu function, the selected document did not display. An error message, The Unicode point '2' is not a legal XML 1.0 character, would display, or print requests for the patient education document would fail.

Patient education documents for patients with names that did not contain Arabic characters displayed as expected. Patient education documents in languages other than English that were selected for patients with names containing Arabic characters also displayed as expected.

Cause

Patient education documents in English were not supported when the patient name contained Arabic characters.

Resolution

The user can now print and review PDFs of English language patient education documents when the patient name contains Arabic characters.




847148 Summary

Patient demographics were not being populated on the debug log or measure analysis in the Clinical Quality Measures Run menu function (eCQM).

Symptoms

Patient demographics, such as race, birthdate, and ethnicity, were not being populated on the eCQM debug log or on the measure analysis, even though they were correctly displaying on the Continuity of Care Document (CCD).

Cause

The values of the demographics were not being stored into the correct variables that would cause them to populate the debug log and run analysis.

Resolution

The demographic values are now properly inserted into the correct variables and display in the debug log and in the run analysis. The data continues to display properly on the CCD.

847247 Summary

The Inactive Code Report was not printing when requested.

Symptoms

The report defined in the Problem List Inactive Code Search menu function, Inactive Code Report push parameter would not print if the Print Queue push parameter was defined as terminal default.

Cause

When the Problem List Inactive Code Search menu function, Print Queue push parameter was defined as terminal default, the print request did not use the value defined in the Device Table, ^ad, Printer Group field. Printing would only occur if the Problem List Inactive Code Search menu function, Print Queue push parameter was defined with a specific printer.

Resolution

The Inactive Code Report now prints when the Problem List Inactive Code Search menu function, Print Queue push parameter is defined as terminal default.

848133 Summary

Procedure selection screens auto-suggestion is not defaulting when the problem is selected from the Reason For Orders dropdown in the Order Entry application.

Symptoms

In the Order Entry application, the problem-specific order set did not get selected if the problem was selected from the Reason For Orders dropdown list. Order sets are defined to be auto-suggested in the Problem List Master Table ^nt(“plm”), Procedure Tree(s)/Set(s) field. This issue arose when the Order Set option and an order set were selected and listed in the Currently Defined Procedure Tree(s)/Set(s) Options display.

Cause

This issue occurred when the problem was selected from the list of active problems presented in the Reason for Orders field in the order block when the Problem List Master Table ^nt(“plm”), Procedure Tree(s)/Set(s) field was not defined.

Resolution

When an Order Set is defined to be suggested by a selected problem, the defined Order Set now displays on the Order Selection Tab in the Order Entry application.




848204 Summary

The default definition for the Device Table, âd, Allow Multimedia Edits? field is now configured in the System Parameter Table, ^%z.

Symptoms

When the user attempted to edit a multimedia field created from the Result Entry Profile Table, ^nt(“rp”), Multimedia data element or from the Assessment Category/Data Element Table, ^nt(“ac”), Multimedia data element, the selection/option was not selectable. This worked as expected when the Device Table, âd, Allow Multimedia Edits? field was defined as no. In this instance, the field defaulted to yes and multimedia data elements should have been selectable.

Cause

In QCPR Release 6.0.0 Update 10 and higher versions, the default definition for the Device Table, âd, Allow Multimedia Edits? field was changed from no to yes. The System displayed the default as yes; however, the table did not recognize the setting and functioned as if the field was defined as no.

The Allow Multimedia Edits? field was reintroduced to the Device Table, âd, in QCPR Release 6.0.1 Update 29 and higher.

The new System Parameter Table, ^%z, Utility Parameters subfile, System-specific level, Miscellaneous Parameters screen, Default Allow Multimedia Edits? field has also been added. This new field defines the default definition of the Device Table, âd, Allow Multimedia Edits? field. The Default Allow Multimedia Edits? field defaults to no. In order for access to Multimedia data elements to be editable by default, clients must define the Default Allow Multimedia Edits? field as yes on each domain (DEV, PROD, TEST, etc.) once this update has been received.

Fields created from the Multimedia data element in the Result Entry Profile Table, ^nt(“rp”), or the Assessment Category/Data Element Table, ^nt(“ac”), can be edited only from devices where the Device Table, âd, Allow Multimedia Edits? field is defined as yes.

An additional issue was introduced in Updates 5.4.1.52 and 6.0.1.18 with previously-existing devices that ran the AF loop 37 ‘Clear multimedia edits flag’. The loop set the value of the Allow Multimedia Edits? field to NULL in the global structure. Once the System Parameter Table, ^%z, Utility Parameters subfile, System-specific level, Miscellaneous Parameters screen, Default Allow Multimedia Edits? field was defined as yes, then the existing devices displayed as yes, even though the setting was NULL, preventing access to the multimedia data elements.

Resolution

Multimedia data elements have been updated so that if the System Parameter Table, ^%z, Utility Parameters subfile, System-specific level, Miscellaneous Parameters screen, Default Allow Multimedia Edits? field is defined as yes or is not defined (NULL), then Multimedia data element access is allowed. If the System Parameter Table, ^%z, Utility Parameters subfile, System-specific level, Miscellaneous Parameters screen, Default Allow Multimedia Edits? field is defined as no, then the data element checks if the Device Table, âd, Allow Multimedia Edits? field is defined and displays if defined as yes. If the Device Table, âd, Allow Multimedia Edits? is defined as no, users are not allowed to edit multimedia data elements from the device.

848363 Summary

Users experienced a delayed response when accessing QCPR in the Navigator Mode in Ultiview.

Symptoms

User experienced long wait times for System response when in Navigator Mode in Ultiview. The Error Log also showed Illegal Negative Value errors in program %zu2c%j for users affected by this issue.

Cause

Previously-made changes associated with Audit Log cleanup of logon/logoff logging caused QCPR to experience the slow responsiveness when a popup "interrupt" message was presented or a user clicked the Mailbox button on the Ultiview tool bar.

Resolution

The System no longer experiences delayed response times with "interrupt" messages or when the Mailbox button on the Ultiview tool bar is clicked.




848464

848150

848322

848830

Summary

Users were unable to edit a result within the Provider Inbox Across Patients and Provider Inbox applications.

Symptoms

This issue occurred when the user had a security position defined in the Employee Table, ^ae, that matched at least one security position defined in the Procedure Table, ^t, Documentation Security screen, Result Security field and the result was statused as “unverified”.

The same user was able to edit the result via the Interactive Care Grid application (ICG). The user was able to edit the result if the definition of the Procedure Table, ^t, Result Review Information screen, Result Verification Init Doc field was deleted.

Cause

The component responsible for allowing result editing in the Provider Inbox Across Patients and Provider Inbox applications was preventing the (E) Edit Results processing option from displaying.

Resolution

The (E) Edit Results processing option now displays when reviewing results in the Provider Inbox Across Patients and Provider Inbox applications when the user meets the required edit securities and the result status is unverified.

848560 Summary

When running the Clinical Quality Measures Run menu function (eCQM) for quality measures evaluating when patients were converted from Emergency Department (ED) to Inpatient, the expected patients were not included in the Initial Patient Population (IPP).

Symptoms

In clinical quality measures ED1- Median Time from ED Arrival to ED Departure for Admitted ED Patients and ED3 - Median Admit Decision Time to ED Departure Time for Admitted Patients, patients that qualified for Stratum 3, or patients seen in ED and admitted with diagnosis consistent with psychiatric or mental health disorders, were not part of the Initial Patient Population for the criteria measure.

Cause

QCPR defaulted the principal diagnosis documentation date to be 1 minute after the start of the IP visit. For patients with a diagnosis consistent with psychiatric or mental health disorders, the diagnosis must have a documentation date/time for the ED segment of the visit. Those patients were failing to qualify for the IPP as the diagnosis documentation was within the Inpatient segment of the visit.

Resolution

QCPR now evaluates the patient diagnosis. When the diagnosis falls into the code set listed below, indicating a diagnosis of psychiatric or mental health disorders, the diagnosis documentation time is set to ED Admit Time + 1 minute. In all other cases, the diagnosis documentation time is set to Inpatient visit or transfer time + 1 minute.

Diagnosis, Active: Psychiatric/Mental Health Patient

Psychiatric/Mental Health Patient

2.16.840.1.113883.3.117.1.7.1.299 (Version: 20130401)




848794 Summary

An issue occurred in the prescription writing functionality of the Order Entry menu function or application when a provider created a discharge prescription from a procedure that linked to a product for which a generic packaged drug was not yet on the market. This issue occurred for clients who had purchased the ePrescribing module.

Symptoms

When a Medi-Span drug for an unavailable generic drug form was used in an electronic prescription, a match was not found in the ePrescribing Portal Launch application.

Products are linked to the Medi-Span database in the Product Table, ^pt(“p”), System-specific level, Drug Classification Information – Wolters Kluwer DKV screen, DKV Product Drug Link field. Prescription writing functionality is enabled in the Order Entry menu function or application when prescriptions are configured to be the primary order type.

This issue does not apply to clients who create prescriptions from the Consolidated Medication List application.

Cause

The ePrescribing Portal Launch application matches National Drug Code (NDC) codes with the Medi-Span Drug ID. Generally, when brand name drugs are introduced to the market, a generic form is not available until the patent on the brand name drug expires. Since there wasn’t a packaged drug associated to the Drug ID in Medi-Span, there were no NDC's for the ePrescribing Portal Launch application to match.

When the Product Table, ^pt(“p”), System-specific level, Drug Classification Information – Wolters Kluwer DKV screen, DKV Product Drug Link field is first defined, the recommended practice has always been to use the generic form of the drug, if available. Users are unable to see whether a drug has packaged products available or not.

Resolution

A new menu function, ePrescribing Product DDID without Package Product/NDC Report has been created. This menu function functions as a report that lists all products in the Product Table, ^pt(“p”), that are linked to a DKV Product and do not have packaged drugs available. This menu function can be placed on the User Desktop and be run on demand. Once completed, the report output can be viewed within the Background Job Display for Completed Background Jobs. The report lists the Product Code (from the Product Table, ^pt("p"), System-specific level, Product Identification screen, Primary Barcode ID field) and the Product Name.

It is recommended that this report be run after loading the monthly Medi-Span update.




6.0 AF loop 13 – Rebuild all order profiles

6.0 AF Loop 14 – Rebuild all result profiles

6.0 AF Loop 65 – correct malformed corrected/supplemented Clindoc events




CASE NUMBER Description

841152 Summary

The Clinical Quality Measure Run menu function (eCQM) evaluated patients in the Initial Patient Population (IPP) and displayed correct patients in the menu function as meeting criteria counts but were incorrect in the Debug Log File and QRDA III.

Symptoms

In the Clinical Quality Measure Run menu function, when running the Clinical Quality Measure (CQM) report for "Prophylactic Antibiotic Received Within One Hour Prior to Surgical Incision" (SCIP Inf1), the patients were correctly included in the Initial Patient Population as well as numerator and denominator for sub-measures. However, numerator and denominator patient counts in several sub-measures shown in the Debug Log file and Quality Reporting Document Architecture (QRDA III) did not match the values shown in CQM.

Cause

The Debug Log File and QRDA III report incorrectly represented the data that was created in the eCQM Run menu function.

Resolution

The Debug Log File and QRDA III have been updated so that they display the same patients evaluated by the Clinical Quality Measure Run menu function.

841440 Summary

Default settings for review queues in the Applications User Profile Table, âp were not recognized in the System.

Symptoms

In the Provider Assignment Editor menu function, the Queue? field defaulted to No even though in the Applications User Profile Table, âp, Physician Profile subfile, Review Queue Definition screen, Physician Review Queue Defaults field, Add’l Responsible Review Queue Default Definition subfield, facility default was defined as Always Yes.

Cause

The definition from the Applications User Profile Table, âp for the Additional Responsible field did not retain the value as it was set.

Resolution

The Applications User Profile Table, âp, has been updated to correctly retain the field definition of the Add’l Responsible Review Queue Default subfield when it is defined as Always Yes. The Queue? field in the Provider Assignment Editor when the Applications User Profile Table, âp, Additional Responsible field is defined as Always Yes.




841891 Summary

Unhandled Exception error occurred when Consolidated Clinical Document Architecture (CCDA) documents were created.

Symptoms

When creating Consolidated Clinical Document Architecture (CCDA) documents using the Document List application, multiple errors occurred that prevented the creation of the CCDA. The following error message was generated:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.

Cause

The error was generated during the creation of the XML file used for CCDA documents.

Resolution

Generating XML files for CCDA documents no longer incur errors in the Document List application.

843068 Summary

Duplicate checking was not working for procedures defined to check for duplicate procedures.

Symptoms

A procedure that had been defined with Duplicate Checking parameters, in the Procedure Table, ^t, Order Scheduling screen, Duplicate Proc Parameters field was no longer presenting an alert when the duplicate check threshold had been exceeded. The duplicate check threshold is defined in the Duplicate Procedure Group table, ^nt("dp"), Duplicate Procedure Group Option, Duplicate Procedure Allowance Pairs parameter.

Cause

In the Procedure Table, ^t, Order Scheduling screen, Duplicate Proc Parameters field, Duplicate Procedure Advisory Alert subfield, the value for affected procedures had been set to prescription. It was found that this occurred when the same procedure had the parameter defined in the Procedure Table, ^t, Documentation Information screen, Monitor/Interface Definition field, Allow PACS Study Launch? subfield as yes.

The storage location for Allow PACS Study Launch? subfield and the Duplicate Procedure Advisory Alert subfield was the same. Changing the value for one parameter simultaneously changed the value for the other.

Resolution

Storage locations for the Procedure Table, ^t, Documentation Information screen, Monitor/Interface Definition field, Allow PACS Study Launch? subfield, and in the Procedure Table, ^t, Order Scheduling screen, Duplicate Proc Paramters field, Duplicate Procedure Advisory Alert subfield are now distinct for each parameter.




844476 Summary

CCDA document displayed incomplete allergy information for select patients.

Symptoms

When a large number of allergies (more than 22) were documented for a patient, not all of the allergies displayed when viewing the Consolidated Clinical Document Architecture (CCDA) documents from the Document List application.

Cause

When a large number of allergies were documented, the node in which this data was stored reached the maximum character limit. At this point, an additional node was formed and stored the remaining data. As a result, the Document List application did not populate the data from both nodes from the patient global structure.

Resolution

The Document List application has been updated to consider both global nodes when displaying allergy data for CCDA documents.

845172 Summary

Medications and instructions did not display correctly when viewed from the Clinical Information Reconciliation application.

Symptoms

When a user viewed the Medication tab in the Clinical Information Reconciliation application, some medication instructions displayed in the medication column and medication information did not display.

Cause

The Clinical Information Reconciliation application displayed the XML data from the substance Administration/text element for Medications rather than the substance Administration/manufactured Product/manufactured Material/code/original Text element.

Resolution

The Clinical Information Reconciliation application now incorporates the free-text SIG from the substance Administration/text element so that the medications and Instructions display correctly.

845388 Summary

The Language Translation Table Import menu function did not support the translation of some text.

Symptoms

When the System Parameter Table, ^%z, System-specific level, System Language field was defined as Quebec French, the System did not allow the translation of texts such as "Prior Adverse Reaction" warning text as well as certain other texts.

Cause

Starting with the QCPR 5.4 release, due to the change in revision control system, we had moved the cataloged global repository. This adversely impacted the Language Translation Table Import menu function. Any references made to the old global would not work in some circumstances for certain components. The end result was that non-English clients were unable to translate certain English text depending on the component.

Resolution

The components and translation code was updated to allow translation of cataloged components.




845696 Summary

System out of Memory errors displayed when creating multiple CCDA documents in the Document List application.

Symptoms

When a user generated multiple Consolidated Clinical Document Architecture (CCDA) documents sequentially in the Document List application, the application failed with a System out of Memory error.

Cause

Based on the contents of the Error Log files created with this error, a Memory Error Leak was occurring in the document preview which is in Open XML Paper Specification (XPS) format.

Resolution

The Document List Application has been updated to allow the XPS format preview to be inactivated so that only the XML format of the report is seen. This inactivation must be performed for workstations where multiple sequential CCDA documents are created (e.g., Medical Records).

To inactivate the XPS format preview after loading the CDA build included in this update, locate and define the app.conf file in the local workstation to false.

845901 Summary

In the Clinical Information Reconciliation application on the Medications tab, when merging selected medication(s), the Medication field on the Merge Medication(s) screen driver did not populate with the medication name.

Symptoms

When a user selected medication(s) from the imported document to merge to the patient record in the Clinical Information Reconciliation Application, the Merge Medication screen driver, Medication field did not populate with the medication name for the selected medication(s).

Cause

The medications that are required to display in the Medication field in the Clinical Information Reconciliation application, Merge Medications screen driver were not constructed properly to display the medications based on the RXNORM code mapped with multiple DDID/DNIDs.

Resolution

The medications required to display in the Medication field in the Clinical Information Reconciliation application, Merge Medications screen driver, now display the medication name based on the following:

If RXNORM code contains single DDID, then Medication field is populated by default.

If RXNORM code contains multiple DDID/DNIDs , the Medication field becomes required (displayed in bold format) and users have to select the Medication field. The list of medications then display.




846158 Summary

The Document List application generated a fault xlmns error message when creating a Consolidated Clinical Document Architecture (CCDA) document.

Symptoms

When a user attempted to create a Consolidated Clinical Document Architecture (CCDA) documents using the Document List application, the user received an error indicating QuadraMed.Service.Library.ServiceException: <Fault xmlns="http://www.w3.org/2003/05/soap-envelope"

Cause

The error occurred due to the presence of a greater than symbol, <, in the description of one of the entries in the Social History Section of the CCDA document.

Resolution

The Document List application now translates the "<" character to a version which can be displayed in XML when encountered in the Social History Section of the CCDA.

846203 Summary

Data documented using the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element and defined in the parameter Result Entry Profile Table, ^nt(“rp”), Required Expression as Process Required allowed documentation which was not complete to be accepted in Result Entry.

Symptoms

A result profile contained 2 Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data elements where one was defined in the parameter Result Entry Profile Table, ^nt(“rp”), Constants, Required Expression as Process Required field and another was Not Required. If the result was documented through an interface where the field which was defined as Process Required was empty and the field which was not required filed with data then the event was able to be Accepted in Result Entry although the documentation was not complete.

Cause

The data storage and display structures for the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element did not store separate flags for each Controlled Vocabulary data elements to evaluate required expressions.

Resolution

The result entry dictionary has been updated for these fields. All result profiles which contain Controlled Vocabulary data elements must be rebuilt once this update has been loaded.

846339 Summary

String Too Large error displayed when printing the Chart Print report.

Symptoms

When a user attempted to print a Chart Print report for a patient, the System generated an error message String Too Large in module %zu2c.

Cause

There was an issue with the Result Entry Profile Table, ^ntrp, Active Problem(s) data element where an infinite loop was encountered, causing the data string to exceed the 32K KB Cache limit.

Resolution

The result entry dictionary has been updated so that each loop variable is unique which prevents future occurrences of "String Too Large" errors. All result profiles containing the Result Entry Profile Table, ^ntrp, Active Problem(s) data element must be rebuilt once this update has been loaded.




846549 Summary

Reports which used the Report Formatter Data Dictionary Table, ^arfd, record visit:conversion:visit time type did not match the expected options for the key value. The key value is stored as an integer of 1-6 and represents each of these options.

Symptoms

When the user attempted to build a QCPR report or an SQL connect query using the following items, keyed values did not match the expected options of 1-6 in the Visit Type Table, ^rt(“vt”).

Report Formatter Data Dictionary Table, ^arfd, record of visit:conversion:visit time type

SQL connect table qcpr_arf_OC.VisitConversion.VisitTimeType

Cause

When a Lifecare visit was created, it was created with a coded date and time instead of the absolute time. The values stored for this data contained numbers that exceeded the field limit size for the key value.

Resolution

The Lifecare Visit structure has been updated to store Lifecare Visit Times in absolute time format. AF Loop 5.4 36 Fix Lifecare Visit Visit Times must be run once this update has been loaded. The loop updates every Lifecare visit on the System which may take as long as 48 hours to run. The loop is not expected to interrupt user activity as it updates the records.

846915 Summary

The Order Entry application did not create all scheduled events for change orders.

Symptoms

In the Order Entry application, a user entered a new order with an open frequency (i.e., no built-in termination point). The user then performed a change order against the new order with an effective time beyond the point that the new order had been scheduled and with a closed frequency (i. e, one that has a termination point). This caused the events between the point that the new order had already been scheduled and the effective time of the change order to be missed.

Cause

The Change Order functionality in the Order Entry application did not properly schedule events that were before the change order’s effective time based on the last scheduled date.

Resolution

The Order Entry application now creates scheduled events for change orders that are before the change order’s effective time based on the last scheduled date.




847077 Summary

Checkerboard background displayed in the Problem List application.

Symptoms

When viewing the patient’s problem list in the Problem List application, a checkerboard displayed where the problem description was expected. This also occurred when the user accessed the Problem List application from a field created using the Order Entry Profile Table, ^nt(“op”), Active Problem(s) data element in the Order Entry Application. Issues were only present in the GUI mode.

Cause

Invalid data was stored with the date of the event. The System was unable to display the data and instead displayed a checkerboard.

Resolution

The invalid characters have been removed from the display in the Problem List application.

847087 Summary

In an order with tapered doses, editing a product in one dose cleared products for all other doses.

Symptoms

In the Medication Product Selection Edit menu function, when a user modified or replaced one of the products in a tapering dose, the previously selected products of the order’s remaining tapering dose(s) was removed.

An example would be an order for Prednisone 30 mg po daily followed by 20 mg daily, followed by 10 mg daily. The product originally selected for the 30 mg dose was 1 x 20 mg tab and 1 x 10 mg tab, with the 20 mg dose as 1 x 20 mg tab; and the 10 mg dose as1 x 10 mg tab. In the Medication Product Selection Edit menu function, when the user changed the product for the 30 mg dose to 3 x 10 mg tab, the previously selected products for the other doses in the same tapering order get cleared out.

Cause

When a user modified one of the products in a tapering dose after drug product selection had occurred, the system inadvertently cleared the previously selected products of the remaining tapered doses.

Resolution

Previously selected products of the order’s remaining tapering dose(s) are no longer cleared when the Medication Product Selection Edit menu function is used to modify or replace one of the products.

847116 Summary

Report runs in the Clinical Quality Measure Run menu function (eCQM) completed without any data output.

Symptoms

When performing a patient-specific run in the eCQM, the runs finished immediately without displaying expected data.

Cause

The Patient(s) field in the report screen driver could not be selected and thus could not be defined. The report therefore completed immediately because the System could not retrieve appropriate patient data. The Patient(s) field should have been required as the Patient Specific Run? field was defined as yes.

Resolution

The report screen driver has been updated to require input in the Patient(s) field when the Patient Specific Run? field is defined as yes. The Clinical Quality Measure Run menu function, Default Inquiries and Expand Menu push parameters need to be defined for the patient(s) desired.




847277 Summary

The report GEN – Discharge Medication Print Report generated an error in the Background Job Display when the report was rebuilt after a QCPR update release.

Symptoms

When users attempted to run any of the Historical Medication Package reports, the reports failed to execute and generated errors such as Report screen driver program does not exist or Item does not exist.

Cause

The report GEN – Discharge Medication Print Report included a field called Title which was linked to the Title field in the QuadraMed employee table record. This field is not included in the Report Formatter Data Dictionary Table, ^arfd, on client systems and therefore the error Item does not exist was generated after rebuilding the reports.

Resolution

The GEN – Discharge Medication Print Report has been rebuilt and modified to remove the Title field corresponding to the QuadraMed employee record.

847398 Summary

When using the Drug Query (API) application and selecting the option to print drug information, the patient gender did not default in the print dialogue window.

Symptoms

When printing drug information in the Drug Query (API) application from the main desktop, the print dialogue window had no value for gender even when patient gender of Male or Female was specified.

When running the Drug Query (API) application from the visit desktop for a male patient, the print dialogue window showed Gender as Unknown. This only occurred for male patients.

Cause

QCPR was not using the gender of the patient indicated on the main Drug Query (API) window when printing Drug Information.

Resolution

QCPR now uses the gender of the patient as indicated in the main Drug Query (API) window as the default gender in the print dialogue window when printing drug information in the Drug Query (API) application.

842827

842308

842529

Summary

Documented problem(s) did not display in the Plan of Care section of the Consolidated Clinical Document Architecture (CCDA) document.

Symptoms

The CCDA document created in the Document List application displayed No plan found in the Plan of Care section even though problems were documented in the Problem List application for the patient’s visit.

Cause

The background job Midnight problem list auto resolve in the Daily Jobs Table, ^%zbgdj, automatically resolves problems. When the problems were resolved, the event/problem link was broken, thus the event was not found when building the Plan of Care section of the CCDA document.

Resolution

The Midnight problem list auto resolve job has been modified so that the event/problem link is maintained, allowing problem documentation to display in the Plan of Care Section of the CCDA document.




844728 847013 847665

Summary

An Uncaught Exception Java error occurred when right-clicking on a problem.

Symptoms

When the Problem List application was defined in the Standard Desktop Configuration Table, ^at(“dt”) as an applet, and the user right-clicked on a problem, an Uncaught Exception Java error occurred. The Java error did not occur if the applet was expanded to full screen.

Cause

The Problem List application was updated in 6.0.1.28 Update to resolve an issue where Lifecare visits may have a null value. The Problem List applet was not updated to handle this scenario and therefore generated an Uncaught Exception error.

Resolution

The Problem List application has been updated. The issue and error no longer occur when the application is in applet mode.

847053

847094

Summary

Problem onset date/time was not recognized by the System when the problem was added after discharge.

Symptoms

When the Clinical Quality Measure Run menu function (eCQM) evaluated the problem start date/time for a problem related to a visit, visits were not passing the quality measure if the problem was added after discharge. This occurred even if the problem onset date/time was recorded between the admission and discharge date/time for the visit.

Cause

QCPR only used the date and time that the problem was filed (archive date and time) when evaluating the problem for the quality measure.

Resolution

A new logic is now used for evaluating problem start date/time in the eCQM. The System first checks the problem onset date against the problem archive date. When both dates are the same, the System uses the problem archive date and time. When the onset and archive dates differ, the System then evaluates the onset date against the visit start date (or the transfer date to a non-emergency department location). When the onset date and the visit/transfer dates are the same, the System uses the visit admission date plus one minute. When the onset date and visit/transfer dates differ, the System uses the problem onset date and 0000 as the time

847628 Summary

Divide by Zero error message displayed when entering a dose quantity for a prescription during order entry.

Symptoms

When entering a dose quantity for a prescription in the Order Entry menu function and application, as well as the Health Maintenance Record menu function, a Divide by Zero error message displayed.

Cause

There was an attempt by the System to divide a calculated value by zero during the order entry process when determining the product quantity to dispense.

Resolution

When a user enters a dose quantity for a prescription in order entry, the System now passes a true value to use in the dispensing calculation.





Systems configured with a default System Language of Saudi Arabic must run:

o 5.4 AF loop 36 Fix Lifecare Visit Visit Times

o 6.0 AF Loop 36 – Initialize document-logging audit type

o 6.0 AF loop 14 Rebuild Result Profiles

o 6.0 AF Loop 64 Convert Problem node visits to new 13th piece






842722 Summary

The Clinical Quality Measures Run menu function (eCQM) displayed complete with errors for some measures and displayed a <ZDDIF> error message.

Symptoms:

When an event was documented precisely at 24:00, and the patient was included in a Clinical Quality Measures run, the System generated a <ZDDIF> error message in the Clinical Quality Measures Run menu function.

Cause

When the Clinical Quality Measures Run menu function evaluated the time, the seconds field was evaluated as 0000. The Clinical Quality Measures Run menu function evaluated the 0000 as a null value, generating the error.

Resolution

The Clinical Quality Measures Run menu function now appropriately calculates events with an event time of 24:00.

843140 Summary

Processing option displayed in the transaction line when documenting results in the Result Verification menu function.

Symptoms:

When the System Parameter Table, ^%z, System-specific level, System Language field was defined as Quebec French, and a user was attempting to review and/or verify results using the Result Verification menu function, the Visualiser/Rechercher (B) processing option (translated from the (S) View/Search processing option) displayed in the transaction line instead of as a selectable option. This required the user to clear this option from the transaction line and prevented that activity from performing as it did not display as a processing option.

Cause

The (S) View/Search option was added to multiple menu functions and applications in QCPR 6.0.0 release. The translation utility was not correctly interpreting the new option, causing the display issue.

Resolution

The (S) View/Search option is now correctly translated in the translation utility and displays appropriately with other options available to the user and not in the transaction line.




845147 Summary

Information displayed incorrectly in exported Consolidated Clinical Document Architecture (CCDA) documents when they were viewed in the Interface View Utility menu function.

Symptoms:

When a CCDA was created and exported from the Document List application and later viewed in the Interface View Utility menu function, the CCDA displayed information incorrectly even though it displayed correctly in the Document List application. Information from incorrect fields displayed in the Header and Medication sections.

Cause

The Interface View Utility menu function was using a different style sheet than the Document List application. The style sheet used by the Interface View Utility menu function to translate the XML data to a viewable format was selecting incorrect fields for display. Despite this, the correct data was being sent to the external system.

Resolution

A new style sheet for the Interface View Utility menu function has been created to correctly display CCDAs sent to external systems.

845505 Summary

Fields in the Employee/Provider Table, âe, Facility-specific level are not accessible in the Table Editor Site Specific Security Table, âtes.

Symptoms:

In the Table Editor Site Specific Security Table, âtes, Facility Specific Security subfile, when defining security positions for the Employee/Provider Table âe, Facility-specific level, the following fields could not be selected. Instead, the message User cannot view/edit security displayed.

Job Definition

Sel.Scrns(s)/Trees(s)

Access to My favorites

Cause

Edit security expressions changed in QCPR 6.0.1 release and were no longer available.

Resolution

Edit security expression has been added to the affected fields in the Employee/Provider Table, âe, and users are now able to select those fields to view/edit security.

847073 Summary

Illegal Negative Value errors occurred for various actions in QCPR.

Symptoms:

For systems with the System Parameter Table, %z, System-specific level, System Language field defined as Saudi Arabic, the error Illegal Negative Value occurred for users at multiple locations within QCPR, including creating and filing a prescription or registering a patient.

Cause

The wide characters, which are part of the Arabic language, were causing this error when events were filed to the audit log.

Resolution

The data stream that sends events to the audit log has been modified so that wide characters are processed without errors.




847340

847369

847239

Summary

A midnight job, Midnight send of Pending CCD/Patient Ed docs to Patient Access Module, was running on domains that were not configured with the Patient Access Module.

Symptoms:

Midnight send of Pending CCD/Patient Ed docs to Patient Access Module, a midnight job in the Daily Jobs Table, %zbgdj, was attempting to run daily for client sites that had not implemented the Patient Access Module.

All processes in QCPR were taking longer than normal to complete and responsiveness was diminished for all users.

Cause

The midnight job, Midnight send of Pending CCD/Patient Ed docs to Patient Access Module, in the Daily Jobs Table, ^%zbgdj, was attempting to execute for sites that had not implemented the Patient Access Module. The midnight job checked whether the Patient Access Module was enabled for the site in the HDS Customer Table, ^afc. Since the sites did not have the Patient Access Module implemented, the system could not identify the Patient Access Module server and continued to time out when trying to complete the job.

Resolution

The midnight job now verifies the System Parameter Table, %z, Utility Parameters subfile, System-specific level, Patient Access Parameters screen, Patient Access Web Services Base Address field before executing. If the field is not defined, the midnight job does not attempt to execute.



Systems configured with a default System Language of Saudi Arabic must run:

o 6.0 AF Loop 36 – Initialize document-logging audit type

o 6.0 AF loop 14 Rebuild Result Profiles






ENH QCPR now provides enhanced audit log functionality for tracking application and report activities. New audit log event types have been created to record user actions when launching and closing applications, as well as when executing reports. Also, existing audit log event types have been updated to more consistently record the actions that trigger them.

See Release Notes Addendum 2 for 6.0.1 for more details regarding this enhancement.

846746 Summary

Users sometimes encountered Java error message, NullPointerException in the Consolidated Medication List (CML) application.

Symptoms:

A Java error message, NullPointerException, sometimes occurred when a user selected a discharge or home medication in the standalone Consolidate Medication List application or the Order Entry application, Consolidated Medication List tab. The Order Entry application, Consolidated Medication List tab is available when the Order Entry application, Non-Facility Parameters, Consolidated Med List App field is defined.

Cause

The Clinical Desktop Application did not handle a discharge medication or home medication which contained an empty Order Process Type value, a value set by the Consolidated Medication List (CML) application.

Resolution

The Clinical Desktop Application has been updated so that users select the Home or Discharge medications within the Consolidated Medication List (CML) a NullPointerException java error.




846991 Summary

Unimplemented Atom error occurred when a user executed some reports

Symptoms

When a user executed a report the user was presented with an error message, “Unimplemented Atom” in module ahfs%xxxx.

This error involved the following records in the Report Formatter Data Dictionary Table, ârfd:

visit:event:result:result profile field

visit:event:result:result field internal

visit:event:result:result field external

Reports and interfaces that repeat through any one of the records sometimes failed to include data stored in the appropriate node of the record, causing the reports to err.

Cause

This error affected at least three (3) records in the Report Formatter Data Dictionary Table, ârfd. Event result data is stored in two possible nodes underneath the event result tree: The "r" (primary) node and the "t" (secondary) node.

Data is stored in the secondary node for large storage items (such as word processing and multiple fields), which has extended piecing of the data. This secondary node is actually a filing tree and not an individual node. If a given result is too large for filing in the "r" node, the overflow data is stored in the "t" tree as well. The issue is that reports and interfaces that repeat through any of the following three ârfd records sometimes fail to include data that is stored in the "t" node:

visit:event:result:result profile field

visit:event:result:result field internal (based on a virtual structure)

visit:event:result:result field external (based on a virtual structure)

The "missing" data is because all three of these records have the "r" node as their starting point, after which they also load the "t" node for each "r" node entry through which they repeat. For the visit:event:result:result profile field record, the "r" node is the primary structure, and the "t" node is an additional structure in ârfd. For the other two records, the virtual structure code loads the "r" node, and then "adds" the "t" node data to it. The error message received indicated that data in the record did not have a corresponding "r" note for a given "t" node because the overflow of data in the "r" node an entry point was not found.

Resolution

The Report Formatter Data Dictionary Table, ârfd has been updated to reference data stored in records that use virtual structures. All reports must be rebuilt after this update is received.




828285

843440

Summary

The message The Wolters Kluwer Medi-Span API Modules Drug Advisory System is unavailable displayed for clients using the Medi-Span flat file database.

Symptoms

When a client using the Medi-Span flat file database clicked the Drug Info button in the Order List or Consolidated Medication List application, or in the Order Entry application, Consolidated Medication List tab, the System displayed the message: The Wolters Kluwer Medi-Span API Modules Drug Advisory System is unavailable. No clinical drug checking will occur. Upon clicking OK to accept the message a Java Error Message was received.

Cause

The Drug Info button should only display for Medi-Span API Clients, as drug information is not available through the Order List or Consolidated Medication List application for Medi-Span flat file implementations for Drug Knowledge Checking (DKV).

Resolution

The Drug Info button now only displays in the following:

Order List application

Consolidated Medication List application

Order Entry application, Consolidated Medication List tab

Order history for Medi-Span API clients

Clients using the Medi-Span flat file implementations can access drug information using the Patient Drug Education Inquiry menu function.

832743 840238

Summary

SQL Connect record update: qcpr_arf_OC.VisitConversionReferredByPhysician fields EmployeeFacilityID and EmployeeFacilityAdditionalAddressID.

Symptoms

The following fields in the SQL Connect table qcpr_arf_OC.VisitConversionReferredByPhysician did not display data from the visit:conversion:referred by physician record as expected:

EmployeeFacilityID

EmployeeFacilityAdditionalAddressID

Cause

Previously, there were two (2) fields in the SQL Connect table qcpr_arf_OC.VisitConversionReferredByPhysician:

EmployeeFacilityID

EmployeeFacilityAdditionalAddressID

An enhancement in the QCPR 5.4 Release merged these fields into the single field AdditionalAddressFacilityID.

Data for these entries is stored in the Report Formatter Data Dictionary Table, ârfd, visit:conversion:referred by physician record. However, the data that is stored in the Report Formatter Data Dictionary Table, ârfd, visit:conversion:referred by physician record did not display in the SQL Connect table qcpr_arf_OC.VisitConversionReferredByPhysician fields.

Resolution

SQL Connect has been updated so the table qcpr_arf_OC.VisitConversionReferredByPhysician, records EmployeeFacilityID and EmployeeFacilityAdditionalAddressID now display data in the fields based on the record within the Report Formatter Data Dictionary Table, ârfd, visit:conversion:referred by physician record.




839743 840491 841719

Summary

Using the Modify Active Orders menu function to reschedule medication administration events that have a solution ID caused the rescheduled events to fail Bar Code Medication Administration (BCMA) processing with the error message Product ID XXXXX not on file.

Symptoms

When the user scanned the solution ID for a medication, the System displayed the error message Product ID XXXXX not on file. This only occurred when the medication schedule was edited using the Modify Active Orders menu function, but not if the schedule was changed using the Change Order option in the Order Entry application or menu function.

This issue affected events for the medication order where the products with a solution ID had been delivered to the nursing unit and those products were affected by the schedule change.

Solution IDs are used for medications that are processed through solution queues, including orders that have the Route Table, ^pt("ro"), Route level, Product Selection Type field defined as IV, Syringe, or IVPB, and the products are not obtained from floor stock.

Cause

The Modify Active Orders menu function did not acknowledge previously generated solution ID numbers.

Resolution

The Modify Active Orders menu function now processes the rescheduling of doses in the same way as the Change Order option in the Order Entry application or menu function. This allows rescheduled doses to be successfully administered using BCMA.


There are no screens that need to be rebuilt for this update.


AF Loop 5.4 #35 Rebuild ^alog event types

AF Loop 6.0 #3 Rebuild Report Writer (arf) Reports






821495 Summary:

Free-text strings entered in a field created from the Result Entry Profile Table, ^nt(“rp”), Numeric data element did not display in SQL Connect queries.

Symptoms:

The Result Entry Profile Table, ^nt(“rp”), Numeric data element enables users to enter a comment associated with the numeric data by entering a space following the numeral. The entered text string saved with the documented result is visible on the result profile and expected to be retrievable in SQL Connect queries. However, the text string entered following a space in the numeric field did not display as expected when running SQL Connect queries for the qcpr_arf_OC.VisitEventResultResultProfileField record.

Cause:

Text strings entered in a field created using the Result Entry Profile Table, ^nt(“rp”), Numeric data element was not available for evaluation by the SQL Connect qcpr_arf_OC.VisitEventResultResultProfileField record.

Resolution:

The new SQL Connect record qcpr_arf_supplemental.VisitEventResultResultProfileField is now available. The new record can access Numeric Data Element comments.

821752 Summary

The Interactive Care Grid application (ICG) did not consistently open with fixed rows expanded as expected.

Symptoms

Fixed rows defined in the Interactive Care Grid application, Non-Facility Preferences, Interactive Care Grid Fixed Rows field did not display expanded in the application. Also, normal rows defined in the Interactive Care Grid Normal Rows field displayed collapsed with icons indicating data was present.

This issue occurred intermittently and with higher frequency when QCPR was accessed via Citrix.

Cause

The ICG executes two Clinical Desktop Application (CDA) background jobs to load data in the application. When the jobs completed out of the sequence required by the display build, the ICG did not build or display correctly.

Resolution

The Interactive Care Grid application has been updated to ensure the CDA jobs are completed in the correct sequence required to display data as intended.




843918 Summary

In the Clinical Information Reconciliation application (CIR), when merging multiple patient allergies to the patient record, the user had to process one allergy at a time.

Symptoms

When selecting allergies to merge to the patient record from an imported document, the System did not cycle through each or all selected allergies. Instead, the System allowed the user to document one allergy on the assessment screen and then returned the user back to the Clinical Information Reconciliation application to select another allergy to document.

Allergy assessment procedures are defined in the Clinical Information Reconciliation application, Facility Parameters, Allergy Assessment Procedure field. The data is then defaulted into the assessment screen defined in the Procedure Table, ^t, Documentation Information screen, Result Profile/Link Information field, Assessment Screens subfield when the Procedure Table, ^t, Documentation Information screen, Result Profile/Link Information field, Result Entry Type subfield is defined as assessment.

Cause

The procedure responsible for merging allergy data was not merging and defaulting all data into the allergy assessment screen.

Resolution

The procedure responsible for merging allergy data now defaults all allergies selected in the Clinical Information Reconciliation application into the allergy assessment screen.



There are no AF Loops that need to be run for this update.






ENH The Clinical Quality Measures Run menu function (eCQM) has been enhanced to allow users to delete a run.

The new Clinical Quality Measures Run menu function, Delete Security push parameter has been added. This push parameter can be defined with a security position(s) from the Security Position Index Table, âet(“spi”), and the Security Position Table, âet(“sp”). When the user meets the security(s) defined in the Delete Security push parameter, the (D) Delete processing option displays within the Clinical Quality Measures Run menu function (eCQM).

User securities are defined in the Employee/Provider Table, âe, Facility-specific level, Security Positions field.

836581 Summary:

Bulk product orders with a “start if” condition were charged twice.

Symptoms:

When an activate condition was documented as met for a conditional order, the bulk products which had been charged at initial dose were charged again. A product is considered a bulk product when the Product Table, ^pt(“p”), System-specific level, Order/Dispensing Information screen, Dispensing Type field is defined as bulk.

Cause:

The flag that prevented bulk orders from charging was not sent to the charging routine.

Resolution:

This flag is now being sent, preventing duplicate charges when the “start if” condition is met.

841295 Summary

The Clinical Quality Measures Run menu function (eCQM) omitted patients from the Initial Patient Population (IPP) with qualifying Emergency Department (ED) to Inpatient (IP) visits.

Symptoms

When running the eCQM for quality measures that included Median Time from ED Arrival to ED Departure for Discharged ED Patients, the run did not contain all expected patients in the IPP. Other quality measures with the same logic included the omitted patients.

Cause

This issue occurred when the eCQM did identify the complete and correct list of patients, but the display skipped the first and last line when the list included more than one page of returned data. This was due to the way the display was built by QCPR.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated to prevent the omission of data in run displays when there is more than one page of returned data.




843290 Summary

When using the Clinical Quality Measures Run menu function (eCQM) to evaluate the quality measure for Anticoagulation Therapy for Atrial Fibrillation/Flutter (STK-3), the menu function did not correctly evaluate discharge medication orders placed for a patient. The System instead compared whether the medication start time was bounded by the start and stop time of the inpatient visit.

Symptoms

When an order for a discharge medication met the requirement to pass the quality measure for Anticoagulation Therapy for Atrial Fibrillation/Flutter (STK-3), the Clinical Quality Measures Run menu function (eCQM) incorrectly marked the run for that patient as “failed”.

Cause

The Clinical Quality Measures Run menu function (eCQM) was evaluating if the start and stop time for medication orders were within the bounds of the visit.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated to only evaluate whether the start time for discharge medication orders is within the bounds of the visit. Any Clinical Quality Measure runs that failed due to this issue need to be run again to evaluate as expected.

843551 Summary

In the Patient Access Account Manager, a <COMMAND> error occurred, preventing creation of new accounts.

Symptoms

When creating a new patient account in the Patient Access Account Manager, a <COMMAND> error displayed, preventing addition of the new account. The user was unable to create a new account.

Cause

This error occurred when guarantor information was present in the patient visit record, but no guarantor relationship to the patient was defined. The Patient Access Account Manager needed a relationship to be defined.

Resolution

An update has been implemented to prevent errors in the Patient Access Account Manager when a guarantor is defined in the patient visit record without a defined relationship.

842039 Summary

The user was able to renew discontinued prescriptions in the Order Entry application.

Symptoms

In the Consolidated Medication List tab of the Order Entry application, the user was able to renew a prescription that had been discontinued by selecting a discontinued prescription and clicking on the Renew button. The Consolidated Medication List tab displays in the Order Entry application when the Order Entry application, Non-Facility Parameters, Consolidated Med List App field is defined with a configured Consolidated Medication List application.

Cause

The Order Entry application, Consolidated Medication List tab did not disable access to the Renew button when the prescription was past the discontinue date.

Resolution

The Order Entry application has been updated so that the Renew button no longer displays on the Consolidated Medication List tab when a discontinued prescription is selected.





ENH New principal procedure logic has been introduced:

When the principal procedure is picked up to be included in the Quality Reporting Document Architecture (QRDA) engine, the System now scans all the other procedures and attempts to match the principal procedure code to that of another procedure (picked up by the Procedure Type marker).

o If a match is found, the System includes any attributes associated with the matched procedure in the principal procedure (including incision date/time).

The System now uses that procedure’s exact time.

o If a match is not found, the System uses the date that was mapped to the Start SNOMED code 398201009 and scans for that exact day, in order to identify an incision date/time.

If an incision date/time is found, the System includes any attributes associated with the matched procedure in the principal procedure (including the incision date/time).

o The system uses that procedure’s exact time.

If an incision date/time is not found, the System scans for a surgical procedure (CCD mapping approach) on the date received.

o If only one surgical procedure is found, that procedure’s attributes are used.

o If more than one surgical procedure (CCD mapping approach) is found on that date, the System does not add any additional attributes and generates a procedure performed template with the code, principal code, and date (time is visit admit + 1 min).

NOTE: This enhancement is included in 6.0.1 Update 22 and higher releases.




833381 Summary:

The screen sequence in the Order Entry menu function did not match the sequence for the Order Entry application, causing confusion if an item from a procedure selection screen did not have the Order Entry Profile Table, ^nt(“op”), When data element completely defined.

Symptoms:

This issue occurred when the user selected an option from a procedure selection screen in the Order Entry menu function that did not have the Order Entry Profile Table, ^nt(“op”), When data element completely defined. The order profile would display as blank for one or more of the frequency atoms defaulted for the When data element, such as “q ___ hrs”.

The user was prompted to document the field created from the When data element. Upon doing so, the System displayed a frequency selection screen. This was confusing to the user, since it appeared as if the frequency was not complete. In the Order Entry application, the frequency screen is not presented once the When data element field is completed.

An item on a procedure selection screen can be defined without a complete frequency in the Procedure Selection Tree Table, ^nt(“ps”), Selection Tree Line Definition level, Procedure(s) field. During procedure definition, the user can define default order information. When frequency atoms selected for the When data element are incomplete and not defined for the procedure, the field created from the When data element displays as incomplete or blank.

Cause:

The screen sequence used by the Order Entry menu function added an extra screen which was not present in the Order Entry application screen sequence.

Resolution:

The screen sequence has been modified to omit the frequency selection screen if the When data element is defined in the order profile by entering the incomplete frequency atoms.

839881 Summary

The Clinical Quality Measures Run menu function (eCQM) failed to evaluate Result Entry Profile Table, ^nt(“rp”), Word Processing data elements when a Result Entry Profile Table, ^nt(“rp”), Numeric data element and Word Processing data element were mapped to the same concept in the Concept Mapping Tool application.

Symptoms

When both a Word Processing and a Numeric data element were mapped to the same concept, if there was a result documented for both data element types on the same result profile, the results were not evaluated in eCQM runs as expected. Additionally, when the user created a Consolidated-Clinical Document Architecture (CCDA) document with the Document List application, the numeric portion of the result would display, but the word processing portion of the result displayed as an asterisk (*).

Cause

It is common for some lab results to be accompanied with result text, which clarifies or adds information to the numeric result. It is appropriate to map the numeric and word processing text, as both data elements are expected to appear when a CCDA document is created.

For the eCQM run, only the Numeric data element was part of the evaluation. When Numeric and Word Processing data elements were mapped to the same concept, the eCQM could not evaluate the Word Processing data element and thus both data elements were ignored.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated to evaluate only the Numeric data element when both a Numeric and Word Processing data element are mapped to the same concept. When a CCDA document is created, all the information in the Numeric and Word Processing data elements displays, even if both data elements are mapped to the same concept.




840196 Summary

Medication orders without an Automatic Stop Order (ASO) defined in the Procedure Table, ^t, DC/ASO Information screen, ASO Definition field were not being sent to Pyxis via the HL7 interface.

Symptoms

Users were unable to draw out medications from the Pyxis dispensing cabinet. The medication orders were active and scheduled in QCPR.

Cause

The System compared order start time to order stop time. When no order stop time was defined, it was interpreted as a zero, "0", in the HL7 node and no interface message was created.

Resolution

When the order has no stop time, the order start/order stop time check no longer causes the HL7 node to have a "0" value and orders are sent correctly to Pyxis.

840303 Summary

Order block display expression “<cr>” was not found in the report writer.

Symptoms

When writing standard QCPR reports, there was no option to extract line breaks “<cr>” from the data.

Cause

The Report Formatter Data Dictionary Table, ^arfd, was never developed to output this data.

Resolution

The Report Formatter Data Dictionary Table, ^arfd, has been updated. The new visit:order:order state:order number:multiple line and visit:order:order state:block display multiple line records have been created. These records allow report writers to repeat through the multiple lines of block display value.

844244 Summary

Users were unable to review past clinical quality measure runs in the Clinical Quality Measures Run menu function (eCQM).

Symptoms

When the user selected a previously completed clinical quality measure in the eCQM, an XSLT XML Transformer Error occurred.

Cause

This issue was caused when a numeric result, documented using a Numeric data element, also contained free-text in addition to the numeric value.

Resolution

The eCQM now properly displays previous clinical quality measure runs when a documented numeric result has an additional comment in the same field.




844340 Summary

The Clinical Quality Measures Run menu function (eCQM) was not including patients in the Initial Patient Population (IPP) as expected based on diagnosis.

Symptoms

When a Clinical Quality Measure was run in the eCQM, patients with qualifying diagnoses were not included in the IPP.

Cause

In some cases, the diagnosis date/time occurred before the Admit or Transfer date/time to a non-emergency department (ED) location. This would occur when the principal diagnosis was documented prior to the patient Admit or Transfer to a non-ED location.

Resolution

A new Event Index has been created for principal diagnosis. When the above scenario occurs, the eCQM now evaluates the principal diagnosis and associates it with the patient’s Admit or Transfer date/time, allowing the patient to be included in the IPP as expected.

844422 Summary

Users received an error message and could not login to the Clinical Desktop Application (CDA) across multiple devices.

Symptoms

When the user attempted to login to CDA across multiple devices, an error message displayed. The message notified the user that they were already logged in and prevented the user from logging in to another session.

Cause

Instead of referencing the definition of the Employee/Provider Table, âe, Facility-specific level, Allow Multiple Connections? field, CDA incorrectly referenced the values defined in the Employee/Provider Table, âe, Facility-specific level, Chart Review Access field. When the Chart Review Access field was defined as Not Allow, multiple log-ons were disabled.

Resolution

The facility-level multiple log-on check in CDA has been updated, enabling the user to have multiple log-ons. The check will now reference the Allow Multiple Connections? field in the Employee/Provider Table, âe.

844817 Summary

The Department Order Review Queue application and menu function (DORQ) did not display the effective time if there was only a change order.

Symptoms

When only one order state existed in DORQ for an order, (e.g., new or change order and not both), the Effective Time field did not display in the header when the pharmacist selected the order. If an order had both a new and a change order state in DORQ and the order was selected, the Effective Time field displayed in the header.

Cause

There were not enough lines in the DORQ header, which did not allow the Effective Time field to display.

Resolution

A new line has been added to the header. The Effective Time field now displays on the DORQ header when only one order state exists for an order.




844997 Summary

An undefined error occurred when filing a patient registration in the Patient Identification menu function when the Allow Adds? push parameter was defined as yes: qcpr.log.cee.CriteriaMessageDestination.

Symptoms

An undefined error displayed when the System processed a patient registration that fulfilled requirements of certain criteria. Criteria is defined in the Criteria Engine Table, ^nt("ce"), Criteria field.

Cause

A correct variable value based on the Criteria definition defined in the Criteria Engine Table, ^nt(“ce”), Criteria field, was not created. This variable is needed to complete the Criteria Engine processing.

Resolution

Criteria Engine processing has been updated to define and use the correct variable when evaluating criteria.

845018 Summary

An error occurred when adding or viewing procedure selection screens in the Procedure Selection Tree Table, ^nt(“ps”).

Symptoms

When the user tried to add or view procedures in the Procedure Selection Tree Table, ^nt(“ps”), and the Procedure Selection Tree Table, ^nt(“ps”), Selection Tree Line Definition level, Procedure(s) field was defined with a default procedure that contained a frequency option type of “q bedtime”, the user received an error message: Language Syntax Error, and the System prevented the procedure selection tree from being saved.

Cause

The Procedure Selection Tree Table, ^nt(“ps”), did not display “q bedtime” frequencies due to incorrect coding syntax.

Resolution

The Procedure Selection Tree Table, ^nt(“ps”), has been updated to display “q bedtime” frequencies without error. Procedure selection screens with a “q bedtime” frequency will need to be rebuilt once this update has been received.

845165 Summary

When a Consolidated-Clinical Document Architecture (CCDA) document was sent from QCPR as an HL7 message in XML format, effective dates for vital signs displayed as "00010101000000".

Symptoms

The effective date/time for vital signs displayed as "00010101000000" instead of the correct date and time in the XML message.

Cause

The issue occurred because the Document List application interpreted the effective date/time incorrectly.

Resolution

This issue has been resolved in CDA build 6.0.1.68. The effective date and time for vital signs is now correctly interpreted and displays in the XML message in the correct "yyMMddHHmmss" format.




845418 Summary

A missing routine line error was generated when the user filed multiple procedures in the Order Entry application at the same time.

Symptoms

This issue occurred when the Order Entry application, Non-Facility Parameters, Consolidated Med List App field was defined with a configured Consolidated Medication List application and the user included multiple procedures in an order. Accepting the order generated a missing routine line error in the Error Log Display menu function, preventing the order from filing.

Cause

An incorrect function call caused the missing routine Caché error.

Resolution

When the user orders multiple procedures at the same time, the Order Entry application now uses the correct function call, preventing the missing routine line error.

845725 Summary

Values were incorrect for antibiotic susceptibility definitions in the Microbiology Antibiotic Table, ^nt("ma"), Antibiotic Range Definition field, Interpretation subfield.

Symptoms

Definitions for the resistant range value in the Microbiology Antibiotic Table, ^nt("ma"), Antibiotic Range Definition field, Interpretation subfield displayed with an additional equal sign, “=”, causing the range to display as <=, which is the same display for the intermediate range value. This led to confusing result displays and impacted correct antibiotic selection for patients.

Cause

The System incorrectly inserted the equal sign, “=”, in the final component of the range definition as part of a new display algorithm for listing organisms.

Resolution

The final component of the range definition in the Microbiology Antibiotic Table, ^nt("ma"), no longer contains the equal sign, =, to allow for correct result interpretation. The Cleanup Antibiotic Sensitivity Interpretation Mapping AF loop must be run once this update has been applied.

845846 Summary

Global subscript length error occurred when defining free-text home or discharge medication in the Home Medication Editor menu function.

Symptoms

In some cases, when the user defined a free-text medication name in the Medication field of the Home Medication Editor menu function, a global subscript length error displayed and did not allow the user to complete the process.

Cause

This issue occurred when the entered free-text medication name exceeded the Caché subscript limit of 255 characters. In QCPR, there was no length restriction for the free-text medication name. The medication name is used as an index in the patient structures and the indices are used for sorting home/discharge medications when they are displayed to the user.

Resolution

These indices have been truncated to 127 characters to accommodate both English and non-English systems. A new loop was created to convert existing data.




838234 838227 838765 838767

Summary

In certain scenarios, default product selection did not occur correctly based on product availability.

Symptoms

The following scenarios occurred in either the Department Order Review Queue menu function or in the Order Entry menu function and application when the Order Entry menu function, Allow Drug Product Selection? push parameter and/or the Order Entry application, Non-Facility Parameters, Allow Drug Product Selection? field was defined as yes:

The System did not display whole products first for product selection:

For example, in an order for a 3 mg tablet, the System suggested one 2.5 mg tablet and 0.5 of a 1 mg tablet instead of one 2 mg and one 1 mg tablet when product strengths of 1, 2, and 2.5 mg were available.

Product Selection logic is to use whole products first when available.

The suggested products exceeded the ordered dose.

For example, in an order for 3.5 mL of a liquid where unit dose products were available for 3 mL and 1.5 mL, the System displayed products that totaled 4 mL.

Cause

An issue with rounding occurred when the System calculated portions of the total dose. This resulted in incorrect product selection and incorrectly dispensed total doses.

Resolution

Product selection calculations now suggest the correct and best match for quantities and dosages for ordered medications based on available products.

839704

842722

841481

843095

841481

Summary

The Clinical Quality Measures Run menu function (eCQM) displayed as complete with errors for the clinical quality measures defined for Venous Thromboembolism Patients Receiving Unfractionated Heparin with Dosages/Platelet Count Monitoring by Protocol or Nomogram (VTE-4) and Incidence of Potentially-Preventable Venous Thromboembolism (VTE-6).

Symptoms

When executing the clinical quality measures for VTE-4 and VTE-6 in the eCQM, the menu function displayed as complete with errors with the error message: Patient build error Code <COMMAND>, Location=zBuildResultsForEvent+8^qcpr.build.EventsDta.1.

Cause

The eCQM displayed a secondary error message: Profile not imported. The error resulted because there were procedures present that did not have a result profile defined in the Procedure Table, ^t, Documentation Information screen, Result Profile/Link Information field, Result Profile subfield.

This is a valid configuration in QCPR; however, for clinical quality measure evaluations, result profiles are required to be mapped to a concept marker in the Concept Mapping Tool application.

Resolution

The Clinical Quality Measures Run menu function (eCQM) now only processes events which have a corresponding concept marker mapped in the Concept Mapping Tool application.






AF Loop 6.0 #63 Cleanup Antibiotic Sensitivity Interpretation Mapping

AF Loop 6.0 #62 Truncate Long Free-text Home Disch Med Name Indices






ENH The ePrescribing Vendor Table, ^pt(“erxv”), Registration User Name and Registration Password fields have been replaced with the Dev Registration Definitions and Prod Registration Definitions fields. The Dev Registration Definitions field will expand to allow definition of the Dev Registration User Name and Dev Registration Password subfields provided by Dr.First for registration. When the Prod Registration Definitions field is selected for definition, the Prod Registration User Name and Prod Registration Password subfields provided by Dr.First display for definition.

In order to activate ePrescribing, the ePrescribing System/Server for each facility must be defined as either a Development or Production System in the System Parameter Table ^%z, Order Comm System Parameters subfile, Facility-specific, ePrescribing Parameter screen.

827306

841963

Summary

Error message displays upon saving from the Clinical Information Reconciliation application.

Symptoms

When a user imported a Consolidated-Clinical Document Architecture (CCDA) document, selected the Display Document(s) button in the Clinical Information Reconciliation application, and attempted to save any selected Allergies, Medications, or Problems from a Visit Summary document type, the user received one or both of the following error messages:

Save failed for CCD: Visit Summary (id=1). Error Procedure and/or result profile not defined!

Save failed for CCD: Visit Summary (id=2). Error: Event data does not exist!

Cause

The initial issue which caused the Save failed for CCD: Visit Summary (id=1). Error Procedure and/or result profile not defined! error message occurred when the System Parameter Table, ^%z, Order Comm System Parameters subfile, Facility-specific level, Miscellaneous Parameters screen, Clinical Reconciliation Procedure field was not recognized by the Clinical Information Reconciliation application when the (P) Choose Procedure Name option was selected.

Once the initial issue was resolved, the user received the Save failed for CCD: Visit Summary (id=2). Error: Event data does not exist! error message. This error was generated upon a second save attempt in the Clinical Information Reconciliation application when a medication or problem was selected from a Visit Summary document type. The Clinical Information Reconciliation application did not update the timestamp for the event created by the selected event.

Resolution

The Clinical Information Reconciliation application has been updated to identify the selected procedure and result profile based on the selected procedure in the System Parameter Table, ^%z, Order Comm System Parameters subfile, Facility-specific, Miscellaneous Parameters screen, Clinical Reconciliation Procedure field. Visit Summary document types can now be reconciled with events when Clinical Information Reconciliation is performed.




841659 Summary

The Clinical Quality Measures Run menu function (eCQM) displayed complete with errors for the clinical quality measure Venous Thromboembolism Patients with Anticoagulation Overlap Therapy (VTE3).

Symptoms

The Clinical Quality Measures Run menu function was run for the clinical quality measure VTE3. When users selected the (V) View Report Overview processing option, the following error message displayed: Cache ERROR #5002 Cache Error: <WIDE CHAR>zTransformStreamWithCompileXSL+37^%XML.

Cause

The issue occurred when a Result Entry Profile Table, ^nt("rp"), Numeric data element was evaluated by the Clinical Quality Measures Run menu function and data was not translated into a format that could be displayed in XML when the (V) View Report Overview processing option was chosen.

Resolution

The Clinical Quality Measures Run menu function has been updated to evaluate Result Entry Profile Table, ^nt("rp"), Numeric data elements in a format acceptable to XML. The (V) View Report Overview processing option now displays clinical quality measure information as expected. Any runs that experienced this issue need to be run again.

843314

Summary

Reports which referenced the GEN - HTML and Javascript Library report generated errors when the reports were rebuilt after a database roll.

Symptoms

The Historical Medication Package uses a group of subroutines which enable the reports in the package to execute properly. The majority of the subroutines used in the report package are in the Hierarchical Filing Structure (HFS), GEN - HTML and Javascript Library report. Several of the reports which referred to the subroutines included in the GEN - HTML and Javascript Library generated error messages when rebuilt from the Hierarchical Filing Structure Table, ^ahfs. The following error messages were received:

Error: Mainline: Data dictionary...

Error: Mainline: Field 'title' not available…

Error: Subroutine "allergy display": Data dictionary…

Error: Mainline: Database does not exist

Error: Mainline: External subroutine call report does not exist

Cause

The Item ID defined for the GEN - HTML and Javascript Library report was updated in the 6.0.1.14 and 6.0.1.21 releases; however, additional references within the reports to the subroutines defined in the GEN - HTML and Javascript Library and GEN - Medication/IV Report (rev2) reports were not updated to refer to the new version of the report.

Resolution

The Item ID for the GEN - HTML and Javascript Library report has been updated to gen.html.js.lib and the related reports have been updated to refer to this updated version of the report. Reports affected include the following:

GEN - HTML and Javascript Library (gen.html.js.lib)

GEN - Medication/IV Report (rev2)




843916 Summary

Onset Date does not display for a problem in the GEN – HTML Clinical Information Reconciliation Hook Report.

Symptoms

The issue occurred when users imported a Consolidated-Clinical Document Architecture (CCDA) document, and selected the Display Document(s) button in the Clinical Information Reconciliation application, and selected a problem from a Visit Summary document. After saving the document, users reviewed the Clinical Information Reconciliation event from the Chart Review menu function and selected the multimedia field which stored the GEN – HTML Clinical Information Reconciliation Hook Report. The Problems section displayed Onset Date numbers that were not in a standard date format.

Cause

The GEN – HTML Clinical Information Reconciliation Hook Report was not defined to display the expected date format for the Onset Date.

Resolution

The GEN – HTML Clinical Information Reconciliation Hook Report has been updated to display the expected date format for the Onset Date. Once this update is applied, the GEN – HTML Clinical Information Reconciliation Hook Report needs to be rebuilt.

844728 Summary

An Uncaught Exception Java error occurred when users right-clicked on a problem in the Problem List application.

Symptoms

When a user attempted to launch the right-click menu by right-clicking on a patient problem in the Problem List application, an Uncaught Exception Java error occurred.

Cause

The error occurred when a problem was right-clicked for a patient that did not have a visit that was a Lifecare visit type.

Resolution

When the user right-clicks on a problem for a Lifecare visit type, Java errors no longer occur in CDA.




845336 Summary

During order entry, users received a Java error, Uncaught Exception when selecting the Reason for Orders field created from the Order Entry Profile Table, ^nt(“op”), Controlled Vocabulary data element.

Symptoms

The error occurred when users selected the Reason for Orders field when entering orders for procedures in the Order Entry Application. The Reason for Orders field is created from the Order Entry Profile Table, ^nt(“op”), Controlled Vocabulary or Controlled Vocabulary (Proc Specific) data elements. Order profiles are linked to procedures in the Procedure Table, ^t, Order Information screen, Order Profile field.

Cause

When the Controlled Medical Vocabulary (CMV) code was loaded or updated at a client site, the Problem List Inactive Code Search menu function was not used. The Problem List Inactive Code Search menu function allows clients to determine which codes have become inactive following updates to coding scheme tables or to the Controlled Medical Vocabulary server. Inactive CMV items were not addressed, creating an empty value in the problem list global since that problem was not properly inactivated.

Resolution

If an inactive CMV code is linked to an active problem for the patient and that problem is defined in a field created from the Order Entry Profile Table, ^nt(“op”), Controlled Vocabulary or Controlled Vocabulary (Proc Specific) data elements, errors no longer occur and the order can be accepted.

This issue does not negate the need for the use of the Problem List Inactive Code Search menu function.

For more information, see the Problem List Inactive Code Search chapter in the QuadraMed CPR Patient Data Review Function Reference.









838348 Summary

Unchanged/uncorrected order fields displayed incorrectly in bright (black) text in the Department Order Review Queue menu function (DORQ), Department Order Review by Patient menu function, and in the Department Order Review Queue application.

Symptoms

This issue occurred when a field created from the Order Entry Profile Table, ^nt(“op”), When data element was changed/corrected in the Order Entry menu function and application, and other fields documenting dosage and route values were left unchanged. When the order was reviewed in the Department Order Review Queue menu function, the fields containing the dosage and route values displayed in bright (black) text even though they had not been previously changed/corrected.

Cause

Changes made to correct the display of field values for results in Update 6.0.1.19 inadvertently changed the display of values for orders that had been modified.

Resolution

When changes/corrections are made to fields created from the Order Entry Profile Table, ^nt(“op”), data elements, the standard display in QCPR now displays the changes/corrections in bright (black) text and unchanged/uncorrected values in dim (blue) text. The Order Entry menu function and application now store the appropriate text display value according to standard display rules.

841167 Summary

When an event was cancelled in the Medication/ IV Administration menu function, a free-text cancel comment was allowed even though the Procedure Table, ^t, Cancel/Resolve/Reschedule Information screen, Allow Cancel Freetext? field was defined as no.

Symptoms

This issue occurred when the Procedure Table, ^t, Cancel/Resolve/Reschedule Information screen, Allow Cancel Freetext? field was defined as no for a procedure. When an event for a procedure was cancelled in the Medication/ IV Administration menu function, the option to enter a free-text comment displayed in addition to selecting an option from the selection screen defined in the Medication/ IV Administration menu function, Cancel/Reschedule Params push parameter, Cancel Comment Screen field.

Cause

The Procedure Table, ^t, Cancel/Resolve/Reschedule Information screen, Allow Cancel Freetext? and Allow Cancel Multi-Select? fields were added in Update 6.0.1.8. The Medication/ IV Administration and Medication Administration menu functions allowed the user to enter a freetext cancel reason when medications selected for barcode administration were cancelled even though the Procedure Table, ^t, Cancel/Resolve/Reschedule Information screen, Allow Cancel Freetext? field was defined as no. Barcode administration was allowed when the Medication/IV Administration menu function, Barcode Parameters push parameter, Allow Barcoding? field and Medication Administration menu function, Barcode Parameters push parameter, Allow Barcoding? field were defined as yes.

Resolution

The Medication/ IV Administration menu function has been updated to recognize the Procedure Table, ^t, Cancel/Resolve/Reschedule Information screen, Allow Cancel Freetext? and Allow Cancel Multi-Select? fields so that the System only displays the ability for free-text entry when the Allow Cancel Freetext? field is defined as yes.




842396

Summary

Krames Patient Education documents did not print for Spanish language documents.

Symptoms

When a user attempted to document results in a result profile containing the Assessment Category/Data Element Table, ^nt("ac"), Patient Education data element, and selected one of the Spanish languages for the Patient Education document and chose to print the document, the document did not print. When the same document was selected in the English language, the document printed as expected.

Cause

The Caché job defined to remove the temporary file created when a print request was initiated prematurely removed the file before the print request was able to complete.

Resolution

The Assessment Category/Data Element Table, ^nt("ac"), Patient Education data element has been updated to delay the removal of the temporary file until the patient education document has printed. Krames Patient Education document print requests for all language documents now complete as expected.

842900 Summary

The Clinical Quality Measures Run menu function (eCQM) was not evaluating data correctly when the data included documented unscheduled procedures.

Symptoms

When running the eCQM for any measure, patients who had documentation needing to be evaluated by the quality measure were not being included in the measure as expected.

Cause

The eCQM looked for documented results that were associated with an order. In this issue, certain procedures were being documented as unscheduled procedures in the Unscheduled Procedure menu function and did not have an associated order. Because of this, the documented results were not being included and evaluated for measures.

Resolution

The eCQM now evaluates patient results for procedures documented as unscheduled procedures and includes these procedures in measures as expected.

843117 Summary

Info button did not return all Patient Education materials when multiple medications were selected.

Symptoms

This issue occurred when the user attempted to document a result profile containing the Assessment Category/Data Element Table, ^nt("ac"), Patient Education data element in the Work Queue, Patient Schedule, Kardex, and Unscheduled Procedure menu functions and selected patient education material for multiple medications. When the user clicked the Info button, the available options only returned one result which was not able to be selected.

Cause

The Info button returned results from the Medline Patient Education Web Service based on the RxNorm code defined in the Product Table, ^pt(“p”), System-specific level, Drug Classification Information - Wolters Kluwer DKV screen, RxNorm field. For multiple medications, only the last entry identified was returned, which was not the expected result.

Resolution

The Info button has been updated to incrementally search patient education materials available and return multiple results to match material available.




843156 Summary

Duplicate barcode values were defined for different products.

Symptoms

Products displayed duplicate barcodes in the Product Table, ^pt(“p"), System-specific level, Product Identification screen, Primary Barcode ID and Secondary Barcode ID(s) fields and in the Product Pricing Barcode Maintenance application, Product Barcode List.

Cause

When the Clinical Desktop Application (CDA) was updated to CDA build 6.0.1.57 and higher in Update 6.0.1.19, the System was updated to check the Product Table, ^pt(“p”), and Product Pricing Barcode Maintenance application for duplicate barcodes, and to check user sessions for new barcode entries that had not yet been filed. When the user entered a duplicate barcode, the System should have displayed the warning message: Product barcode currently being used by another user, and prevented the user from filing the new barcode.

In this issue, when the user accessed the Product Pricing Barcode Maintenance application, defined a barcode for one product, and then proceeded to add another different barcode to a different product in the Product Pricing Barcode Maintenance application, the System did not clear values stored in memory when entering barcodes for multiple products. This allowed a duplicate barcode to be associated to another product.

Resolution

The Clinical Desktop Application (CDA) has been updated with CDA build 6.0.1.63 and higher versions. The Product Pricing Barcode Maintenance application now checks user sessions for what has been entered as a new barcode and clears all previous entries in System memory. When the user enters multiple barcodes for multiple products, the System now checks and files only the appropriate entries.




842377

842545

842552

842753

842834

842901

843203

843226

842753

843615

Summary

Charges did not file when a result profile was documented in the following result entry menu functions that contained an undefined inclusion expression where the posting event was satisfied:

Result Entry (Equiv Results w/Selection) menu function

Result Entry (Equiv Results) menu function

Result Entry (Multiple Events) menu function

Result Entry (Specimen First) menu function

Symptoms

For any procedure where an inclusion expression was defined in the Procedure Table, ^t, Charge/Cost Information screen, Charge Definition field, Inclusion subfield, no charges were posted when the field contained an undefined inclusion expression where the posting event was satisfied.

Cause

Due to changes made in the 6.0.1.14 Update, in order for the System to evaluate multiple inclusions defined in the Procedure Table, ^t, Charge/Cost Information screen, Charge Definition field, Inclusion subfield, when more than one charge option was selected from a field created using the Result Entry Profile Table, ^nt(“rp”), Selection Table data element, the evaluation of multiple and undefined inclusion expressions was negatively impacted. This occurred when the inclusion expression was defined as <nttField>=<value> in the Procedure Table, ^t, Charge/Cost Information screen, Charge Definition field, Inclusion subfield, and this expression would fail to generate charges.

Resolution

Changes made in the Updates 6.0.1.14, 6.0.1.18, and 6.0.1.19 related to inclusion expression evaluation have been removed, with the exception of changes made to correct an issue in Update 6.0.1.18 involving an error in the Error Log Display menu function for a Language Syntax Error in the routine npc3.

Inclusion expressions defined in the Procedure Table, ^t, Charge/Cost Information screen, Charge Definition field, Inclusion subfield now evaluate according to the rules defined in the “Quantity and Inclusion Calculations” section of the Charge/Cost Information Screen chapter of the QuadraMed CPR Procedure Table Reference.

For inclusion expressions containing multiple inclusions defined in the Procedure Table, ^t, Charge/Cost Information screen, Charge Definition field, Inclusion subfield, when more than one charge option is selected from a field created using the Result Entry Profile Table, ^nt(“rp”), Selection Table data element, the recommended expression should now be defined as $$zpf^%zu2f(<nttField>,$c(1),<value>) or $c(1)_<nttField>_$c(1)[($c(1)_<value>_$c(1)).




843663

843950

Summary

Home medications copied to visit orders displayed frequencies as fractional time periods.

Symptoms

When a home medication with a frequency containing a whole time period, such as “every 2 hours” entered in a field created from the Order Entry Profile Table, ^nt(“op”), When data element, was copied to a visit order for a home or discharge medication, the Consolidated Medication List application displayed the value as “every 2.0 hours.” This also displayed incorrectly in the Order Entry application, Order History and Consolidated Medication List tabs, and in the pharmacist’s unverified orders queue, causing a processing delay.

Cause

The Consolidated Medication List application was updated in Update 6.0.1.14 to translate fractional hour time frequencies to the equivalent in minutes for order profiles containing fields created from the Order Entry Profile Table, ^nt(“op”), When data element. When a home medication was copied to a visit order with a frequency entered in a field created from the Order Entry Profile Table, ^nt(“op”), When data element with a whole time period, such as “every 2 hours”, the Consolidated Medication List application displayed the value as “every 2.0 hours.”

Resolution

The Consolidated Medication List application has been updated in CDA builds 6.0.1.61 and higher to translate frequencies with a fractional time period (e.g., every 2.5 hours) and to display frequencies with a whole time period (e.g., every 2 hours) correctly.









841494

842920

843383

Summary

When a user launched the Audit Viewer application, an error message displayed and prevented access to the application.

Symptoms

Upon launching the Audit Viewer application, the user received the following error message:

QuadraMed.Service.Library.ServiceException: Search Audit Log<Fault xmlns="http://www.w3.org/2003/05/soap-envelope"><Code><Value>Receiver</Value></Code><Reason><Text xml:lang="">CSP Gateway Error (version:2012.2.5.962.0.13054 build:1202.1315b)</Text>

The error message prevented the Audit Viewer application from launching.

Cause

The algorithm used by the Audit Viewer application to build the list of audit log events within the start and stop timestamps exceeded the InterSystems Caché 48 MB job memory process limit. As a result, the Audit Viewer application generated an error message and did not return any data.

Resolution

Clinical Desktop Application (CDA) build 60 has been updated to allow the Audit Viewer application to build the lists without generating an error message. The Audit Viewer application will display audit log events in increments maintaining the 48 MB memory process limit. For start and stop times which contain large numbers of events, only a limited number will display on each scrolling display screen.

841956 Summary

The Clinical Quality Measures Run menu function (eCQM) did not separate multiple visit admission times for patients in the reporting period when evaluating the Venous Thromboembolism Prophylaxis (VTE1) Quality Measure.

Symptoms

When the Clinical Quality Measures Run menu function (eCQM) ran for the Venous Thromboembolism Prophylaxis (VTE1) Quality Measure, the evaluation failed patients with two or more visits within the reporting period, even though the patients met the requirements to pass the measure.

Cause

When running the VTE1 Quality Measure, one criteria of the eCQM tool identifies the discharge time of a visit. If there is an EP visit type followed by the admission of an IP or OP visit type, the criteria adds the admission and discharge times to the measure for that patient visit. The issue occurred when a visit type that became active at a later time was included in the same measure for multiple active visits within a specified reporting period (e.g., 30 days). This resulted in the failed measure.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated to evaluate a patient with two visits. The first visit location type conversion time difference updates correctly with the second visit location type conversion time, allowing the quality measure to be evaluated according to the regulatory requirements.




842147 Summary

Update to patient’s e-mail address in QCPR Registration did not update their patient account in the Patient Access Account Manager application.

Symptoms

In QCPR, patient e-mail addresses are stored and updated in fields created from the Registration Screen Sequence Table, ^rt("rs"), Patient E-Mail data element. Alternatively, the e-mail addresses can be updated or corrected in a separate registration system and sent to QCPR via an HL7 ADT interface. In this issue, the HL7 ADT interface updated a new e-mail in the patient registration record in QCPR, but did not update the patient’s account in the Patient Access Module once the account had been created.

The patient did not receive an e-mail notifying them of an account creation in the Patient Access Module since the e-mail was not associated to the account.

Cause

The Patient Access Account Manager application checks for updates to a patient’s demographic information (including e-mail) each time the patient’s account is accessed in QCPR. An issue occurred with the check and updates to patient e-mail in QCPR did not carry over to the patient’s Patient Access account.

Resolution

The System now updates a patient’s e-mail from the Edit Registration menu function when an interface message is received for patient accounts created in the Patient Access Account Manager application.




842837

842624

Summary

Reports which referenced the GEN - HTML and Javascript Library report generated errors when the reports were rebuilt after a database roll.

Symptoms

The Historical Medication Package uses a group of subroutines which enable the reports in the package to execute properly. The majority of the subroutines used in the report package are in the Hierarchical Filing Structure (HFS), GEN - HTML and Javascript Library report. Several of the reports which referred to the subroutines included in the GEN - HTML and Javascript Library generated error messages when rebuilt from the Hierarchical Filing Structure Table, ^ahfs. Several different error messages were received:

Error: Mainline: Data dictionary...

Error: Mainline: Field 'title' not available…

Error: Subroutine "allergy display": Data dictionary…

Error: Mainline: Database does not exist

Error: Mainline: External subroutine call report does not exist

Cause

The Item ID defined for the GEN - HTML and Javascript Library report was updated in the 6.0.1.14 release; however, additional references within the reports to the subroutines defined in the GEN - HTML and Javascript Library were not updated to refer to the new version of the report.

Resolution

The Item ID for the GEN - HTML and Javascript Library report has been updated to “gen.html.js.lib” and the related reports have been updated to refer to this updated version of the report. Reports affected include:


GEN - Event Result View

GEN - Medication/IV Dose Summary

GEN - Medication/IV Report

GEN - Never Administered Discontinued Orders

GEN - Routine Blood Trends

GEN - Trend Report




843111 Summary

Reports defined with the visit:event:result:assessment result record generated a report build error, Unimplemented Atom.

Symptoms

Reports defined with the visit:event:result:assessment result record generated a report build error, Unimplemented Atom in module ahfs%xxxx

Cause

The visit:event:result:assessment result and visit:event:result:assessment result:field records did not reference the appropriate virtual structure in the Report Formatter Data Dictionary Table, ârfd.

Resolution

The visit:event:result:assessment result and visit:event:result:assessment result:field records have been updated to reference the appropriate virtual structure in the Report Formatter Data Dictionary Table, ârfd.

843386 Summary

The Patient Access Account Manager application, Account Summary, Patient Summary, and Registration reports changed report definition after a rollover.

Symptoms

After a rollover, the reports defined in the Patient Access Account Manager application, Non-facility preferences, Account Summary Report, Patient Summary Report and Registration Key Report fields changed to different reports than were previously defined.

Cause

Internal keys for reports in the Hierarchical Filing Structure Table, âhfs, may vary between Production (PROD) and Development (DEV) domains. The Hierarchical Filing Structure Table, âhfs, internal keys were stored in the Patient Access Account Manager, Non-facility preferences, Account Summary Report, Patient Summary Report and Registration Key Report fields. During a rollover, the internal keys from the PROD domain were overwritten with the keys from the DEV domain, resulting in the mismatch.

Resolution

The Patient Access Account Manager application has been updated to store the Report ID in the report definition table structure. When rollovers are performed, the definition of the Account Summary Report, Patient Summary Report and Registration Key Report fields now remain defined.

The Patient Access Account Manager application, Non-facility preferences, Account Summary Report, Patient Summary Report and Registration Key Report fields must be re-defined for this change to take effect. If these fields are not redefined, users may receive an "Invalid Report definition!" error message when these reports are run from the Patient Access Module Patient Web application.




843453 Summary

When creating a visit summary in the Document List application, the error message Error Refreshing document displayed.

Symptoms

In the Document List application, the creation of a Consolidated-Clinical Document Architecture (CCDA) document failed and the following error message displayed:

QuadraMed.Service.Library.ServiceException: Bad xml, xml=ctions</content></th></tr></thead><tbody><tr><td>Normal delivery</td><td>RTC 6 wks, Preeclampsia S&S discussed System.Xml.XmlException: An error occurred while parsing EntityName. Line 1, position 13041.

The error message prevented the completion of the document creation.

Cause

This issue occurred when the Document List application encountered an Instructions field entry in the Plan of Care section containing a value with a reserved XML symbol. An error occurred because the Instructions field was not formatted to replace the reserved character in XML.

Resolution

When creating CCDA documents, the Document List application converts reserved characters when the patient has an active problem on their problem list containing reserved XML symbols in the Instructions field.









841095 Summary

Data documented using the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element with a defined face sheet storage did not display in a field created from the Result Entry Profile Table, ^nt(“rp”), Display Only (Face Sheet) data element.

Symptoms

The face sheet storage defined in the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element, Face Sheet Constants field was not populating a field created using the Result Entry Profile Table, ^nt(“rp”), Display Only (Face Sheet) data element that is defined with the same face sheet in the Face Sheet Reference Constants field.

Also, when the same face sheet data element is defined in a screen sequence in the Face Sheet Table, ^nt("fs"), the screen did not rebuild and the build job resulted with an error in the Error Log Display menu function.

Cause

The data storage and display structures for the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element and any Display Only (Face Sheet) data element populated by data documented using the Controlled Vocabulary data element was not appropriately displaying this data.

Resolution

The affected data storage and display structures have been modified. Data documented using the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element with defined face sheet storage now displays correctly in the Result Entry Profile Table, ^nt(“rp”), Display Only (Face Sheet) data element, face sheet screen sequences, and any other location where face sheet data elements are used. When added to face sheet screen sequences, the screens now build without error.

842740 Summary

When a user launched the Staff Queue Assignment By Employee menu function, the user received the Java exception error message Null Pointer Exception.

Symptoms

An employee was assigned by another employee from the Staff Queue Assignment By Employee menu function to a location that contained a patient. The employee was then assigned to a location without a patient. When the employee who was assigned in the Staff Queue Assignment By Employee menu function selected the same menu function from their desktop, the Java exception error message Null Pointer Exception displayed.

Cause

The Java exception error message Null Pointer Exception displayed because the Staff Queue Assignment By Employee menu function did not recognize the assignment of an empty location when another location was already added.

Resolution

The Clinical Desktop Application (CDA) has been updated with CDA build 6.0.1.58 and higher to resolve this issue. The Staff Queue Assignment By Employee menu function now displays employee assignments for locations that contain patients and those that are empty when the employee is assigned to those locations in the same order respectively.




842743 Summary

Terms and Conditions statement did not display for patients upon initial login to the Patient Access Module Patient Web application.

Symptoms

When the patient accessed their account for the first time in the Patient Access Module Patient Web application, the application did not display the window displaying the site’s Terms and Conditions statement as defined in the Patient Access Module Administrative Web application.

Cause

The Patient Access Module Patient Web application did not reflect the setting in the Patient Access Module Administrative Web application when the Display Terms and Conditions at Initial Login field was defined as Yes.

Resolution

PAM Build 6.0.13.607 has been updated so that the definition for the Display Terms and Conditions at Initial Login field in the Patient Access Module Administrative Web application is appropriately used in the Patient Access Module Patient Web application.

842965 Summary


Symptoms

In the Document List application, creation of a Consolidated-Clinical Document Architecture (CCDA) document failed and the following error message displayed:

System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:59.9850000. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.


Cause

This issue was caused when the Document List application encountered a problem entry in the Plan of Care section that contained a value with a reserved XML symbol. An error occurred because the problem list entry was not formatted to replace the reserved character in XML.

Resolution

When creating CCDA documents, the Document List application now converts reserved characters when the patient has an active problem on their problem list containing reserved XML symbols.




840532

842101

842168

843551

843606

Summary

Patient search in the Patient Access Account Manager application did not find patients as expected.

Symptoms

Users were unable to create a new account for patients in the Patient Access Account Manager application. When searching for a patient by name using any of the following formats, the search failed to return any patient names even though the patient did exist in QCPR:

• Compound surnames with separate names (e.g., Rodriguez Zapatero, Jose Luis)

• Compound surnames with a period (e.g., St. Rodriguez, Jose Luis)

• Compound surnames with a hyphen (Rodriguez-Zapatero, Jose Luis)

• Name search using hyphen as a wildcard character (e.g., Rodriguez, Jose-)

Cause

The validation expression used when performing a patient search in the Patient Access Account Manager application did not allow a name search to include two-word last names containing a space, hyphen, period, or trailing hyphen. As a result, the query did not return any results.

Resolution

Patient search in the Patient Access Account Manager application now supports spacing and a trailing hyphen as a wild card for name search.


The following AF loops need to be run for this update:

1. AF loop 16 Rebuild Face Sheet Screens

2. AF loop 13 Rebuild Order Profiles

3. AF loop 14 Rebuild Result Profiles






ENH The Clinical Quality Measures Run menu function (eCQM) has been enhanced to display more information in error messages for quality measures that result in a Complete with Errors status. The error messages now display additional patient and System information, enabling system administrators and QCPR Client Support to better troubleshoot errors.

When a run completes with errors in the eCQM, the Run Information for Test screen displays additional information about the error in the following format:

Patient ID: <external patient ID> (^r code=<internal patient ID>)

Patient Name = <patient name>

Code: <error code>, Location=<error code location>

Measure=<measure id>, Class=<measure class>

Measure Name = <measure name> (NQF Number=<measure code>)

837577 Summary

Result values in the Provider Inbox application displayed in dim text that is normally used for reference range values.

Symptoms

In the Provider Inbox application, when a provider reviewed an item that included result values, the result values displayed in dim (blue) text. Displays in other applications/menu functions were not affected.

Cause

When the result was documented using one of the following result entry menu functions, the System stored an improper text display value which was interpreted by the Provider Inbox application:





Resolution

When result values are immediately followed by the reference range, the standard display in QCPR lists the result values in bright (black) text and the reference range in dim (blue) text. The following result entry menu functions now store the appropriate text display value according to the standard display rules:








841405 Summary

When launching the Department Order Review Queue application, the user received the Java exception error message Null Pointer Exception.

Symptoms

When the Application Desktop Table, ^at(“dt”), Department Order Review Queue application, Non-Facility Preferences, Default Column Selection and Display Order field was defined as default, the Department Order Review Queue application displayed the Java exception error message Null pointer Exception after the user attempted to launch the application.

Cause

The Java exception error message Null Pointer Exception displayed because the Department Order Review Queue application did not recognize the specified default data review columns.

Resolution

The Department Order Review Queue application has been updated to now accept the default option for the Application Desktop Table, ^at(“dt”), Department Order Review Queue application, Non-Facility Preferences, Default Column Selection and Display Order field.

842135

842183

843156

Summary

Duplicate barcode values were defined for the same product and in different products.

Symptoms

Products displayed duplicate barcodes in the Product Table, ^pt(“p"), Product Level, Product Identification screen, Primary Barcode ID and Secondary Barcode ID(s) fields or in the Product Pricing Barcode Maintenance application, Product Barcode List.

Cause

There were two causes found for this issue:

1. In the Product Table,^pt(“p”), if a product had one verified barcode and a new barcode was added and the user responded Yes to Add original primary barcode to secondary list?, the original barcode was added as a secondary barcode. But if in the same session, the user added more than one new barcode and each time responded Yes to make the primary a secondary barcode, the original primary barcode was added again as a secondary barcode.

2. If one user accessed the Product Pricing Barcode Maintenance application and defined a barcode for one product and a separate user added the same barcode to a different product in either the Product Pricing Barcode Maintenance application or the Product Table, ^pt(“p”), the System check did not include the barcodes that had not yet filed.

Resolution

1. The Product Table, ^pt(“p”), has been updated to prevent the duplication of barcodes when multiple barcodes are added and each is made the primary barcode in the same session.

2. The Clinical Desktop Application (CDA) has been updated with CDA build 6.0.1.57 and higher to check across the entire Product Table, ^pt(“p”), and Product Pricing Barcode Maintenance application for duplicate barcodes, and to also check user sessions for what has been entered as a new barcode, but not yet filed. When a user attempts to enter a duplicate barcode, the last user receives the warning message, Product barcode currently being used by another user and prevents the user from filing the new barcode.




842377

842545

842552

842753

842834

842901

843203

843226

Summary

Charges did not file when a result profile was documented in the following result entry menu functions that contained an undefined inclusion expression where the posting event was satisfied.





Symptoms

For any procedure where an inclusion expression was defined in the Procedure Table, ^t, Charge/Cost Information screen, Charge Definition field, Inclusion subfield, no charges were posted when the field contained an undefined inclusion expression where the posting event was satisfied.

Cause

Due to changes made in the 6.0.1.14 Update, in order for the System to evaluate multiple inclusions defined in the Procedure Table, ^t, Charge/Cost Information screen, Charge Definition field, Inclusion subfield, when more than one charge option was selected from a field created using the Result Entry Profile Table, ^nt(“rp”), Selection Table data element, the evaluation of undefined inclusion expressions was negatively impacted.

An error was also generated in the Error Log Display menu function for a Language Syntax Error in the routine npc3 due to the changes made to correct this issue in the 6.0.1.18 Update.

Resolution

The System now checks if an inclusion expression is undefined or has two or more entries. When a user documents an event in one of the result entry menu functions that is defined to satisfy a posting event and where one or more inclusion expression(s) are defined in the Procedure Table, ^t, Charge/Cost Information screen, Charge Definition field, Inclusion subfield, charges will generate as expected. The Error Log Display menu function now no longer displays a Language Syntax Error in the npc3 routine.

841880

843124

Summary


Symptoms

In the Document List application, creation of a Consolidated-Clinical Document Architecture (CCDA) document failed and the following error message displayed:

QuadraMed.Service.Library.ServiceException: <Fault xmlns="http://www.w3.org/2003/05/soap-envelope"><Code><Value>Receiver</Value></Code><Reason><Text xml:lang="">Server Application Error</Text></Reason><Detail>

<error xmlns="http://quadramed.com/clindoc/">

<text>ERROR #5002: Cache error: <ILLEGAL VALUE>zConvertDTExToEx+32^qcpr.clindoc.act.ActManager.1</text>


Cause

The System stored event dates for a visit included in the CCDA with a space character in addition to the date. The error message displayed because the field contained an unexpected character with the expected date when generating the CCDA.

Resolution

The Document List application has been updated to convert any dates to the expected System format when creating a CCDA document.





833289 Summary

Continuity of Care Document Architecture (CCDA) document did not display “Results Pending” suffix for microbiology procedures whose result profiles contained a Result Entry Profile Table, nt(“rp”), Multiple Fields data element.

Symptoms

A microbiology lab test procedure was defined with a result profile containing the Result Entry Profile Table, ^nt(“rp”), Multiple Fields data element. The procedure was defined with a chart review group linked to the System Parameter Table, ^%z, Order Comm System Parameters subfile, System-specific level, Laboratory Parameters screen, CCD Results Section Review Group(s) field.

When a Visit Summary document was created in the Document List application for a visit where the microbiology procedure was ordered, the document did not display with a Results Pending suffix even though the procedure was in a Partial or In Progress status.

Cause

The Document List application did not evaluate Result Entry Profile Table, ^nt(“rp”), Multiple Fields data element types when creating the Results section of a document.

Resolution

The Results section now includes pending lab tests for procedures defined with a result profile containing Result Entry Profile Table, ^nt(“rp”), Multiple Fields data elements. The names of these tests now include the suffix Results Pending when a Visit Summary document is created in the Document List application.

834275

836446

Summary

Dosage change to an effective future date/time for a PRN frequency displayed as changed immediately without meeting effective change time.

Symptoms

When a dosage change was performed in the Medication/IV Administration menu function (eMAR) and in the Order Entry menu function and application with an effective future date/time for a PRN frequency, the dosage change displayed immediately in the Medication/IV Administration menu function (eMAR).

When a dosage change was performed in the Patient Schedule menu function with an effective future date/time for a PRN frequency, the dosage change displayed only when the effective time had been met.

Cause

The Medication/IV Administration menu function (eMAR) and the Order Entry menu function and application did not appropriately update to only display the change when the effective change time was met.

Resolution

The Medication/IV Administration menu function (eMAR) and the Order Entry menu function and application have been updated to only display changes when the effective change time is met.




838158 Summary

Face sheet screens did not display appropriately in the output of the GEN DBASE - Face Sheet Data Element(s) Linked to Face Sheet Screens report.

Symptoms

When the GEN DBASE - Face Sheet Data Element(s) Linked to Face Sheet Screens report was executed, the report did not display all face sheet data elements as defined in the Face Sheet Table, ^nt(“fs”), Screen Sequence Definitions subfile.

Cause

Face sheet data elements defined on face sheet screens were not appropriately referenced in the Report Formatter Data Dictionary Table, ârfd.

Resolution

The Report Formatter Data Dictionary Table, ârfd, face sheet screen:screen:field record now allows for definitions of face sheet screen sequences and face sheet data elements. The GEN DBASE - Face Sheet Data Element(s) linked to Face Sheet Screens report is updated to utilize the updated face sheet screen:screen:filed record.

835255

839204

Summary

When executing the report GEN - HTML Patient Medication Discharge Instruction Report (rev3.1), the Quantity field in the output of the report did not display the documented quantity.

Symptoms

In the output of the GEN - HTML Patient Medication Discharge Instruction Report (rev3.1) report, the Quantity field did not display the ordered quantity for medications ordered using the Order Entry application’s prescription writing features. Prescriptions are ordered in the Order Entry application when the Order Entry application, Non-Facility Parameters, Primary Order Type field is defined as prescription.

Cause

The Quantity field on the GEN - HTML Patient Medication Discharge Instruction Report (rev3.1) did not reference the patient:medication archive:medication:Rx quantity display string record in the Report Formatter Data Dictionary, ârfd, for quantities ordered using the Order Entry application.

Resolution

The Quantity field used on the GEN - HTML Patient Medication Discharge Instruction Report (rev3.1) has been updated to reference the Report Formatter Data Dictionary, ârfd, patient:medication archive:medication:Rx quantity display string record for quantities ordered using the Order Entry application.

842363

842427

Summary

The Ordered By field in Continuity of Care Document Architecture (CCDA) Visit Summary documents, under the Medications section for each medication order, displayed the title of the user as “MD” regardless of the employee’s defined title in the Employee/Provider Table, âe.

Symptoms

When creating a Visit Summary document, the Author field displayed the correct academic or professional title in the Name column. In the Medications section of the Visit Summary document, the Ordered By field displayed with an incorrect academic or professional title.

Cause

The Document List application did not collect the title as defined for the user in the Employee/Provider Table, ^ ae, Employee-specific level, Title field.

Resolution

The Ordered By field in CCDA documents now displays the appropriate title for any user who orders medications using the Order Entry menu function and application, and Consolidated Medication List application. Any CCDA document created using the Document List application with an incorrect title for the Legal Authenticator field prior to this update needs to be generated again after the update has been applied.




842516

842588

842704

Summary

When creating a discharge summary document in the Document List application, Continuity of Care Document (CCD) generated an error message: Error Refreshing document.

Symptoms

In the Document List application, CCD creation failed and an error message displayed: System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:59.9850000. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.


Cause

This issue was caused when an e-mail address defined in the Employee/Provider Table, âe, Employee-Specific level, E-Mail Address field contained a reserved XML symbol and the Employee/Provider Table, âe, Employee-Specific level, Physician? field was defined as yes. If a provider was defined as an attending provider for a visit and a document was created with the Document List application, an error occurred because the E-Mail Address field was not formatted to replace the reserved character in XML.

Resolution

When creating CCDs, the Document List application now converts reserved characters when the Employee/Provider Table, âe, Employee-Specific level, E-Mail Address field is defined with an e-mail address containing reserved XML symbols.

842751 Summary

When creating a discharge summary document in the Document List application, Continuity of Care Document (CCD) generated an error message: Error Refreshing document.

Symptoms

In the Document List application, CCD creation failed and an error message displayed: QuadraMed.Service.Library.XmlErrorException: An error occurred while parsing EntityName. Line 1, position 4592.;Bad xml, xml='/><telecom use='WP' value='mailto: /><assignedPerson><name><given> </ System.Xml.XmlException: An error occurred while parsing EntityName.


Cause

This issue was caused when an e-mail address defined in the Employee/Provider Table, âe, Employee-Specific level, E-Mail Address field contained a reserved XML symbol and the Employee/Provider Table, âe, Employee-Specific level, Physician? field was defined as yes. If a provider was defined as an attending provider for a visit and a document was created with the Document List application, an error occurred because the E-Mail Address field was not formatted to replace the reserved character in XML.

Resolution

When creating CCDs, the Document List application now converts reserved characters when the Employee/Provider Table, âe, Employee-Specific level, E-Mail Address field is defined with an e-mail address containing reserved XML symbols.





823477 Summary

When processing requests with incomplete patient information, the eBooking Order Processor menu function resulted in an endless loop.

Symptoms

The eBooking Order Processor menu function became unresponsive when processing a request with incomplete patient information in the external scheduling queue. The same patient also had messages in the queue to cancel the original appointment and to reschedule a new one.

This issue caused the Clinical Desktop Application session to become unresponsive, lowering QCPR server performance for all users such that users could no longer access the QCPR server.

Cause

This issue occurred only when a system was defined to use the eBooking Order Processor menu function and the corresponding external data queue’s External Data Queue Table, ^at("edq"), Auto File? field was defined as yes. When there was an appointment request in the active/pending external data queue defined for the eBooking Order Processor menu function, and an appointment cancel message was received followed by an appointment reschedule request, the previous appointment was not being cancelled appropriately. Instead, the System tried to process the reschedule request first, resulting in an endless loop. The InterSystems Caché Journal rapidly filled with entries. Once the journal was 100% full, the System went into downtime.

Resolution

When the External Data Queue Table, ^at("edq"), Auto File? field is defined as yes for an external scheduling queue, the queue now first processes any pending request before executing any subsequent requests (i.e., cancel the appointment first and then process the appointment rescheduling request).

Also, when the message processing repeats the same task for more than 500 times, the System now displays an Unexpected error occurred! message in the Error Log Display menu function and terminates the task instead of running it indefinitely.




830909

Summary

Duplicate audit reports found in the Hierarchical Filing Structure Table, ^ahfs

Symptoms

When searching for reports by name in the Hierarchical Filing Structure Table, ^ahfs, the following report names were found as duplicates:

GEN - Patient Level Audit

GEN - System Level Audit

GEN - User level Audit

Cause

Pre-release versions of the reports were included in the catalog of reports delivered in the release which contained the same name but different report item ID.

Resolution

The pre-release versions have been removed from the release. The following generic reports should be used:

GEN - Patient Level Audit (gen.pat_lvl_audit)

GEN - System Level Audit (gen.sys_lvl_audit)

GEN - User level Audit Report (gen.user_lvl_audit)




837558

841295

Summary

Issue occurred in the Clinical Quality Measures Run menu function (eCQM) when evaluating the quality measure for the ‘Median Time from ED Arrival to ED Departure for Discharged ED Patients’ (ED3).

Symptoms

When using the Clinical Quality Measures Run menu function (eCQM) to evaluate the quality measure for the ‘Median Time from ED Arrival to ED Departure for Discharged ED Patients’ (ED3), the menu function evaluated the entire length of stay as part of an EP visit, including the time after the patient was transferred from the Emergency Department. In addition, there was a conflict in the measure requirements where the clinical quality measures did not classify a visit as an EP visit even though the measure should have evaluated the Transfer To marker for the following event occurrence:

1. Conversion of an observation patient from EP to OP with a documented observation order

2. Patient was checked into an ED bed

3. Patient was later transferred to a nursing unit

Cause

When a field created from the Result Entry Profile Table, ^nt(“rp”), Discharge Type data element was mapped to the Transfer To marker in the Concept Mapping Tool application, the time of the event evaluated for the Transfer To marker was not appropriately identified in the Clinical Quality Measures Run menu function (eCQM) as the transfer or check-out procedure for the EP discharge.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated when evaluating for the quality measure ‘Median Time from ED Arrival to ED Departure for Discharged ED Patients’ (ED3). The menu function now checks for the following:

A visit conversion to an IP, OP, or SP visit type

A discharge time documented within 20 minutes after the EP visit using the Result Entry Profile Table, ^nt(“rp”), Discharge Type data element

The discharge time is mapped to the Transfer To marker in the Concept Mapping Tool application

839281 Summary

User unable to create new password in the Patient Access Module Patient Web application.

Symptoms

While resetting their password in the Patient Access Module Patient Web application, the user entered the new password and the error message No such object displayed, preventing the user from resetting their password. This occurred after the user verified their likes and dislikes on the Security Likes/Dislikes page.

Cause

The user had selected a custom option on the Security Likes/Dislikes page prior to an administrator initiating the password reset. An issue occurred in the record storage for users who defined custom security preferences during account creation, which caused the error during password reset attempts.

Resolution

The Patient Access Module Update 6.0.12.606 now allows users with custom likes and dislikes on the Security Likes/Dislikes page to reset their passwords without errors.




839996 Summary

Heading for evidence-based order set with a URL link did not open webpage.

Symptoms

When an Evidence Based Order Set Table, ^nt(“oset”), Order Selection Set, Line Type is defined as heading with the Reference(s) field was defined with a URL and the URL required additional functionality (e.g., javascript) which was not available within the limited browser session used by the Clinical Desktop Application (CDA) then a webpage was not returned.

Cause

The additional functionality required for the webpage to display as expected was not available within the limited browser session used by the Clinical Desktop Application (CDA).

Resolution

CDA 6.0.1 build 55 and higher has been enhanced to launch to an Internet Explorer browser window within the Clinical Desktop Application session to allow for full browser functionality for order set headings defined with a URL in the Evidence Based Order Set Table, ^nt(“oset”), Order Set Screen field, Reference subfield.

841327 Summary

User received error message when any e-File report was executed in the E-File Application Class application.

Symptoms

When user executed an e-File report in the E-File Application Class application, the error message Abort report is not of ARF type. displayed.

Cause

The report referenced by the item ID defined in the E-File Application Class application, Facility Parameters, Report /HFS Application field, was removed from the System, causing the error message to display.

Resolution

The E-File Application Class application now requires a valid report item ID for all reports defined in the E-File Application Class application, Facility Parameters, Report /HFS Application field. When no report is defined in the field, the new error message Report not defined. displays.

841490 Summary

After a leave of absence (LOA) checkin procedure was documented, orders with a status of “LOA Hold” did not update to “Active”. Events related to the orders with a status of “LOA Hold” could not be documented after an LOA checkin event was documented.

Symptoms

Users attempted to document events associated to a leave of absence checkin procedure but found the events for the patient who had returned from a leave of absence remained in “LOA Hold” status even after documenting a LOA checkin procedure. The checkin procedure is used to document a return from LOA with the Procedure Table, ^t, Department Processing screen, Procedure Type field defined as checkin.

Cause

The LOA checkin procedure was defined as an associated procedure to another associated procedure. Because of this, the background job, "Update LOA hold ranges for visit", invoked from the procedure ended in an error state.

Resolution

The "Update LOA hold ranges for visit" job now supports procedures with associated procedures that also have associated procedures. This allows all appropriate orders to go to “Active” status and events associated with these orders to be documented.




841493 Summary

The Allow Multimedia Edits? field has been removed from the Device Table, âd.

Symptoms

When the default definition of the Device Table, âd, Allow Multimedia Edits? field was accepted as yes, fields created from the Multimedia data element in the Result Entry Profile Table, ^nt(“rp”), or the Assessment Category/Data Element Table, ^nt(“ac”), were not editable.

Cause

In QCPR Release 5.4.1 Update 36 and higher versions, the default setting for the Device Table, âd, Allow Multimedia Edits? field was changed from no to yes. The System displayed the default as yes; however, the table did not recognize the definition and functioned as if the field was defined as no.

Resolution

The Allow Multimedia Edits? field has been removed from the Device Table, âd. AF Loop 37 Clear Multimedia Edits Flag must be run once the update has been loaded on each domain (DEV, PROD, TEST, etc.) to clear data stored for the field. After running the loop, fields created from the Multimedia data element in the Result Entry Profile Table, ^nt(“rp”), or the Assessment Category/Data Element Table, ^nt(“ac”), can be edited from all devices.

842147 Summary

Update to patient’s e-mail address in QCPR Registration did not update their patient account in the Patient Access Account Manager application.

Symptoms

In QCPR, patient e-mail address is stored and updated using a field created from the Registration Screen Sequence, ^rt("rs"), Patient E-Mail data element. Alternatively, the e-mail address can be updated or corrected in a separate registration system and sent to QCPR via an HL7 ADT interface. When sent from a separate registration system, the new e-mail updated the patient registration record in QCPR, but did not update the patient’s account in the Patient Access Module once the account had been created.

The patient did not receive an e-mail notifying them of account creation in the Patient Access Module as the e-mail was not the e-mail associated to the account.

Cause

The Patient Access Account Manager application checks for updates to a patient’s demographic information (including e-mail) each time the patient’s account is accessed in QCPR. An issue occurred with the check such that the updates to patient e-mail in QCPR did not also update the patient’s Patient Access account.

Resolution

Updates to a patient’s e-mail from interface messages are now reflected in the patient’s Patient Access account.



5.4 AF loop 36 ‘Update Order subscript for sub area and sub-sub area’

5.4 AF loop 37 ‘Clear multimedia edits flag’

5.4 AF loop 38 ‘Update âfa sub area and sub-sub area’

6.0 AF loop 14 ‘Rebuild Result Profiles’

6.0 AF loop 15 ‘Rebuild Assessment Profiles’






ENH In QCPR 6.0.1 update 16 (Case 839469) an update was made to address the issue where the Consolidated Clinical Document Architecture (CCDA) document displayed only no known allergies when NKDA, NKLA, and NKSA were documented. A similar change was also required to the Clinical Information Reconciliation (CIR) application to avoid having these entries blank in the CIR application. This enhancement will default the display name in the CIR application based on the changes in made for Case 839469 so that it is clear to the user it is a “No Known” allergy for each allergy type is that is documented. The ability to reconcile the “No Known” allergies from the external document to the current patient information in QCPR within the CIR is disabled.

822975 Summary

The GEN - Patient Audit Trail~ report failed to execute.

Symptoms

When a user executed the GEN - Patient Audit Trail~ report to a printer from the Hierarchical Filing Structure Table, ^ahfs, on a production domain, the print job never completed. When a user executed the same report to a printer from the Hierarchical Filing Structure Table,^ahfs, on their development domain, the report printed as expected.

Cause

The GEN - Patient Audit Trail~ report was designed to gather data from all visit records on the System during execution. Due to the large number of visit records in the production environment, the report first appeared to not have printed. However, after several days of executing, the report printed. Development domains did not exhibit the same issue as there are significantly fewer patient visit records stored on the System.

Resolution

The report has been modified to filter the number of visit records with criteria to limit the number of iterations through the visit records. The GEN - Patient Audit Trail~ report and screen driver must be rebuilt manually once the update has been applied.

831845

836574

836583

Summary

Patient cautions or allergies did not consistently update

Symptoms

For Face Sheet Storage Links defined in the System Parameter Table, %z, REG/ADT System Parameters subfile, Facility-specific level, Header Strip Definitions screen, Patient Med Allergies and Other Caution(s) fields, Face Sheet storage did not display current documented data as documented.

Cause

An issue was identified in the Result Entry Profile Table, ^nt(“rp”), Selection Table data element field. When the Selection Table data element was defined with a Face Sheet storage, the data was not cleared consistently upon selection for multiple fields data element configured on the result profile or assessment through assessment category that is defined as patient or visit historical.

Previously reported resolution from Update 6.0.1.8 has been updated based on additional investigation.

Resolution

Face Sheet storage for the Result Entry Profile Table, ^nt(“rp”), Selection Table data element and the Assessment Category/Data Element Table, ^nt("ac"), Allergy Name data element will now update consistently upon selection in the Patient Schedule menu function.




839107 Summary

Additional Charge(s) result profile data element search failed on a non-English implementations of QCPR.

Symptoms

This issue occurred for systems with the System Parameter Table, ^%z, System-specific level, System Language field defined as Quebec French. When documenting a Result Profile, ^nt(“rp”) that contained the Additional Charge(s) data element, no results would be returned when the user would attempt to add a charge and do a partial name search for the charge name. This would occur despite the fact that performing the same search in the Charge/Cost Table, ^nt(“c”) returned matching charge names.

Cause

The Charge Credit Processor was collating the search query before generating the partial name match pattern. As a result the check based on the displayed search criteria was given extra control characters at the end of the string which subsequently found no match for the entered search string.

Resolution

The Charge Credit Processor component was updated to fix the problem so the original search string would not be manipulated and the partial name search will return matching charges when present.

841088 Summary

When viewing a previously documented field via the Chart Review menu function, a field that previously displayed would no longer be visible.

Symptoms

When viewing a previously documented assessment from the Chart Review or Patient Schedule menu functions, an assessment field that previously displayed and contained documented data within it would no longer be visible. The assessment data element field and the data documented could be seen when in edit mode within the Patient Schedule menu function.

Cause

This issue is caused a specific parameter that contained the event date/time stamp was not being passed to the record which determined whether or not results could be viewed when the Assessment Data element on the Assessment screen contained an allowed security expression that is based on a time comparison for the data element. Allowed security expressions are defined in the Assessment Screen Table, ^nt("as"), Assessment Screen, Vertical Screen Driver Sublevel, Assessment Data element screen driver field, Expressions.

The event date/time stamp of the event is part of the logic to determine whether or not the data element would display based on the Allowed Security expression logic which was using a date/time comparison. Since this piece of data was missing the expression always evaluated as False and thus did not allow the field to display in review functions.

Resolution

The code has now been updated to include the parameter where event date/time stamp is stored. This will allow the date/time comparison to be properly evaluated as True or False and display as expected.




841572 Summary

Patients could not be added to PAM Manager as names were not found.

Symptoms

Users were unable to create a new account for patients in the Patient Access Account Manager application (PAM). When searching for a patient by name, the user entered the name using format "last,first-" but the system failed to return any patients even though the patient did exist in QCPR.

Cause

The Patient Access Account Manager application used a SQL query to search for patient names which was case sensitive. As a result the query did not return any results.

Resolution

The Patient Access Account Manager application Patient Name search SQL query has been updated to be case insensitive when performing a name search string is entered in lower case or mixed case text.

841986 Summary

Patient/s showing in "(F) Display Failed Patients Only" were not displaying within the main level IPP view.

Symptoms

When a Quality Measure was run using the Clinical Quality Measures menu function (eCQM), patient(s) showing in "(F) Display Failed Patients Only" were not displaying within the main level IPP view. On further examination those failed patients were in the IPP for previous eCQM runs for other quality measures.

Cause

When quality measures were run using the eCQM the data record for failed patients was not being initialized, thus included failed patients from previous runs.

Resolution

When re-running the eQCM tool after getting failed patients, the system will clear all previous failed patients before the start of the new run, so only the new failed patients will appear.




840532

841306

Summary

When Creating a User Account from Patient in Patient Access Account Management (PAM) application, the user received error message.

Symptoms

When the user in the Patient Account Manager application selected the “Create from Patient” button and searched for a patient an error message occurred after several minutes of attempted processing.

Error Message:

System.ServiceModel.ProtocolException: The content type text/plain of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 143 bytes of the response were: '

<STORE>

<ERRTRAP>

<P><P><B><FONT COLOR="RED">Error Condition</FONT></B><P>

CSP application closed the connection before sending a response'.

Cause

The Patient Access Account Manager application used a SQL query to search for patient names which did not query by an index on patient names. As a result an error message occurred because the search took longer than expected to complete.

Resolution

The Patient Access Account Manager application Patient Name search SQL query has been updated to require at least 2 characters to be entered when performing a name search









808720 Summary

Result profile displayed abnormal results as normal when the event was documented using the Result Verification menu function.

Symptoms

When a field created from the Result Entry Profile Table, ^nt(“rp”), Multiple Fields data element contained two entries, one marked as abnormal result and one containing normal result but marked as an internal result, the abnormal result displayed as normal during result review. This issue occurred when the second multiple field entry on the result profile was marked as an internal field during result entry, and displayed the abnormal result without the appropriate underline in the Provider Inbox application, Chart Review menu function, and the Interactive Care Grid application.

Cause

When multiple results were documented using the Result Entry Profile Table, ^nt("rp"), Multiple Field data element, results marked as internal removed the display indicator of results marked as abnormal.

Resolution

The Result Entry Profile Table, ^nt("rp"), Multiple Fields data element now displays abnormal results appropriately as underlined regardless of internal fields on the same result profile.

822926 Summary

Visits did not close due to active orders for Leave Of Absence (LOA) and transfer events.

Symptoms

A visit discharged while a patient was on LOA did not close and the user received a message that active orders were outstanding.

Cause

For procedures defined with the Procedure Table, ^t, Department Processing screen, Procedure Type field as LOA, visit interrupt or transfer, when the procedure is ordered in the Order Entry menu function, the System creates an LOA event on the Patient Schedule menu function. When the LOA event is scheduled, events for orders can be placed on hold when the procedure was defined in the Procedure Table, ^t, Order Scheduling screen, LOA Hold? field as yes. All events scheduled for that procedure between the LOA event time and the estimated return time are placed on hold. If the visit is discharged prior to the return time, the order event for the LOA was discontinued, however the check-in event remained on the Patient Schedule menu function.

Resolution

The Patient Schedule menu function now adds a discontinuation to the check-in event. When discontinuing orders during discharge processing, the Patient Schedule menu function does not remove an LOA, visit interrupt or transfer event.




828311

827343

Summary

When the Area Table, âfa , Sub-Area subfile was defined with more than 99 beds, the 100th bed displayed as the 11th.

Symptoms

When the Patient List application displayed a Sub-Sub-Area defined in the Area Table, âfa, Facility-specific level, Area subfile, Sub-Area subfile that contained more than 99 Sub-Sub-Areas, the 100th Sub-Sub-Area displayed after the 10th Sub-Sub-Area instead of after the 99th Sub-Sub-Area. This pushed the display of the 11th Sub-Sub-Area below the series of Sub-Sub-Areas following the 100th Sub-Sub-Area.

Cause

The Area Table, âfa, was designed for no more than 99 possible sub-locations to any location (i.e., no more than 99 sub-areas in an area (rooms in a unit) and no more than 99 sub-sub-areas in a sub-area (beds in a room). When an area has more than 99 beds, the 100th bed was inserted after bed 10 and so on based on the sorting logic.

Resolution

The Area Table, âfa, allows for a 4-digit sub-area and sub-sub-area, increasing the limit to 9999 sub-locations for each level. 5.4 AF Loop 36 'Update Order Subscript for Sub-area and Sub-sub-area' must be run after this update has been applied to modify existing entries in the Area Table,âfa.

833410 Summary

A "Coding Server Unavailable" message displayed when attempting to define a vocabulary code in the Procedure Table, ^t, Procedure Identification screen, Controlled Vocabulary field.

Symptoms

When users attempted to define specific coded vocabulary values in the Procedure Table, ^t, Procedure Identification screen, Controlled Vocabulary field, the system would present the message Coding Server Unavailable and the code could not be added to the procedure. Also, when a user tried to add or resolve a problem in the Problem List application, the same message was received and the user was unable to add or resolve a problem, despite the CMV server being available and correctly configured.

Cause

The Clinical Desktop Application (CDA) can be installed either from an executable (.exe) or a Windows (.msi) installer. When CDA was installed via the .exe installer, invalid CMV connectivity information was provided on the workstation that overrode the server-side configuration.

Resolution

The workstation override of CMV server configuration has been removed from the Clinical Desktop Application installer.




835535 Summary

Users were unable to document medication event containing PRN frequency after the start if condition is met and documented.

Symptoms

In an Order Entry Profile Table ^nt(“op”), When data element, when an order was documented in the Order Entry menu function which contained a PRN frequency with a start if and a stop if modifier, after the start if condition was documented from either the Medication/IV Administration menu function or the Patient Schedule menu function, the user was not able to document the first scheduled event because the stop if condition was then expected to be documented. This returned the user to the Medication/IV Selected for Administration screen. The medication order displayed a status of incomplete.

Cause

The Medication/IV Administration menu function or the Patient Schedule menu function found the conditional event type first and did not allow the user to document the first event. The Medication/IV Administration menu function or the Patient Schedule menu function proceeded to the documentation of the second conditional event type.

Resolution

The Medication/IV Administration menu function and the Patient Schedule menu function now checks for conditional event types (start if and stop if) when multiple conditions are ordered to allow the user to document.

838110 Summary

The GEN - Med/IV Admin Override Notification Report received a ‘build error’ message upon rebuild of the report.

Symptoms

When a user selected the (R) Rebuild button from the Hierarchical Filing Structure Table, ^ahfs, for the GEN - Med/IV Admin Override Notification Report, once the rebuild completed, the report did not execute and the user received a ‘build error’ message.

Cause

The GEN - Med/IV Admin Override Notification Report contained an expression which referred to the record HDS Department which was not available on the client system.

Resolution

The GEN - Med/IV Admin Override Notification Report has been updated to no longer refer to the HDS Department, record. The GEN - Med/IV Admin Override Notification Report must be rebuilt once this update has been loaded.




839469 Summary

Consolidated Clinical Document Architecture (CCDA) document displayed only no known allergies when NKDA, NKLA, and NKSA were documented. When an allergy was documented, the CCDA did not display any of the NKDA, NKLA, NKSA allergy documentation.

Symptoms

When the Assessment Category/Data Element Table, ^nt(“ac”), Allergy Name multiple field data element was documented with at least one no known allergies (NKDA, NKFA, NKSA, or NKLA), the allergy section of the CCDA document only displayed no known allergies and did not specify for each allergen type.

When an Assessment Category/Data Element Table, ^nt(“ac”), Allergy Name multiple field data element was documented with at least one no known allergies (NKDA, NKFA, NKSA, or NKLA), and at least one additional allergy name specified the allergy section of the CCDA document did not display any no known allergies and did not specify for each allergen type.

Cause

When an Assessment Category/Data Element Table, ^nt(“ac”), Allergy Name multiple field data element was documented with at least one no known allergies specified (NKDA, NKFA, NKSA, or NKLA), the Document List application did not create a specific entry for each allergen type when creating the allergy section of the CCDA document.

Resolution

The Document List application now creates a specific entry for each allergen type when creating the allergy section of the CCDA document, when an Assessment Category/Data Element Table, ^nt(“ac”), Multiple Field Screen Definitions subfile, Allergy Name data element is documented with at least one no known allergies specified (NKDA, NKFA, NKSA, or NKLA). The entry for each allergen type displays as documented in the Allergy Name data element.

The 6.0 AF loop 62 ‘Rebuild indices for QCPR invariant concept codes’ must be run after this update has been loaded.

839704 Summary

The Clinical Quality Measures Run menu function (eCQM) displayed complete with errors for the following Clinical Quality Measures:

Venous Thromboembolism Patients Receiving Unfractionated Heparin with Dosages/Platelet Count Monitoring by Protocol or Nomogram (VTE-4)

Incidence of Potentially-Preventable Venous Thromboembolism (VTE-6)

Symptoms

When executing Clinical Quality Measures for VTE-4 and VTE-6 in the eCQM, the menu function displayed complete with errors with the error message Patient build error Code <COMMAND>, Location=zBuildResultsForEvent+8^qcpr.build.EventsDta.1.

Cause

The eCQM received a secondary error message, Profile not imported. The error resulted because there were procedures present that did not have a result profile configured in the Procedure Table, ^t, Documentation Information screen, Result Profile/Link Information field, Result Profile subfield.

This is a valid configuration in QCPR; however, for Clinical Quality Measure evaluation, result profiles are required to be mapped to a Concept Marker in the Concept Mapping Tool application.

Resolution

The Clinical Quality Measures Run menu function (eCQM) now processes only events which have a corresponding Concept Marker mapped in the Concept Mapping Tool application and does not evaluate procedures that do not.




840269 Summary

The GEN - Med/IV Admin Override Notification Report generated for every action (except for hang, check, and take down events) performed in the Medication/IV Administration menu function.

Symptoms

The GEN - Med/IV Admin Override Notification Report is designed to execute during patient/product ID overrides. However, the report executed when no overrides occurred and both the patient and product/solution had been scanned generated for every action (hang, check, and take down) performed in the IVAR. The override is specific to Patient/Product ID Override and occurs when no override has taken place and both the Patient and Product/Solution had been scanned.

Cause

The Medication/IV Administration menu function generated an override event when a near miss event was expected, which caused the GEN - Med/IV Admin Override Notification Report to execute.

Resolution

The Medication/IV Administration menu function was changed to record an override only when a patient or product is not barcoded and triggers the report.

840612 Summary

The Clinical Quality Measures Run menu function (eCQM) failed to evaluate shared results.

Symptoms

Results were present on patient records that should have been reflected in the eCQM but were not included.

Cause

When evaluating a quality measure in the eCQM for an event documented on a result profile containing data elements with defined shared results, the eCQM failed to evaluated the shared result data. This issue applied to any result data element in the Result Entry Profile Table, ^nt("rp"), where the Shared Result Constants field is available.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated to evaluate result profiles mapped in the Concept Mapping Tool application that are defined with Shared Result Storage.

840909

841192

Summary

Invalid OREF message occurred when documenting the Assessment Category/Data Elements Table, ^nt(“ac”), Patient Education data element with content in a non-English language.

Symptoms

When a user attempted to document a result profile that contained the Assessment Category Table, ^nt("ac"), Patient Education data element, and selected one of the non-English languages for the Patient Education document, the system displayed an error message, Invalid OREF, and the document did not generate.

Cause

The Krames XML style sheet that is used for patient education materials when defined for a non-English language to display as HTML contained an attribute that did not allow for proper conversion to HTML.

Resolution

The Krames XML style sheet has been enhanced to convert the non-English language Patient Education documents to HTML without an error.




841237 Summary

Consolidated Clinical Document Architecture (CCDA) Outbound interface to a third-party patient portal stopped while transmitting a message.

Symptoms

A CCDA Outbound interface to a third-party patient portal generated an error message when attempting to transmit a message. The error message states: Error #6901: XSLT XML Transformer Error: SAXParse Exception.

Cause

Some Krames patient education documents can contain foreign language characters in the PDF which is stored in the Assessment Category/Data Element Table, ^nt("ac"), Patient Education data element. When creating a document using the Document List application for a CCDA document that contained certain foreign language characters, the CCDA document was generated with content omitted. As a result, the XML representation of the document was invalid and therefore could not be parsed by the XML parsers. A CCDA Outbound interface to a third-party patient portal attempted to transmit a message containing the compromised CCDA document and generated an error message.

Resolution

The Document List application has been updated to handle the Assessment Category/Data Element Table, ^nt("ac"), Patient Education data element which contains foreign language characters when creating a CCDA document.

841331 Summary

All quality measure runs failed to complete in the Clinical Quality Measure Run menu function (eCQM) when the Facility Table, âff, Address field, Mailing Code subfield was not defined.

Symptoms

When a user reviewed the quality measure runs in the eCQM, the runs displayed with an incomplete status.

Cause

The runs failed to complete when the Facility Table, âff, Address field, Mailing Code subfield was not defined. The eCQM was unable to handle this missing data.

Resolution

The Clinical Quality Measure Run menu function (eCQM) now processes and completes a run when the Facility Table, âff, Address field, Mailing Code subfield is not defined.




841352 Summary

The Global Size Calculation (%zgsize) background job ran for a long duration of time and consumed a significant amount of database server processor (CPU) resources.

Symptoms

When viewing the job in the Job Monitor menu function, the Global Size Calculation (%zgsize) background job ran for more than 24 hours and consumed a large number of lines (>360,000 lines). When a user reviewed that InterSystems Cache System Management Portal, Cache System Dashboard, the job displayed a large amount of processes and was identified as one of most active processes in the System Usage column.

Cause

The Global Size Calculation (%zgsize) is a job defined in the Daily Job Table, ^%zbgdj, to calculate the size of every global on a given domain and record the statistical data. It is defined to execute at midnight and displays in two places within QCPR, the Background Log. Display and the Job Monitor menu functions as well as in InterSystems Cache in the System Management Portal, Cache System Dashboard.

For some systems containing large global structures for several interface transmitters, this routine appeared to run in an infinite loop. The job, however, was running as expected but was processing redundant data stored by the interfaces. Normally, the interface would regularly purge these entries on a pre-determined interval (i.e., 30 days). It was identified that the purge routine for these interfaces did not remove the historical messages which were expected to be purged.

Resolution

Several interface transmitters have been updated to purge the messages as defined in the Interface Table, ^ati.




AF loop 59 ‘Remove deprecated screen dump security’

AF loop 61 ‘Update Order subscript for sub area and sub-sub area’

AF loop 62 ‘Rebuild indices for QCPR invariant concept codes’




ENH QuadraMed CPR now supports Integrated Medication Management (IMM) facility-specific level charging definitions for multiple facility clients who use facility-specific charging definitions. The System now uses the definition of the Product Table, ^pt(“p’), Facility-specific level, Charging & NDC(s) Definitions field to correctly calculate facility-specific pricing for IMM charges.

Users can now define a specific charge definition for each facility and/or override the price category at the facility level.

The System now uses the price category defined in the Product Table, ^pt(“p”), Facility-specific level, Charging & NDC(s) Definitions field, Price Category subfield, the IMM markup, and any defined inclusion information when calculating the patient charge for a product.

Users should define general criteria if inclusions are defined, and should also define criteria in the order in which they should be evaluated by the System.

When multiple criteria are defined for a facility in the Product Price Category Table, ^pt(“ppc”), the general criteria with no inclusions should be the last criteria on the list for evaluation.

Previously, the System was calculating facility-specific prices using the charging definition(s) defined in the Product Table, ^pt(“p’), System-specific level, Charge Information screen.

The following changes have been made to the Product Table, ^pt(“p”), to clarify how the table should be defined to support this functionality:

The System-specific level, Charge Information screen, Price Category field has been renamed Default Price Category.

The Facility-specific level, Charging & NDC(s) Definitions field, Charge Definition subfield can now only be used to define a single selection of a charge code on the facility level. This subfield no longer supports an Insert/Delete/Move editor.

When the System-specific level, Charge Information screen, Charge Definition field is defined with a charge code, lookup name, or partial charge word(s), the Facility-specific level, Charging & NDC(s) Definitions field, Charge Definition subfield displays the defined charge code but the Charge Definition subfield itself is starred out (***) and cannot be accessed for definition.

Defining the System-specific level, Charge Information screen, Charge Definition field as facility-specific retains the current functionality where the Facility-specific level, Charging & NDC(s) Definitions field, Charge Definition subfield initially displays as empty until it is defined.

The Price Category subfield has been added to the Facility-specific level, Charging & NDC(s) Definitions field. This field is used to define the facility-specific price category for the defined product and links from the Product Price Category Table, ^pt(“ppc”).

ENH Information about InterSystems Caché license usage can now be monitored and accessed from the Caché System Management Portal (SMP). With this enhancement, license traffic from any QuadraMed product (e.g., Affinity and QES) is collected and collapsed into one database. Users can execute the included Caché ZEN report as a task from the SMP to retrieve and e-mail monthly peak license activity. Users signed onto more than one QuadraMed product with enabled LDAP services are collapsed into a single count in accordance with InterSystems and QuadraMed business agreements.

Previously, the QCPR Caché License Monitor was available only in QCPR. Clients with multiple QuadraMed products needed separate Caché keys for each product, requiring manual reconciliation of the license keys from different products. With this enhancement, Caché license usage is accessible through SQL reports and clients with multiple QuadraMed products can view cross-product license usage as a single count (after meeting minimum version requirements for the QCPR LDAP services).

To view the collapsed user information, QCPR LDAP services must be implemented when they become available in a future release. However, users can execute the Monthly Peak Report with this release to assess their license usage and prepare for the consolidation of the license keys across products.




820884 Summary

Multiple charges did not file when a result profile was documented in the following result entry menu functions that contained inclusion expressions where two or more inclusions were satisfied.





Symptoms

When the user selected two or more options from a selection table in the field created with the Result Entry Profile Table, ^nt(“rp”), Selection

Table data element, Multi-Select? Constants field defined as yes, the charges defined for those two items did not file appropriately. This occurred despite the charges meeting the inclusion expressions defined in the Procedure Table, ^t, Charge/Cost Information subfile, Charge Definition field, Inclusion subfield. No charges were posted when multiple options were selected. When only one option was selected, a charge was posted.

Cause

The System did not evaluate multiple inclusions defined in the Procedure Table, ^t, Charge/Cost Information subfile, Charge Definition field, Inclusion subfield when more than one charge option was selected from a field created using the Result Entry Profile Table, ^nt(“rp”), Selection Table data element.

Resolution

The System now checks to determine if an inclusion expression has two or more entries. When a user documents a result profile that is defined to satisfy more than one inclusion expression in the Procedure Table, ^t, Charge/Cost Information subfile, Charge Definition field, charges will generate as expected.

822761 Summary

When patient bed assignment was changed using the Bed Swap menu function, the patients involved in the swap appeared twice in patient lists presented in the Patient Identification menu function.

Symptoms

Users saw the same patient listed twice in patient lists displayed in the Patient Identification menu function.

Cause

Patient visits are identified within QCPR with specific area, visit, and facility codes. When the Bed Swap menu function was used for a patient visit, the area and visit codes were duplicated for the same patient while the beds were swapped. The Clinical Desktop Application (CDA) display did not filter for a specific code, thus displaying the patient twice in the Patient Identification menu function, once for each code during the swap.

Resolution

The Patient Identification menu function has been updated in a CDA build, 6.0.1 build 45 and higher, and will now remove duplicate patients when displaying a list of patients.




828190

833544

Summary

The medication list in the Consolidated Medication List tab in the Order Entry application did not default to the current visit as defined.

Symptoms

When the Consolidated Medication List tab was accessed from the Order Entry application, the Consolidated Medication List tab launched without a selected visit and did not display any data. The user had to select the “Current” option in the Consolidated List Options filter pane, Visit(s) section and update the consolidated medication list for data to appear.

In order to access the Consolidated Medication List application from the Order Entry application, it must be defined in the Order Entry application, Non-Facility Parameters, Consolidated Med List App field. The default display for the consolidated medication list is defined in the Order Entry application, Non-Facility Preferences, Consolidated Med List Preferences field, Default Order History Visit(s) subfield. The subfield was defined as current, the System default, during this issue. However, no visit, current or past, was selected in the application when launched.

Cause

The Clinical Desktop Application (CDA) was not using the value defined in the Order Entry application, Non-Facility Preferences, Consolidated Med List Preferences field, Default Order History Visit(s) subfield. This caused the Consolidated Medication List tab to display without any of the patient’s visits selected and no data was returned.

Resolution

The Order Entry application, Consolidated Medication List tab now reflects the default visit preference defined in the Order Entry application, Non-Facility Preferences, Consolidated Med List Preferences field, Default Order History Visit(s) subfield. The Consolidated Medication List tab now opens with the appropriate visit option selected as a default and displays medications as defined for the application.

832545 Summary

Associated procedures that had the Optional Default Status subfield defined as super-proc defined did not display the documented status from the super procedure order.

Symptoms

Associated procedures that had the Procedure Table, ^t, Associated Procedure Information screen, Associated Procedure(s) field, Order Status subfield defined as optional and the Optional Default Status subfield defined as super-proc defined, did not display documented values on order profiles containing a field created from the Order Entry Profile Table, ^nt(“op”), Choose data element in the Order Entry menu function.

Cause

The Order Entry menu function did not update associated procedure orders according to the definition in the Procedure Table, ^t, Associated Procedure Information screen, Associated Procedure(s) field, Optional Default Status subfield.

Resolution

The Order Entry menu function now updates associated procedure orders according to the definition in the Procedure Table, ^t, Associated Procedure Information screen, Associated Procedure(s) field, Optional Default Status subfield.




834115 Summary

A red and white checkered box displayed on home and discharge medications with a fractional frequency in the Consolidated Medication List application.

Symptoms

Home and discharge medications displayed in the Consolidated Medication List application with a red and white checkerboard in the Information column. If an attempt was made to copy the row with the checkerboard to a visit medication, a Java error message displayed.

Cause

When an order profile containing a field created from the Order Entry Profile Table, ^nt(“op”), When data element was documented and submitted using a frequency with a fraction of a time period, such as “every 1.5 hours”, for a home or discharge medication, the Consolidated Medication List application did not translate the fractional hour time frequencies to the equivalent in minutes.

Resolution

The Consolidated Medication List application was updated to translate fractional hour time frequencies to the equivalent in minutes for order profiles containing fields created from the Order Entry Profile Table, ^nt(“op”), When data element.

835703 Summary

The Item ID for the GEN - HTML and Javascript Library report has been updated.

Symptoms

The Historical Medication Package uses a group of subroutines which enable the reports in the package to execute properly. The majority of the subroutines used in the report package are in the Hierarchical Filing Structure (HFS), GEN - HTML and Javascript Library report.

Cause

The Item ID defined for the GEN - HTML and Javascript Library report was not consistent with QCPR generic reports.

Resolution

The Item ID for the GEN - HTML and Javascript Library report has been updated to “gen.html.js.lib” and the related reports have been updated to refer to this updated version of the report. Reports affected include:


GEN - Event Result View

GEN - Medication/IV Dose Summary

GEN - Medication/IV Report

GEN - Never Administered Discontinued Orders

GEN - Routine Blood Trends

GEN - Trend Report




836343 Summary

The Problem List application erred when selecting the All Problems filtering option in the Problem Display Options filtering pane, List Display section.

Symptoms

After launching the Problem List application and choosing the All Problems filtering option to view the patient's problems across visits, a Null Pointer Exception error would display. This occurred only for some patients and not all.

Cause

When the All Problems filtering option was chosen, the application searched for an active Lifecare visit for the patient. When the patient did not have an active Lifecare visit, the application displayed the error.

Resolution

The Problem List application now checks for a patient's active visits and displays only problems for those active visits when the All Problems filtering option is selected from the Problem Display Options filtering pane, List Display section.

836854 Summary

A Java error occurred when launching the Provider Inbox Across Patients application.

Symptoms

When launching the Provider Inbox Across Patients application, the user received the Java error message: java.lang.NullPointerException.

Cause

When the ‘Recompute assessment multiple field abnormal flags’ loop was executed prior to 6.0.1 Update 13, the loop did not correct some of the events containing abnormal values stored in patient visit events documented on assessment screens containing fields created from the Assessment Category/Data Element Table, ^nt(“ac”), Multiple Fields data element. The Provider Inbox Across Patients application would err upon encountering these entries.

Resolution

6.0 AF loop 47 ‘Recompute assessment multiple field abnormal flags’ must be run after this update to correct these entries.

837113 Summary

An order with a route defined in the Route Table, ^pt(“ro”), Product Selection Type field as syringe did not perform automatic drug product selection during a change order when the administration time was changed.

Symptoms

Automatic product selection would not occur during a change order when modifying administration time for an IV syringe route defined in the Route Table, ^pt(“ro”).

Cause

When the change order was entered, the previously selected product(s) was not saved as the default, causing the user to step through the diluent and additive components of the order.

Resolution

When order administration times are changed for an order with a route defined in the Route Table, ^pt(“ro”), Route level, Product Selection Type field as syringe, previously selected products are defaulted and can be modified if needed.




837305 Summary

French characters with accents did not display correctly in the Clinical Desktop Application (CDA).

Symptoms

This issue occurred for systems with the System Parameter Table, ^%z, System-specific level, System Language field defined as Quebec French. When the user hovered the mouse cursor over the Patient Cautions header strip for Face Sheet Storage entries containing accented characters, the characters did not display as documented in the Face Sheet for face sheet storage links defined in the System Parameter Table, ^%z, REG/ADT System Parameters subfile, Facility-specific level, Header Strip Definitions screen, Patient Med Allergies and Other Caution(s) fields. For example, if the text contained a character such as é, the Patient Cautions Header Strip hover box would instead display “.

Cause

The Patient Cautions Header Strip hover box did not reflect the English-to-French translation performed by the Language Translation Table Import menu function.

Resolution

The Patient Cautions Header Strip hover box has been updated to reflect a previous translation performed by the Language Translation Table Import menu function.

837357

837683

Summary

Errors occurred during validation of Continuity of Care Documents (CCD) using the tool provided by the National Institute of Standards and Technology (NIST) in the Document List application.

Symptoms

When users tried to validate via the NIST Validator, validation failed and the user received errors.

Cause

When creating a CCD, the CCD generated then failed when trying to validate the XML via the NIST Validator when the CCD was generated for a patient that was documented with an allergy as defined in the Allergy Table, ^pt(“ad”), and the allergy was not mapped using the Concept Mapping Tool application to a corresponding procedure code. The CCD was generated without an expected indicator for the allergy and that caused the CCD to fail the validation.

Resolution

QuadraMed recommends that all allergies defined in the Allergy Table, ^pt(“ad”), are mapped to a corresponding procedure code using the Concept Mapping Tool application. The Document List application has been updated so that CCDs pass NIST validation when a patient is documented with an unmapped allergy.




839156 Summary

When using the Clinical Quality Measures Run menu function (eCQM) to evaluate the quality measure for Initial Antibiotic Selection for Community-Acquired Pneumonia (CAP) in Immunocompetent Patients (PN-6), the menu function resulted in error.

Symptoms

When using eCQM to evaluate the quality measure for Initial Antibiotic Selection for Community-Acquired Pneumonia (CAP) in Immunocompetent Patients (PN-6), the error message code <Zdoes>, Location=zGetResults+19^qcpr.qrda.rim.CodedEntry displayed.

Cause

Neutrophils are one type of white blood cell. When a Complete Blood Count (CBC) is performed, the total number of white blood cells (WBC) is reported, along with a percentage breakdown of each type of cell. The PN-6 measure evaluates for the absolute neutrophil count (ANC), not the percentage of the total number of WBCs. The ANC can be captured in two ways:

1. The hematology instrument reports the ANC through an interface.

2. A manual calculation can be performed - The absolute neutrophil count (ANC) = Total WBC x (%"Segs" + %"Bands"),

OR

WBC x ((Segs/100) + (Bands/100))

The Result Entry Profile Table, ^nt(“rp”), Numeric data element, Interface Code Constants field, UCUM Unit subfield was defined as %. However, the expected UCU Units definition for the PN-6 measure was "/mm3". eCQM generated an error message due to the mismatch of the expected UCUM Units.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated to no longer display an error message due to the mismatch of the expected UCUM Units for this measure. However, if the configuration is not defined accordingly, the measure will fail. A "no match" entry will now be logged in the eCQM debug log when this configuration is encountered.

839704 Summary

The Clinical Quality Measures Run menu function (eCQM) displayed “complete with errors” for Clinical Quality Measures VTE-4 and VTE-6.

Symptoms

eCQM displayed “complete with errors” for Clinical Quality Measures VTE-4 and VTE-6. The error message received was Patient build error. Code <COMMAND>, Location=zBuildResultsForEvent+8^qcpr.build.EventsDta.1.

Cause

eCQM received an error message, Profile not imported. The error resulted because there were procedures present that did not have a result profile configured in the Procedure Table, ^t, Documentation Information screen, Result Profile/Link Information field, Result Profile field. This is a valid configuration in QCPR; however, eCQM result profiles are required to be mapped in the Concept Mapping Tool application.

Resolution

eCQM now only processes events mapped in the Concept Mapping Tool application.




839875 Summary

A Visit Summary procedure event that had a status of “complete” displayed in the Provider Inbox and the Provider Inbox Across Patients applications as unsigned.

Symptoms

When a Visit Summary procedure event was generated by Criteria Evaluation Engine (CEE) and subsequently signed by the provider, the visit summary event remained in the Provider Inbox and Provider Inbox Across Patients applications, as well as any nursing review queues linked to the visit summary. In the Chart Review menu function, the event also displayed with an incorrect date/time.

Cause

When the Visit Summary procedure event was signed and filed, the system was filing the previous event's status instead of the actual “complete” status. This caused the event to bypass the queue deletion algorithm.

Resolution

After a Visit Summary procedure event is signed, the event displays the date/time when the event is completed in Chart Review and observes proper queue routing definitions.

840198 Summary

In the Order Entry menu function or application, when a dosage unit was modified, the previous dosage unit displayed.

Symptoms

In the Order Entry menu function or application, when defining dosage in a field created from the Order Entry Profile Table, ^nt(“op”), Dosage data element, and the user modified the dosage unit to one that was different from the unit defined in the Dosage Selection Screen Table, ^pt(“d”), Dosage Selection Screen level, Dosage Option field, the unit change was not captured in the menu function or application.

Cause

The Order Entry menu function and application copied the default strength/unit to current strength/unit when no strength/unit was entered. This copy did not update the strength/unit when a different one was entered.

Resolution

The Order Entry menu function and application now update the strength value and the unit when modified from the default defined in the Dosage Selection Screen Table, ^pt(“d”), Dosage Selection Screen level, Dosage Option field.




840233 Summary

Initial visit admission time for visit conversions were not evaluated in the Clinical Quality Measures Run menu function (eCQM) when evaluating the quality measure for Fibrinolytic Therapy Received Within 30 Minutes of Hospital Arrival (AMI7).

Symptoms

When using the Clinical Quality Measures Run menu function (eCQM) to evaluate the quality measure for Fibrinolytic Therapy Received

Within 30 Minutes of Hospital Arrival (AMI7) for an Inpatient visit converted from an Emergency visit, the initial visit admission time for the Emergency visit type was not included. The measure failed as a result.

Cause

When evaluating the AMI7 quality measure in the Clinical Quality Measures Run menu function (eCQM) for a converted visit, the admission time for the initial visit type was not included during the visit conversion.

Resolution

The Clinical Quality Measures Run menu function (eCQM) now includes all admission times for Inpatient and Emergency visit types when evaluating admission event times. Runs that previously failed when a pass was expected for this measure need to be performed again after this update.

840275 Summary

When using the Clinical Quality Measures Run menu function (eCQM) to evaluate the quality measure for Fibrinolytic Therapy Received Within 30 Minutes of Hospital Arrival (AMI7), users could map ICD-9 codes to the Result Profile Table, ^nt(“rp”), Selection Table data element in the Concept Mapping Tool application, however, the eCQM menu function only evaluated Selection Table data elements which were mapped to SNOMED CT codes.

Symptoms

The eCQM did not evaluate ICD-9 code set for this quality measure.

Cause

The eCQM run did not recognize the requirement being met when an ICD-9 code was mapped to the Result Profile Table, ^nt(“rp”), Selection Table data element. The eCQM did not evaluate ICD-9 code set for this quality measure and would result in a status of error in the eCQM run menu function. The patients documented as having received Fribrinolytic Therpy Within 30 Minutes of Hospital Arrival failed to be evaluated appropriately for this measure.

Resolution

The Clinical Quality Measures Run menu function (eCQM) now evaluates ICD-9 codes mapped using the Concept Mapping Tool application.

840413 Summary

A data-refreshing error occurred when creating a Continuity of Care Document (CCD) in the Document List application.

Symptoms

When using the Document List application to create a CCD, document creation failed and an error message displayed: Error Refreshing Document. The error message prevented the completion of the document creation.

Cause

This issue was caused when the Document List application encountered a "Reason for Visit" containing a value with a reserved XML symbol. An error would occur because the field was not formatted to replace the reserved character in XML.

Resolution

The Document List application has been updated to replace reserved characters in XML in the Reason for Visit section of the CCD.




840917 Summary

The Provider Inbox Across Patients application became unresponsive when providers attempted to load an order block event that contained a free-text employee name.

Symptoms

The Provider Inbox Across Patients application became unresponsive for users who had a free-text employee name in an order block event. When the application began to load the Inbox items, the loading status bar appeared to progress but the application never opened. When the user attempted to close the application, the entire CDA application became unresponsive. And a corresponding A subscript has an illegal value or a global reference is too long error message was logged in the Error Log.

Cause

The Provider Inbox Across Patients application attempted to load an order block event where the employee ID was defined using free-text, the application erred because it was expecting an ID from the Employee/Provider Table, ^ae.

Resolution

The Provider Inbox Across Patients application now translates an employee code entered as free-text in an order block event to use the corresponding employee code from the Employee/Provider Table, ^ae.

841098

840155

Summary

The report GEN - HTML Patient Medication Discharge Instruction Report (rev3) did not file when discharge medications were ordered.

Symptoms

After documenting a Discharge Medication Instructions event using the Consolidated Medication List tab in the Order Entry application, the entire Clinical Desktop Application (CDA) became unresponsive. Additionally, the event did not file, and the error message bad char in module %zu2c%zer displayed in the Error Log.

When users attempted to accept the discharge medication order, the Order Entry application would close, preventing the user from completing the order.

Cause

This issue occurred when the result profile contained both the Result Entry Profile Table, ^nt(“rp”), Multimedia and Frequency data elements. When the Multimedia data element is defined with the GEN - HTML Patient Medication Discharge Instruction Report (rev3) in the HTML Report(s) Constants field, and the Frequency data element was documented with a frequency that contained a reserved character in HTML (i.e., greater than, less than, and quote characters), the GEN - HTML Patient Medication Discharge Instruction Report (rev3) report did not convert the reserved characters to HTML-friendly characters. The report continued to attempt to process the reserved characters.

Resolution

The GEN - HTML Patient Medication Discharge Instruction Report (rev3) has been updated to use the HTML text(__) operator on all the string data types found in the report.



841183

841248

841356

Summary

Consolidated Clinical Document Architecture (CCDA) Outbound interface to a third-party patient portal stopped while transmitting a message.

Symptoms

A CCDA Outbound interface to a third-party patient portal generated an error message when attempting to transmit a message. The error message states: Error #6901: XSLT XML Transformer Error: SAXParse Exception.

Cause

Some Krames Patient Education documents can contain foreign language characters in the PDF which is stored in an Assessment Category/Data Element Table, ^nt(“ac”), Patient Education data element. When creating a document using the Document List application for a CCDA document that contained certain foreign language characters, the CCDA document was generated with content omitted. As a result, the XML representation of the document was invalid and therefore could not be parsed by the XML parsers. A CCDA Outbound interface to a third-party patient portal attempted to transmit a message containing the compromised CCDA document and generated an error message.

Resolution

The CCDAs now support foreign language characters documented using the Assessment Category/Data Element Table, ^nt(“ac”), Patient Education data element.



AF loop 13 Rebuild Order Profiles

AF loop 14 Rebuild Result Profiles

AF loop 47 Recompute Assessment multiple field abnormal flags

AF Loop 59 Remove deprecated Screen Dump Security

AF Loop 60 ePrescribing (DrFirst) Restructure Update Timestamps

Defects Resolved in 6.0.1 Update 14 (CDA Build 45) (QCPR Build 42) (ISDID Build 26) (PAM Build 603)




ENH The GEN - User Level Audit with Inactive User Selection (gen.user_lvl_audit_in) report has been modified as follows:

The Employee screen driver field (created using the Hierarchical Filing Structure Table, âhfs, Employee data element) has been renamed Active Employee(s).

A new All Employee(s) screen driver field (created using the Hierarchical Filing Structure Table, âhfs, Key data element) has been added to this report. Currently, the search functionality available in the Employee screen driver field does not provide the ability to include inactive employees in the search. This new field provides users the ability to search for all employees, including those defined as inactive in the Employee/Provider Table, âe, Active? field.

This report should be rebuilt after this update is loaded for these changes to become available.

ENH In result entry, when an allowed additional procedure(s) is added at result entry time, a link between the allowed additional procedure and the original order can now be created and is available in order review. This is available in the following menu functions:




With this enhancement, the Procedure Table, ^t, Specimen Information Screen, Allowable Additional Procedure(s) field has been enhanced with the following new options when defining an allowed additional procedure:

(L) always link – The System automatically creates a link between the allowed additional procedure and the original order without user intervention.

(N) never link – The System does not create the link between the allowed additional procedure and the original order. This is existing functionality.

When an allowed additional procedure is linked to an order, the order information for the original order now displays in the Chart Review menu function. When reviewing the allowed additional procedure in chart review, users can see the associated order information when they select the (X) Order review processing option.

Previously, the linkage between the allowed additional procedure and the associated order was not available, making reporting such information impossible. This enhancement makes the association between the additional procedure and the original order available for reporting and visible in chart review.

ENH In the External Document Processor menu function, the processing options to add a new patient and edit an existing patient’s registration information can now be suppressed. For sites that interface to a third-party registration system, this enhancement avoids the possibility of users inadvertently creating or editing patient registration information in QCPR.

The External Document Processor menu function, Registration Screen Sequence push parameter is now an optional field. When defined, the field’s current functionality remains unchanged. However, when undefined, the (N) Create New Patient and (E) Edit Registration processing options are suppressed from all screens in the menu function, disallowing users to create a new patient or edit the registration information for an existing patient when performing patient matching in the menu function.




833809 Summary

Af loop 36 Initialize Document-Logging Audit Type was not completing for sites with significant user activity.

Symptoms

When executing af loop 36, the System took several days and aborted the process before it was completed.

Cause

Audit log entries were being created faster than the loop was able to process the entries in the audit log.

Resolution

Af loop 36 Initialize Document-Logging Audit Type has been updated to process audit log entries faster. The loop has been run on sites affected by this issue.

836353

839995

Summary

The Hierarchical File Structure (HFS) report GEN - HTML Patient Medication Discharge Instruction Report (rev3) did not file.

Symptoms

After documenting a Discharge Medication Instructions event using the Consolidated Medication List tab in the Order Entry menu function, Clinical Desktop Application (CDA) became unresponsive. Additionally, the event did not file, and the error message Process Space exhausted in module %zu2f%bp displayed in the Error Log.

When users attempted to accept the procedure, all users on the System noticed performance degradation using QCPR.

Cause

This issue occurred when the result profile contained both the Result Entry Profile Table, ^nt("rp"), Multimedia and Medication Administration Info data elements. When the Multimedia data element is defined with the GEN - HTML Patient Medication Discharge Instruction Report (rev3) in the HTML Report(s) constants field, and the Medication Administration Info data element was documented with free text that contained a reserved character in HTML (i.e. greater than, less than, and quote characters), the GEN - HTML Patient Medication Discharge Instruction Report (rev3) report did not convert the reserved characters to HTML-friendly characters. The report continued to attempt to process the reserved characters.

Resolution

The HTML text (___) report operator has been enhanced to support multiple line string data types. The GEN - HTML Patient Medication Discharge Instruction Report (rev3) has been updated to use the operator on the multiple line string data types found in the report.




839502 Summary

Duplicate codes displayed in Controlled Vocabulary data element fields on order and result profiles

Symptoms

During order and result review, when the screen driver contained more than one field created from a Controlled Vocabulary data element in the Order Entry Profile Table, ^nt(“op”), or the Result Entry Profile Table ^nt("rp"), each data element field displayed codes entered in other Controlled Vocabulary data element fields on the same screen driver.

This issue occurred when all the Controlled Vocabulary data elements on the same screen driver were defined with at least one matching coding scheme in the data element’s Coding Scheme constants field. Codes entered in one Controlled Vocabulary data element field populated other Controlled Vocabulary data element fields, causing each field to display codes for other coding schemes. This issue occurred for the following data elements:

Order Entry Profile Table, ^nt(“op”), Controlled Vocabulary data element

Order Entry Profile Table, ^nt(“op”), Controlled Vocabulary (Proc Specific) data element

Result Entry Profile Table ^nt("rp"), Controlled Vocabulary data element

Result Entry Profile Table ^nt("rp"), Controlled Vocabulary (Proc Specific) data element

Cause

Order and result profiles containing more than one Controlled Vocabulary data element fields on the same screen defined with at least one matching coding scheme did not display the codes appropriately in view mode (i.e., during order review and result review and not order entry or result entry.)

Resolution

The result profile and order profile data dictionaries have been updated to filter the codes to display only the codes respective to the coding scheme defined in each data element. All order profiles and result profiles need to be rebuilt once the update is loaded for changes to take effect.

840419 Summary

The Clinical Desktop Application (CDA) became unresponsive to any inputs for a user attempting to order non-formulary medications were ordered.

Symptoms

The entire CDA application became unresponsive to any inputs for a user attempting to order any non-formulary medications in the Order Entry menu function.

Cause

When the user was entering information in the order profile in the Order Entry menu function and application on a non-formulary medication, the Order Entry menu function and application attempted to perform drug product selection, however, the algorithm became compute bound when it was unable to select a product.

Resolution

The drug product selection algorithm has been enhanced to evaluate the following priorities when attempting to find the best product match:

Floor stock only

Formulary only

Non-formulary




All order profiles, result profiles, and reports in the System need to be rebuilt for this update.


AF loop 13 Rebuild Order Profiles

AF loop 14 Rebuild Result Profiles

AF loop 3 Rebuild Report Writer (arf) Reports





ENH The QCPR Patient Access Module now enables sites to display multiple URL options when clicking the Hospital Home option on the screen banner. In the Patient Access Patient Web and the Patient Access Administration Web applications, when the user clicks the Hospital Home option at the top right corner of all screens, the user is prompted with a screen that can now be configured to display additional information with hyperlinks, including buttons and images, to client-specified URLs.

Previously, the Return to Hospital Home screen that displays after clicking the Hospital Home option provided two options allowing the user to either stay within the application or continue to a client-specified URL. With this enhancement, sites can define more URLs in addition to the existing options, providing increased flexibility in directing patient traffic from the applications while maintaining log-out security.

This enhancement is applied by customizing specific message keys in the qm-messages_en_US.xml file of the ../qm-pam/messages/ directory in the Patient Access Module server. The qm-messages_en_US.xml file contains the message keys used to customize button text and other information displayed in the two web applications. To add the new hyperlink options on the Return to Hospital Home screen, the following message keys need to be modified:

Patient Access Administration

Web application

<Message key="pam.admin.default_layout.message.page.info"> </Message>

Patient Access Patient Web

application

<Message key="pam.include_footer.message.return.hospital.custom">

</Message>

For each of the message keys, the following text must be appended to the XML element prior to the end tag (i.e., </Message>) to display the button of the option and the corresponding URL hyperlinked to the button:

<![CDATA[<site-defined display text><br/>

<a href="http://<server path>/<pam or pam-admin>/logout/hospital?go=http://www.<URL domain>.com"

class="btn btn-primary"><button text></a>

</br> ]]>

In the above XML code, the site-entered text for instructions on the screen and button text are listed in brackets ( < > ), including:

<site-defined display text> – Indicates the description for the subsequent buttons. The text entered within this element displays on top of the hyperlinked buttons (for example, Choose a medical center).

<server path> – Indicates the full address or path, including the Internet protocol (e.g., http://), to the Patient Access Module server.

<pam or pam-admin> – Indicates the web application using the new parameters.

<URL domain> – Indicates the domain of the URL hyperlinked to the button (for example, quadramed). The Internet protocol for the hyperlink (e.g., http://) must precede the domain.

<button text> – Indicates the text that displays inside the button (for example, Go to QuadraMed Medical Center).

The following excerpt is an example using the code directing patients to either proceed to the QuadraMed Medical Center or QCPR Medical Center:




<Message key="pam.admin.default_layout.message.page.info"> <![CDATA[Choose a medical center:

<br/>

<a href="http://<server path>pam-admin/logout/hospital?go=http://www.quadramed.com"

class="btn btn-primary">Return to QuadraMed Medical Center</a>

</br>

<a href="http://<server path>/pam-admin/logout/hospital?go=http://www.qcpr.com" class="btn

btn-primary">Return to QCPR Medical Center</a> ]]>

</br>

</Message>

This enhancement requires restarting the Patient Access Module server. Also, prior to installing a new build and modifying the message keys, a copy of the following files must be made to prevent changes from being overwritten with the new install:

qm-messages_en_US.xml

All sub-directories under ../qm-pam/




819164 Summary

In the Consolidated Medication List tab of the Order Entry application, when copying a visit order to a discharge medication, if either the dosage or frequency could not be copied, the medication is treated as a free-text discharge medication.

Symptoms

When a visit medication was copied to discharge medication and the dosage or frequency failed to also copy in the process, the System interpreted the medication a single free-text item and displayed it as a non-formulary procedure.

When the System Parameter Table, ^%z, Order Comm System Parameters subfile, Facility-specific level, Consolidated Medication List Parameters screen, Allow Free Text Home/DC Meds field was defined as Allow with Alert, copying the visit medication to a discharge medication displays an alert for copying a free-text medication even though the copied medication was not a free-text entry.

Cause

The frequency or dosage of the visit order failed to be copied correctly to a discharge medication. This caused the System to interpret the resulting medication as free-text.

Resolution

This update resolves the issue of visit medications incorrectly copied to discharge medications as free-text medications. The following conditions apply for copying home medications to visit order or a visit order to a discharge medication:

When a visit medication order is copied to a discharge medication, if the visit order is codified, the Medication field is defined using the matching Medi-Span Drug Name Identifier (DNID) The Medication field for the discharge medication does not display as free-text.

A medication is considered codified when a visit procedure has a single product defined via drug product selection and the product has a Dispensable Drug Identifier (DDID) code defined in the Product Table, ^pt(“p”), Drug Classification Information Screen – Wolters Kluwer DKV screen, DDID field. The System uses the DDID to find the higher drug name concept (DNID) to define the corresponding medication in the Medication field of the discharge mediation. When the visit order has multiple products defined, the System matches the procedure’s generic DNID defined in the Procedure Table, ^t, Product Information screen, Medication Component(s) field, DKV Drug Name(s) field. If a procedure has multiple generic DNIDs defined, the System uses the first DNID identified in the Procedure Table, ^t, Product Information screen, Medication Component(s) field, DKV Drug Name(s) subfield.

If the dosage can be copied (i.e., strength/unit from route), then the Dosage field is copied to the discharge medication order. For complex dosages, the dosage information is copied to the discharge medication’s Dose/Route field as free-text. Visit orders defined with a single event do not copy forward, and the Dosage field on the discharge medication displays blank (this is existing functionality).

When the visit order’s Frequency or When field can be copied (e.g., q-min, q_h, q_day, may repeat), the Frequency field is copied to the discharge medication. For complex frequencies (e.g., followed by, then), the frequency information is copied to the discharge medication’s Frequency field as free-text (this is existing functionality).




819236

810219

Summary

IV orders with intermittent frequency were not removed from the IV administration record (IVAR) accessible from the Medication/IV Administration menu function after being discontinued.

Symptoms

When an IV with an intermittent frequency was ordered, hanged, and the infusion was started, an issue occurred when the order was discontinued. The user was able to complete the currently hanging infusion; however, the IV was never removed from the IVAR display. The order no longer displayed in the Chart Review menu function’s Order History screen and displayed a status of ‘discontinued w/ events’. The user was able to interact with the IV on the IVAR, which should not have been possible since the IV order had been discontinued.

Cause

The issue was caused by a special check that kept IVs with actively hanging bottles from discontinuing until the bottle was taken down. The change made with a previous defect resolution reordered the way IVs were updated and caused this IV check to be evaluated before the IV state had been updated.

Resolution

This update resolves the check for a hanging IV to not depend on the IV state node.

In addition, the af loop, Remove discontinue IV orders stuck in IVAR, was improved to support orders not discontinued due to this issue. If the loop has already been run, the user can simply run it again.

826843 Summary

Cart-fill labels printed on bulk products when a patient returned from a leave of absence (LOA).

Symptoms

When a patient returns from an LOA, based on the user definition, all the patient’s events can be checked within the LOA period and be activated or held based on adherence to the LOA timeline. If any cart labels needed to be printed, those would print, or normal LOA checkin would be done instead. If in the event list, the patient had events with a bulk product, each individual event of the bulk product was evaluated. Initial dose labels printed and charges were made, if applicable.

Bulk products should instead be dispensed through initial dose and charged whenever they are requested, unlike non-bulk products, which are charged based on documented events and dispensed based on cart-fill labels.

Cause

Bulk products were not excluded when filing LOA procedures.

Resolution

This update resolves this issue to exclude bulk products when handling LOA procedure filing.




834778 Summary

Error occurred when building an order profile containing the Order Entry Profile Table, ^nt(“op”), Rx Directions (SIG) or Rx Products data element

Symptoms

While accepting changes to an order profile containing the Order Entry Profile Table ^nt(“op”), Rx Directions (SIG) and the Rx Products data elements with an expression(s) defined in the data element’s Expressions field, a QCPR Interrupt e-mail message displayed the following:

Background job status

Build ^nt(“op”, “p”): P/Medication - General completed with errors

Additionally, an entry in the Background Error Log displayed the following:

Save Program

Error: Label s14 not found in program noe%XXXX

Error: Source save error for program noe%XXXX

Cause

The Order Entry Profile Table, ^nt(“op”), data dictionary did not support expressions for the Rx Directions (SIG) and Rx Products data element types.

Resolution

The Order Entry Profile Table ^nt(“op”), Rx Directions (SIG) and Rx Products data elements now support the definition of an expression in the Order Entry Profile Table ^nt(“op”), Data Element, Expressions field. All order profiles need to be rebuilt once this update has been applied for changes to take effect.

836934 Summary

Home medications documented prior to the conversion from Medi-Span flat files to DIB API displayed with gMed Not Found F- before the medication name in the Consolidated Medication List application when the Medi-Span code for the home medication was no longer found in the DIB API database.

Symptoms

Home medications displayed with gMed Not Found F- before the medication name in the Consolidated Medication List application. In the Home Medication Editor menu function, the same home medications displayed with Med Not Found in red text before the medication name.

Cause

The Med Not Found prefix indicated that the ID codes associated with home medications documented in Medi-Span flat files were no longer valid in the API Medi-Span implementation. The extra characters in the Consolidated Medication List application were caused by the Clinical Desktop Application (CDA) displaying the control characters for the red, underlined text used by the Home Medication Editor menu function.

Resolution

The display issue in the Consolidated Medication List application has been resolved. The System now checks for CDA display and removes the control characters for red, underlined text.

To address medications displaying in the Consolidated Medication List application with the Med Not Found prefix, update the home medication(s) by searching for a new look up to the medication name in the Home Medication Editor menu function and filing.




837964

840019

Summary

The Clinical Quality Measures Run menu function (eCQM) displayed an error for clinical quality measures.

Symptoms

The error, Patient build error. Code <COMMAND>, Location=zBuildResultsForEvent+8^qcpr.build.EventsDta.1, displayed when running eCQM.

Cause

When running eCQM, a run completed with the message complete with errors. In this case, a single patient reported with a patient build error. This was caused by a patient who had a visit with over 2,000 orders documented when determining the medications administered for the patient. eCQM handled all of this data in memory and exceeded the process memory limit for InterSystems Caché. Another variation of this same issue occurred when loading all of the patient's visit events.

Resolution

eCQM has been updated to process the data collected for the clinical quality measures report in a temporary storage on disk to conserve system memory usage. Runs that display a status of ‘error’ should no longer err. In addition, this release resolves several cases where a ‘complete with errors’ status was being aborted, specifically when the individual error messages indicated Patient Build Error.

838450 Summary

Error occurred when editing access roles in the Patient Access Administration Web application.

Symptoms

In the Patient Access Administration Web application, when editing the following attributes for an access role, the system display did not match user edits:

ATTRIBUTE USER EDITS SYSTEM DISPLAYED

Enabled No Enabled

Patient Yes No

Attempts to change the attribute definitions caused the following error messages to display:

An Unexpected Error has Occurred

An Unexpected Error has occurred when trying to process your request. Please contact the system administrator for assistance.

The Patient Administration Error Log Details indicated the following error message:

Requested URL: /pam-admin/editconsentrole

Error Message: Request processing failed; nested exception is java.lang.NullPointerException

Cause

In the Patient Access Administration Web application, the message key for the user was being used as the message key for the access roles.

Resolution

PAM build 6.0.8.601 has been updated to use separate message keys for user accounts and access roles. PAM build 6.0.8.601 or higher must be installed to resolve this issue and prevent this error message when configuring the access roles in the Patient Access Administration Web application.




838903 Summary

E-mail templates in the Patient Access Module did not update with custom template changes made by the administrator.

Symptoms

For the Patient Access Administration Web application, changes made to e-mail templates in the /qmd/pam/PIMPAMDEV1/qm-pam/email did not take effect. The application still used default template information.

Cause

The installation path for external e-mail was not stored as a relative path. This caused the default e-mail templates to be used after a client had updated the e-mail template path.

Resolution

The Patient Access Module Installer has been updated to use a relative path for e-mail template storage during installation.

839241 Summary

The Legal Authenticator field on CCDA documents displayed the title of the user as MD regardless of the employee’s defined title in the Employee/Provider Table, âe.

Symptoms

For any employee type defined in the Employee/Provider Table, âe, with a security position that allowed for document creation using the Document List application, the Legal Authenticator field on the CCDA documents defaulted to display the title of the user as MD.

Cause

The Document List application did not collect the title as defined for the user in the Employee/Provider Table, ^ ae, Employee-specific level, Title field.

Resolution

The Legal Authenticator field on CCDA documents now displays the appropriate title for the user who generates the documents in the Document List application. Any CCDA documents created with an incorrect tile for the Legal Authenticator field prior to this update need to be generated again after the update has been applied.

839425 Summary

A language syntax error generated (on the screen and in the error log) in program %zu2f%f when attempting to generate any Audit Log report from the Audit Record Administration menu function.

Symptoms

When attempting to print the GEN - Patient Level Audit report from the Audit Record Administration menu function, an error would display on the screen and post to the error log. The report would not print.

Cause

The Report Formatter Data Dictionary, ârfd, print queue record had a syntax issue.

Resolution

The syntax issue has been resolved. The GEN - Patient Level Audit report must be rebuilt for changes to take effect.




839459 Summary

When using the Clinical Quality Measures Run menu function (eCQM) to evaluate the quality measures for stroke education (STK-4, 5, and 8), the menu function did not correctly evaluate result profiles containing multiple fields data elements in the Result Entry Profile Table, ^nt(“rp”).

Symptoms

If the result profile used for the stroke education quality measures (STK-4, 5, and 8) contained a Result Entry Profile Table, ^nt(“rp”), Multiple Field data element and mapped using the Concept Mapping Tool application, the patients failed to calculate into the numerator. However, patients correctly calculated into the Initial Patient Population (IPP) and Denominator.

Also, the denominator may not include expected Result Entry Profile Table, ^nt(“rp”), Multiple Fields data element type mapped using the Concept Mapping Tool application for the stroke education quality measures.

Cause

Multiple fields data elements in result profiles were not included when the Clinical Quality Measures Run menu function (eCQM) evaluated the IPP for the quality measure.

Resolution

Data recorded using multiple fields in the Result Entry Profile Table, ^nt(“rp”), are now included in evaluations.

839665

838790

Summary

The (A) Associated Procedures processing option displayed during order entry when there were no defined associated procedures.

Symptoms

When entering an order in the Order Entry menu function and application, the (A) Associated Procedures processing option displayed. If the (A) Associated Procedures processing option was selected before all the required fields were completed, the order was accepted and filed in ‘review’ status.

Cause

Another System functionality leveraged the (A) Associated Procedures processing option and activated it in error.

Resolution

The (A) Associated Procedures processing option has been removed from the Order Entry menu function and application.

839704 Summary

The Clinical Quality Measures Run menu function (eCQM) displayed complete with errors for clinical quality measures.

Symptoms

The Clinical Quality Measures Run menu function displayed complete with errors for clinical quality measures VTE-4 and VTE-6. Error message received was Patient build error. Code <COMMAND>, Location=zBuildResultsForEvent+8^qcpr.build.EventsDta.1.

Cause

eCQM received a secondary error message, Profile not imported. The error resulted because there was a procedure that did not have result profile defined in the Procedure Table, ^t, Documentation Information screen, Result Profile/Link Information field, Result Profile subfield. This is a valid configuration in QCPR. However, for eCQM, result profiles are required to be mapped in the Concept Mapping Tool application.

Resolution

eCQM now only processes events where mapping is defined in the Concept Mapping Tool application.




839768

835828

Summary

The Device Table, âd, Allow Multimedia Edits? field’s default definition of yes was not being acknowledged.

Symptoms

If a user attempted to edit a multimedia field created from the Multimedia data element in the Result Entry Profile Table, ^nt(“rp”), or the Assessment Category/Data Element Table, ^nt(“ac”), the selection/option was not selectable. This would be working as expected if the Device Table, âd, Allow Multimedia Edits? field was defined as no. In this instance, the field was defaulted to yes and any multimedia data elements should have been selectable for the device(s).

Cause

In QCPR Release 6.0.0 Update 10 and higher versions, the default setting for the Device Table, âd, Allow Multimedia Edits? field was changed from no to yes. The System displayed the default as yes; however, the table did not recognize the setting and functioned as if the field was defined as no.

Resolution

The Device Table, âd, has been updated to default the Allow Multimedia Edits? field to yes.

840078 Summary

Prescriptions ordered with a stop date did not appear on Continuity of Care Documents (CCD).

Symptoms

When a prescription was ordered with a stop date/time, the stop date should display in the CCD so that patients or other providers know when a medication course is complete. The stop date was not appearing on the CCD.

Cause

The prescription order stop date was not being properly collected from the order record.

Resolution

The Document List application has been updated to include prescription order stop dates in CCD documents.

840106 Summary

Users were unable to execute any reports from the Hierarchical Filing Structure Table, âhfs.

Symptoms

Users received Missing Routine error messages in the Error Log Display menu function when attempting to execute reports.

Cause

The problem reported was a result of the Load Early Items step that was part of an alternate load process during a Rollover which included components expected to be completed during the load process. The Auto-Rollover Load Utility menu function had loaded the

Hierarchical Filing Structure Table, âhfs, (ahfst.gz) prematurely which had been updated in the 6.0.1.10 Update. The table required an updated version of the ahfsi3 component to be loaded simultaneously which was included in the scheduled Update and rollover.

Resolution

The Auto-Rollover Load Utility menu function has been modified to omit the Load Early Items step during the Alternate load process. Components previously loaded during this step will now complete during the load process.




ENH The following report enhancements have been made:

The GEN - Discharge Medication Statistical Usage Report (gen.disc_med_stat.h) has been modified as follows:

The report now includes Ordered Author (Ordered by) information for discharge medications entered using the Home Medication Editor menu function.

The Prescriber Search field now displays on the report.

The Prescriber Usage Section now prints on the report.

The GEN - Discharge Medication Statistical Usage Download Report (gen.disc_med_stat_dwnld.h) has been modified as follows:

The report now includes Ordered Author (Ordered by) information for discharge medications entered using the Home Medication Editor menu function.

The Ordered By information now displays in a new Provider column on the report. The information displays by field value for discharge medications/prescriptions.

The Prescriber Search field now displays on the report screen driver.

822136 Summary

Trend Display report with result type of strength/unit defined in the Strength/Unit Table, pt(“su”), did not display units in the GEN – Chart Review Trend Hook Report.

Symptoms

Numeric values for medication dosages appear on report without strength/units.

Cause

The report was not including the strength/unit result type when evaluating result storage records for inclusion in the report.

Resolution

The following generic reports have been modified to include strength/units for strength/unit result types and will use the short name defined in the Strength/Unit Table, pt(“su”), as a suffix to the dose value:

GEN - Chart Review Trend Hook Report~ (gen.chart_trend.arf)

GEN - Chart Review Trend Hook Report (gen.trend_report.arf)




837901 Summary

Errors occurred during validation of Continuity of Care Documents (CCD) using the tool provided by the National Institute of Standards and Technology (NIST).

Symptoms

When users tried to validate via the NIST Validator, validation failed and the user received errors.

Cause

When generating a CCD, the CCD generated then failed when trying to validate the XML via NIST Validator when a patient visit was created without a defined admitting physician. The empty Admitting Physician field caused the error.

Resolution

When a patient visit is created without a defined admitting physician and a CCD is generated, the generated CCD will now proceed to validate the XML via the NIST Validator.

837910 Summary

Issues occurred when entering postcodes in United Kingdom (UK) implementations in fields created from the Address Collection Driver Table, ^rt(“ad”).

Symptoms

The following issues occurred when entering a postcode in UK implementations:

When adding a new patient, if a postcode was entered into a field created from the Address Collection Driver Table, ^rt(“ad”), Mailing Code data element, the address information did not populate for fields created from the Building Number and Street Address data elements. Only fields created from the Mailing Code, City, and State/Province data elements were populated.

When editing an existing address, fields created from the Address Collection Driver Table, ^rt(“ad”), Mailing Code, City, and State/Province data elements were populated with the new details but fields created from other data elements, such as the Street Address and Building Number data elements, retained the old address information.

Cause

A logic error in QCPR code was causing postcode logic for UK implementations to be skipped. This issue occurred in the Address

Collection Driver Table, ^rt(“ad”), Mailing Code data element.

Solution

The error in the QCPR code has been corrected so that postcode logic for all implementations now processes mailing codes correctly. This update requires a rebuild of Address Collection Driver Table, ^rt(“ad”), screen drivers.

838928

839739

834986

Summary

When using the Clinical Quality Measures Run menu function (eCQM) to evaluate the quality measure for stroke education (STK-8), the menu function did not correctly evaluate result profiles containing multiple fields data elements in the Result Entry Profile Table, ^nt(“rp”).

Symptoms

If the result profile used for the Stroke-8 quality measure had a multiple field in the mapping, the patients failed to calculate into the Numerator. Patients correctly calculated into the Initial Patient Population (IPP) and Denominator.

Cause

Multiple fields in result profiles were not included when the Clinical Quality Measures Run menu function (eCQM) evaluated the IPP for the quality measure.

Resolution

Data recorded using multiple fields in the Result Entry Profile Table, ^nt(“rp”), are now included in evaluations.




839278

838905

Summary

Patients displayed in the Initial Patient Population (IPP) for some quality measures and not for others.

Symptoms

When using the Clinical Quality Measures Run menu function (eQCM), patients displayed in the IPP for some measures and not for others even though the measures had the same criteria. The patients should be displaying in all relevant measures.

Cause

The issue happened whenever an error occurred for patients during evaluation for any of the measures. If any error occurred while evaluating a patient, the patient's evaluation data was cleared from the report and it no longer displayed in the record. Also, the patient was no longer evaluated for any subsequent measures.

Resolution

This update resolves this issue so the patients are evaluated for all measures regardless of any encountered errors. The tally of patients in the IPP now accurately displays.

839390 Summary

Abnormal indicators for data elements in the Generic Table Table, ^ntt, were incorrectly evaluated when the user performed a partial name search against the data elements.

Symptoms

A selection table option created using a Generic Table Table, ^ntt, data element can have an abnormal indicator when the Generic Table Table, ^ntt, Table Definition level, User Defined Abnormal State? field is defined as yes. Defining this field as yes displays the Abnormal State field for each data element in the Generic Table Table, ^ntt, Data Element subfile, Table Data Element Definition screen.

When documenting on a result profile, if a partial match was used to find a selection table option with the Generic Table Table, ^ntt, Subfile Options level, Data Elements subfile, Abnormal State field defined as abnormal, the option did not evaluate as abnormal. The information in the field created from the data element did not display with an underline, which would have indicated an abnormal state.

Cause

The routine calling the program associated with the Generic Table Table, ^ntt, Data Element subfile, Table Data Element Definition screen, Abnormal State field was not appropriately evaluating the field definition when the corresponding Result Profile Table, ^nt(“rp”), Selection Table data element was defined to allow for partial name search. A Selection Table data element provides partial name search when the Result Profile Table, ^nt(“rp”), Selection Table data element, Allow Partial Name? Constants field is defined as yes.

Resolution

This update resolves this issue so that a partial name look-up now returns the appropriate abnormal status for the selection table option.


The following screens need to be rebuilt for this update:

Address Collection Driver Table, ^rt(“ad”) screens must be rebuilt.






ENH QCPR now provides the option to enable manual (simulated) entry of barcodes for patient, product, and solution IDs in the Medication/IV Administration and IV Administration menu functions accessed in Javaview and Clinical Desktop Applications (CDA).

This enhancement is designed to help QuadraMed staff simulate barcode entries when replicating reported issues. Client sites should not use this enhancement as a workaround to established workflows for barcode medication/IV administration functions or for any other purpose for which this enhancement is not intended.

This enhancement includes new fields in the following tables:

System Parameter Table, ^%z – The BCMA Manual Scanning Default field is added to the System Parameter Table, ^%z, Order Comm System Parameters subfile, System-specific level, Pharmacy Parameters screen. This field defines the default definition for manual barcode entry in the new Application User Profile Table, âp, BCMA Manual Scanning? field. This field can be defined as follows:

Yes – Defaults the definition of the Application User Profile Table, âp, BCMA Manual Scanning? field to yes.

No – Defaults the definition of the Application User Profile Table, âp, BCMA Manual Scanning? field to no.

Application User Profile Table, âp – The BCMA Manual Scanning? field is added to the Application User Profile Table, âp, User Interface subfile. This field defines whether a user can manually enter barcodes when scanning patient, product, and solution IDs in the Medication/IV Administration and IV Administration menu functions in Javaview or CDA. The default definition of this field is defined in the new System Parameter Table, ^%z, Order Comm System Parameters subfile, System-specific level, Pharmacy Parameters screen, BCMA Manual Scanning Default field.

When this field is defined as yes for the user:

Manual entry of patient, product, and solution barcode IDs is allowed

Barcode numbers briefly display in the transaction line where barcodes are scanned

When this field is defined as no for the user:

Manual entry of patient, product, and solution barcode IDs is not allowed

Barcode numbers do not display in the transaction line where barcodes are scanned

When a user attempts to enter a barcode manually, the error Manual barcode entry not allowed. displays

ENH For sites implementing the clinical quality measure for exclusive breast milk feeding, the SNOMED CT code representing the concept “Mother refuses to breastfeed (situation)” can now be loaded to QCPR through special request. Once loaded, the code (434581000124103) can be mapped in the Concept Mapping Tool application under the vocabulary of SNOMED CT Concept. This enhancement applies only to sites implementing the clinical quality measure for exclusive breast milk feeding in the perinatal care core measure set. For help loading the code into QCPR, contact QCPR Support.




ENH The Home Medication Editor menu function and Consolidated Medication List application have been enhanced to now display the Ordered By field for discharge medications. This field is a view-only field and is populated based on processing options used to create the discharge medication.

When the Standard Desktop Configuration Table, ^at(“dt”), Non-Facility Preferences, Allow Discharge Med Processing? field for the associated application is defined as no, the System does not modify the Ordered By field during discharge medication processing.

For new and edited discharge medications documented using the Home Medication Editor menu function in Discharge Medications mode, the System stores the Ordered By user identification information with each record according to the following:

For initial discharge medications copied from home medications without edits to the Medication Type, Dose/Route, and/or Frequency fields, the System displays the original Ordered By value defined for the home medication.

When the Medication Type, Dose/Route, and/or Frequency field are edited or modified, or when discharge medications are added, the System automatically replaces the value in the Ordered By field with the name of the user processing the discharge medication.

For new and edited discharge medications and discharge prescriptions documented using the Order Entry application, Consolidated Medication List tab, the System stores the Ordered By user identification information with each record according to the following:

The order block's order author displays in the Ordered By field for the following:

New discharge medications

During Initiate Discharge Medication processing when edits are made to the Medication Type, Dose/Route, and/or Frequency field

When prescriptions are copied to home medications, the System automatically displays the prescription author in the Ordered By field

ENH Fields created from the Order Entry Profile Table, ^nt(“op”), Selection Screen/Tree data element containing Sliding Scale information can now be mapped to display in Discharge Medications when a Visit Order is copied in the Order Entry application, Consolidated Medication List tab.

The new SLIDINGSCALE marker allows the user to map the field containing Sliding Scale information to the Discharge Medications, Patient Instructions field. This marker is located in the Concept Mapping Tool application, QuadraMed QCPR Concepts vocabulary, Order Profile Markers marker. When copied, documented Sliding Scale information, along with any documented instructions information in the Visit Order, is populated into the Patient Instructions field of the Discharge Medications profile.

Once displayed in the Patient Instructions field, the Sliding Scale information can be edited by the user in Discharge Medications. The user can also print this information on the GEN – HTML Medication Reconciliation Report in Discharge mode and on the GEN – HTML Patient Medication Discharge Instruction Report.

ENH The Assessment Category/Data Element Table, ^nt(“ac”), Assessment Category/Data Element Definitions subfile, Home Medications data element has been enhanced with the new Default Medication Field Search Type Constants field. This new Constants field defines the default medication search type in the Medication field when entering a home medication on an assessment screen using the Home Medications data element. This Constants field defaults to drug name search only. When changes are made to the Constants field, screens using the Home Medications data element must be rebuilt in the Assessment Screen Table, ^nt(“as”), for changes to be reflected on the user side.




831135 Summary

When procedures were rescheduled in QuadraMed Enterprise Scheduling (QES), the event date and time were updated in QCPR, but if the procedure had associated procedures, these were not updated and remained at the originally scheduled date and time.

Symptoms

In the QES/QCPR integration for scheduling patient appointments and procedures, if a procedure with the Procedure Table, ^t, Associated Procedure Information screen, Associated Procedure(s) field defined with an associated procedure was rescheduled in QES, the associated procedure was not rescheduled.

Cause

In the initial implementation of the QES/QCPR integration, it was determined that procedures which were not scheduled in QES would not be updated when the parent procedure was rescheduled. This functionality worked for some use cases but not for others.

Resolution

The Procedure Table, ^t, Resource Scheduling/Visit Check Information screen, Use Resource Scheduling? field determines if a procedure is scheduled in QES. If this field is defined as yes for the associated procedure(s), the current logic, to not reschedule an associated procedure(s) when the parent procedure is rescheduled, will continue. In this configuration, parent and children procedures are each scheduled independently in QES and the schedule updates in QCPR for each component.

If the field is defined as no for the associated procedure(s), the associated procedure(s) will now reschedule in QCPR when the parent procedure is rescheduled (or discontinued) in QES.

831528

828424

Summary

An error refreshing data error occurred when creating a Continuity of Care Document (CCD).

Symptoms

Continuity of Care Document creation failed and an error message displayed: QuadraMed.Service.Library.ServiceException: Bad xml, xml=AuthorityName='CCD 11'/><displayName='Body temperature'/><status System.Xml.XmlException: '', hexadecimal value 0x01, is an invalid character.


Cause

This issue was caused when a result profile was defined with an Assessment Category/Data Element Table, ^nt(“ac”), Multiple Field Screen Definition subfile, Measurement data element field that had a value containing a reserved XML symbol and the result was mapped to an event processed by the Document List application. An error would occur because the field was not formatted to replace the reserved character in XML.

Resolution

The Assessment Category/Data Element Table, ^nt(“ac”), Multiple Field Screen Definition subfile, Measurement data element fields now display properly when creating a Continuity of Care Document.




832372 Summary

User received a global subscript length error in reports.

Symptoms

Reports using specific Report Formatter Data Dictionary Table, ârfd records erred when outputting free-text data exceeding 512 bytes of characters that was documented using the Assessment Category/Data Element Table, ^nt(“ac”), Multiple Field Screen Definitions subfile, Generic Table or Free Text data elements. The report referenced the Report Formatter Data Dictionary Table, ârfd, record visit:assessment category:event:data element:multiple field occurrence:order number:generic table element with field option of generic table data element.

Cause

The Report Formatter Data Dictionary Table, ârfd, record visit:assessment category:event:data element:multiple field occurrence:order number:generic table element with field option of generic table data element referenced the value entered in the Selection Table or Free Text data elements in the Assessment Category/Data Element Table, ^nt(“ac”), Multiple Field Screen Definitions subfile, instead of the record key. As a result, when the free-text data entered exceeded 512 bytes of characters, the report would error.

Resolution

The Report Formatter Data Dictionary Table, ârfd, record visit:assessment category:event:data element:multiple field occurrence:order number:generic table element with field option of generic table data element has been updated. All reports using this record must be rebuilt for changes to take effect.

837083 Summary

Scheduled and administered medication events did not appear on the Interactive Care Grid application (ICG).

Symptoms

When an ICG was configured to display scheduled and administered events, the ICG would display indicators that data was present but no data displayed in the grid cells. After refreshing, the data would display.

An ICG is expected to display scheduled and administered events when the Interactive Care Grid Table, ^nt(“vgr”), Interactive Care Grid Row option, Row Type field is defined as event and has chart review groups that include the medication procedures/events defined in the option’s Row Type Data field, Chart Review Group(s) subfield.

Cause

Clinical Desktop Application (CDA) was not consistently gathering the ICG data that needed to display based on the ICG configuration on the patient desktop.

Resolution

CDA version 6.0.1.38 includes the solution that gathers the correct data to consistently display in the ICG with expected data.

837113 Summary

Automatic product selection does not occur when modifying administration time for IV syringe route.

Symptoms

An order with a route defined in the Route Table, ^pt(“ro”), with the Product Selection Type field defined as syringe, would not perform automatic drug product selection during change order when the administration time was changed.

Cause

When the change order occurred, the previously selected product(s) was not saved as default, causing the user to have to step through the diluent and additive components of the order.

Resolution

When order administration times are changed for an order with a route defined with the Route Table, ^pt(“ro”), Route level, Product Selection Type field defined as syringe, previously selected products are defaulted and can be modified if needed.




837656

837612

837777

839278

Summary

eCQM clinical quality measures failed to exclude visits when evaluating discharge types mapped to the Transfer To marker.

Symptoms

Clinical quality measures AMI 2 and AMI 10 both excluded visits documented with a ‘discharge to Home Hospice’ or ‘discharge to Hospice facility’. There was a conflict in the measure requirements where the clinical quality measures classified the same data as different elements (Transfer To, Discharge Type). In one of the AMI clinical quality measures, the logic was such that the Transfer To event time had to ‘start after the end’ of the inpatient visit. The measure evaluated the Transfer To marker for the event occurrence within one hour after the end of the visit. However, QCPR documented the event time within the visit time by design.

Cause

When a Result Entry Profile Table, ^nt(“rp”), Result Entry Profile Definitions subfile, Discharge Type data element was mapped to the Transfer To marker in the Concept Mapping Tool application, the time of the event was considered as being within the duration time of the visit. For some clinical quality measures defined in the Clinical Quality Measures Run menu function (eCQM), the event time for results defined in the Discharge Type data element should evaluate to a time (one minute) outside of the visit.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated so that when Result Entry Profile Table, ^nt(“rp”), Result Entry Profile Definitions subfile, Discharge Type data elements are evaluated for Transfer To markers, the event time is incremented by one minute so that the discharge date/time + one minute evaluates outside of the visit. This change only applies for the Transfer To marker and not the discharge status.

838555 Summary

Initial Event pop-up window does not show the first event for ‘___ times a day’ frequency option.

Symptoms

For the ‘___ times a day’ frequency option, the first event date/time was blank for the Initial Event pop-up window. A date and time displayed only when the ‘2 times a day’ frequency option was used. The date and time for the ‘___ times a day’ frequency option displayed in the order block, but did not populate the first event.

Cause

This issue occurred only when the ‘__ x per day’ frequency option was selected from typical orders. The issue did not occur if the frequency option was selected from the Order Profile tab. This was only an issue in Clinical Desktop Application (CDA) 6.0.1.15.; using typical orders and the ‘___ x per day’ frequency option did not affect functionality in UltiView.

The System retrieved the first event label from the 4th column of the shopping cart, which displayed ‘start date’ information. When the order was selected from typical orders, it was unable to retrieve it from that column.

Resolution

CDA 6.0.1.40 has been updated to get the information from the same source used to display the ‘start date’ in the shopping cart.




838558

838257

838663

Summary

Change orders for an original order with a ‘start if’ frequency modifier did not send updated order information to Pyxis.

Symptoms

Changing an order with a ‘start if’ frequency modifier that has already occurred requires new product selection. The outbound message sent to Pyxis still displayed the previously selected product, and did not allow the correct product to be pulled from Pyxis.

Cause

This issue occurred for a specific scenario:

The ‘start if’ order was activated when the frequency modifier condition was met.

After the ‘start if’ condition was present, the order was changed, causing a change in product selection but not to the frequency.

The HL7 node of the visit record was not updated when dosage of a conditional order was changed in the scenario described.

Resolution

Code changes now update the HL7 node of the visit record when a conditional order is changed after activation without a frequency change. This allows the HL7 outbound interface to send the updated selected product, as a result of the change order.

838763 Summary

User received error message ERROR #6901: XSLT XLM Transformer Error: SAXParseException: Whitespace expected) when selecting the (V) View Report Overview processing option in the Clinical Quality Measures Run menu function (eCQM).

Symptoms

When a user selected the (V) View Report Overview button in the Clinical Quality Measures Run menu function (eCQM) for runs, an error message was received ERROR #6901: XSLT XLM Transformer Error: SAXParseException: Whitespace expected).

Cause

This issue occurred when the (V) View Report Overview processing option in the Clinical Quality Measures Run menu function (eCQM) was selected for runs for visits containing events documented with an Assessment Category/Data Element Table, ^nt(“ac”), Numeric data element, which was documented by an interface message with a greater-than > or less-than < character (e.g., Gestational age >= xx weeks).

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated to display reserved characters using the HTML equivalent character in the QRDA Overview Report when the (V) View Report Overview button is selected.

838818 Summary

Global subscript length error occurred when accessing home medication documentation in the Home Medication Editor menu function.

Symptoms

When attempting to access the Home Medication Editor menu function, if there was an existing order with a free-text Medication Name field containing more than 255 characters, the System displayed a global subscript length error.

Cause

A medication name can be documented as free-text when using the Home Medication Editor menu function. It is later used as an index in various patient medication inversion structures. If the free-text medication name exceeded the limit of the Caché subscript (255 characters), the System displayed a global subscript length err message. An example would be if the dose, route, frequency, and instructions were entered as free-text into the Medication Name field.

Resolution

To prevent free-text entry exceeding the limit, the free-text Medication Name field has been shortened to the Caché 255-character limit.




All assessment profiles need to be rebuilt for this update.


AF loop 43 CMS: Load Data Type Patterns





784204

837439

Summary

‘Language Spoken’ section in the Continuity of Care Document (CCD) did not always display a language, but would display interface code defined for the Generic Table Table,^ntt, mapped to the Language Spoken SNOMED code for some data elements

Symptoms

When creating a CCD, some languages did not display language descriptions even though the correct interface code was defined in the Generic Table Table, ^ntt. The interface code displayed in the ‘Language Spoken’ section in the CCD instead. This problem occurred for the Tagalog, Navajo and Yiddish languages.

Cause

The reference database for language codes in the creation of CCDs was not complete.

Resolution

The reference database for language codes in the creation of CCDs has been updated and is now consistent with ISO 639-1 and ISO 639-2 standards.

789603

797353

Summary

Missing Routine Errors when attempting to accept a PAR Hold Event from the Department Order Review Queue application

Symptoms

The physician's PAR hold review item does not display in the ordering/responsible provider's inbox.

The PAR Hold review item in the Department Order Review Queue application has incorrect and missing data

The unhold of the PAR hold review item does not occur (from the Physician Review Queue application)

Correct patient does not display in the Attending Provider's Patient List application

Cause

This issue occurred as a result of a collapse of medical record numbers. The following specific conditions lead to this error:

Patient B is admitted and the physician places a medication order.

Patient B’s visit is activated by nursing staff and a drug allergy is entered, triggering a PAR Alert.

Nursing places the medication associated with the alert on Hold.

Medical records collapses Patient B (incorrect patient) into Patient A (correct patient).

Resolution

Users will no longer receive “Missing Routine” error messages in in the Department Order Review Queue application when processing PAR Review hold entries during a patient collapse or expand.




829604

Summary

Slow response time when loading medications in the Medication Administration Reconciliation (eMAR) applet

Symptoms

System requires the user to scroll down to view all medication options and the screen takes considerable time to load when viewing patients with a long list of medications in the Medication Administration Reconciliation (eMAR) applet

Cause

There was a data refresh issue with CDA.

Resolution

The eMAR applet has been updated to load all medications upon launch.

833460

Summary

Suppresses the selection of an allergy product that does not have product packaging information codes for Non-API systems

Symptoms

When processing the selection of an allergy product to correct a definition that does not have product packaging information codes, the same allergy with the inactive code is made available for selection from the list.

Cause

The Allergy Definition Table, ^pt(“ad”), Allergy Definitions subfile, DKV Allergy Link(s) field could be defined with the same Medi-Span Knowledge Base Drug Code (KDC) with no active product. This created a repetitive cycle and impeded the user from editing the allergy definition.

Attempts to define a KDC with no active product in the Procedure Table, ^t, Product Information screen, Medication Component(s) field and in the Product Table, ^pt(“p”), Drug Classification Information - Wolters Kluwer DKV screen, DKV Product Drug Link field are unsuccessful. The Allergy Table, ^pt(“ad”), needed to have this same restraint.

Resolution

The Allergy Definition Table, ^pt(“ad”), Allergy Definitions subfile, DKV Allergy Link(s) field and the Assessment Category/Data Element Table, ^nt(“ac”), Multiple Field Screen Definitions subfile, Allergy Name Data Element no longer display medications that do not have a packaged product for definition.

835431

Summary

If a patient had multiple Surgical Procedure codes documented, and one of those codes matched the Principal Procedure code, the patient was not excluded from Clinical Quality Measure (eCQM) as expected.

Cause

The System was only excluding the patient when there was a 1:1 match between Principal Procedure code and the documented Surgical Procedure code.

If multiple Surgical Procedure codes were documented and even if one of the Surgical Procedure codes was a match to the Principal Procedure code, the patient would not be excluded.

Resolution

The CCD logic now looks for a Principal Surgical Procedure match in any documented Surgical Procedure codes. If found, the patient is excluded as expected from the eCQM.




836574

836583

Summary

The Continuity of Care Document (CCD) incorrectly displays allergy information

Symptoms

A generated CCD incorrectly displays Don't know whether there were any allergies when No Known Allergies is documented for a patient.

Cause

This issue occurred when allergies were documented using a result profile defined in the Result Entry Profile Table, ^nt(“rp”).

Resolution

When allergies are documented within a result profile, they now display as ‘documented’ on the Continuity of Care Document (CCD).

838427 Summary

Order Number (OID) of 1 was being assigned for multiple change orders for different procedures

Symptoms

Order profiles/schedules in Pyxis are incorrect. When reviewing interface messages for change orders sent from QCPR to Pyxis, the order number value in multiple messages is ‘1’. This causes the order information in the most current interface message with the order number value of ‘1’ to override the information of the previous order with the same order number.

Cause

For procedures that define that an Order ID (OID) be assigned to orders, an OID is assigned to each order state. There are a number of different workflows that create order states. Each of these paths needs to have code that stores an OID with the newly created order state.

Procedures are defined for OID in the Procedure Table, ^t, Documentation Information screen, Monitor/Interface Definition field, Order Interface ID Assignment subfield.

Prior to this solution, OIDs were assigned for the following workflows:

New order

Change order

Correction change order

Modify active order (nursing change order)

DC subprocedure

Resolution

With this solution, the remaining workflows now assign OIDs:

Transfer default schedule change – This is the workflow that caused the problem to be reported. This scenario happens for orders with frequencies with default schedules when the patient is checked into a bed on a unit with a different default schedule.

IV product edit – redo product selection on an IV order

Orders at discharge




838470 Summary

A language syntax error is generated in the Department Order Review Queue menu function (DORQ)

Symptoms

After selecting an order with a hold status from the Department Order Review Queue menu function, a language syntax error is generated when the function translates from English to French.

Cause

The error is generated during a translation from English to French. Some characters were not being properly translated.

Resolution

Users will no longer receive a syntax error when selecting an order on hold in DORQ when the System Parameter Table, %z, System Language field is defined with the French language.

838250

838108

Summary

Data changed by the Wolters Kluwer Update Mapping RxNorm Codes Utility menu function output is unreadable

Symptoms

After the RxNorm update, the report output for the mapped RxNorm data for DDIDs/GPIs did not display with column formatting and contained the full RxNorm product name which displayed on multiples lines in the report. Selecting the 'Print' button merged the content for each RxNorm entry on the same line without column formatting and did not contain the full RxNorm product name.

Cause

The Wolters Kluwer Update Mapping RxNorm Codes Utility menu function displayed a report upon completion of the background job in the Background Job Display menu function that did not format columns. The report also contained full RxNorm product names which, when printed, displayed on multiple lines in the report.

Resolution

The RxNorm report now displays with column formatting and no longer contains the full RxNorm product name. This allows the report to be reviewed in a more readable format when printed with an 8 1/2 x 11 paper printer form, as defined in the Print Spooler Printer Table, apsp, Form field.

838761 Summary

Screen driven reports with HTML output begin with unreadable text before the <HTML> tag

Symptoms

When the user launches any HTML Hierarchical Filing Structure Table, ^ahfs, screen driven report, the report displays with unreadable text before the <HTML> tag. Additionally, the report does not refresh with the interval defined in the HTML Report application, Non-Facility Parameters, Refresh Interval field.

Cause

Changes made related to the Report Writer application displayed data intended for the Refresh Interval field to display on the report.

Resolution

The Report Writer application has been updated to display and refresh HTML reports without unexpected additional text.



839026 Summary

Error displays in the Medication/IV Administration menu function (MAR) when selecting a reschedule comment

Symptoms

When rescheduling a medication, the Invalid format for this field! error message displays in the MAR when selecting a reschedule comment.

Cause

Defect resolutions in 6.0.1 Update 6 conflicted with the reschedule workflow, causing the error.

Resolution

The user will no longer receive an Invalid format for this field! error message when selecting a reschedule comment in the Medication/IV Administration menu function.

839085 Summary

New patient location does not display in all patient display views when an area name change is made in the Area Table,âfa, Area Name field

Cause

By design, visit and patient records store the location display name. They were not being updated when an area name change was made in the Area Table, âfa, Area Name field.

Resolution

When the Area Name field is changed in the Area Table, âfa, the visit and patient records now update to reflect the new patient location display name.



There are no AF loops that need to be run for this update.





ENH When canceling an event in the following menu functions, the cancel comments now display on Quality Reporting Document Architecture (QRDA) documents with appropriate codification of cancel reason options:

Patient Schedule

Kardex

IV Administration

ENH The following generic Smart Button reports are now available in the Medication Reconciliation package:

GEN – HTML Home Medications Documentation Smart Button Hook Report – This report is used with the Home Medication Editor menu function to display whether the patient's home medications need to be documented with the application based on the patient's home location check-in date and time.

GEN – HTML Medication Reconciliation Documentation Smart Button Hook Report – This report is used with the Department Processor menu function to display medication reconciliation events scheduled for the patient during admission, transfer, and discharge events.

774175 Summary

Allow passing of data with non-printable characters through HTML report URL links

Symptoms

Reports written using the ARF Report Writer for display in HTML include a direct link to open a second report based on data included in the initial report. The report does not display as expected in the internet browser due to unexpected characters included in the URL, Uniform Resource Locator references.

Cause

The ‘url encoding(___)’ operator translates non-printable characters to be encoded in URL references.

In this issue, the ‘url encoding(___)’ operator was not decoding the URL received from the internet browser. Additionally, the ‘url encoding(___)’ operator was only replacing the first occurrence of a character needing encoding.

Resolution

All such characters are now encoded and decoded to open the URL reference as expected.

824791 Summary

CCD Document creation error caused by reserved XML character in reference range

Symptoms

Continuity of Care Document creation fails due to an error message: System.Xml.XmlException: '<', hexadecimal value 0x3C, is an invalid attribute character. User is able to bypass the error message but only the first page of the document displays.

Cause

This issue was caused when a Result Entry Profile Table, ^nt("rp"), Numeric data element, Reference Range Constants field was defined with a value containing a greater than > or less than < symbol.

Additionally, if the result was populated by a foreign system inbound interface that included either the less than or greater symbol, < or >, and the result was mapped to an event processed by the Continuity of Care Document Creation application, an error would occur because the field was not formatted to replace the reserved character in XML.

Resolution

Reference ranges defined for a result profile's Numeric data element field now display properly when creating a Continuity of Care Document.

829808 Summary

HTML report in an external browser window does not close when CDA logs off

Symptoms

For HTML ^AHFS reports, the External Browser tag within the HTML header can be used to force the report to launch in a separate Internet Explorer® web browser window, defined within Microsoft Windows®. This may be helpful to launch links which require additional functionality unavailable within the limited browser session used by the Clinical Desktop Application (CDA).

Cause

Upon launching an HTML report, the window was embedded in Clinical Desktop Application (CDA). However, the client had written a custom report that launched an additional report using a URL (Uniform Resource Locator) reference in an additional Internet Explorer window, separate from CDA. When the user logged off or closed CDA, the expectation was that all the Internet Explorer windows would close as well. Using the HTML tag  changed the way CDA handles an HTML report in the internet browser. However, the internet browser did not close when a user logged off the CDA application. Additionally, when an HTML report was defined with the HTML tag <!—EXTERNAL BROWSER-->

Resolution

For HTML ^AHFS reports, the Enhanced Browser HTML tag within the HTML Header can be used to force the report to launch to an Internet Explorer browser window within the Clinical Desktop Application session. This allows the user to launch links requiring additional functionality unavailable within the limited browser session used by the Clinical Desktop Application (CDA) and enables the CDA session to control the behavior of the window.

Example of usage:

<HTML>

<HEAD>

</HEAD>




831845

836574

836583

Summary

Patient cautions or allergies did not consistently update

Symptoms

Face Sheet storage does not display current documented data as documented.

This issue was identified specifically for Face Sheet Storage Links defined in the System Parameter Table, %z, REG/ADT System Parameters subfile, Facility-specific level, Header Strip Definitions screen, Patient Med Allergies and Other Caution(s) fields.

Cause

An issue was identified in the Result Entry Profile Table, ^nt(“rp”), Selection Table data element field. When the Selection Table data element was defined with a Face Sheet storage, the data was not cleared consistently upon selection.

Resolution

Face Sheet storage for the Result Entry Profile Table, ^nt(“rp”), Selection Table data element and the Assessment Category/Data Element Table, ^nt("ac"), Allergy Name data element now clears consistently upon selection in the Patient Schedule menu function.

838273 Summary

Selections did not display when the user attempted to select an option defined in the Controlled Medical Vocabulary Pick List Table, ^nt("cvpl")

Symptoms

Users are unable to pick options in a field created from the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element when the options were defined in the Controlled Medical Vocabulary Pick List Table, ^nt("cvpl"). A blank line displays instead of the list in the table.

Users are able to expand to search by the exact code.

Cause

When a coding scheme was defined in the Result Entry Profile Table, ^nt("rp"), Controlled Vocabulary data element, Coding Schemes Constants field, a selection did not display when the user attempted to select an option defined in the Controlled Medical Vocabulary Pick List Table, ^nt("cvpl"), in a field created from the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element.

Resolution

Selections now display when an option is selected as defined in the Controlled Medical Vocabulary Pick List Table, ^nt("cvpl"), in fields created from the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element.

838324

838382

Summary

No ‘Now’ event sent to Pyxis from the Department Order Review Queue application

Symptoms

When an Initial Event is added in the Department Order Review Queue application for a scheduled event time of ‘now’, the Pyxis Outbound Interface order start time does not reflect the added initial event.

Cause

An issue was identified when the user selected the Initial Events processing option in the Department Order Review Queue application. When the user selected to add an event and entered ‘now’ for the scheduled event time, the initial event was not filed. As a result, the Pyxis Outbound Interface order start time did not reflect the added initial event.

Resolution

The Department Order Review Queue application has been updated so that an event is created with the scheduled event time of 'now' when the user selects the Initial Events processing option. The start time is equivalent to the time specified by the ‘now’ event during initial event editing.




838737 Summary

System performance issue displayed an ‘Out of Resources’ error message

Symptoms

System performance on specific Application Server Groups is slow. The Job Monitor menu function hangs for a minute when loading, and many jobs appear to process in an infinite loop. Error messages display an ‘Out of Resources’ message for multiple users.

Cause

A specific data sequence displayed when the Patient Schedule menu function was configured with a Chart Review Group filter, so that events were displayed across patients. This caused performance degradation due to several system jobs running in an infinite loop.

Resolution

The Patient Schedule menu function has been updated to resolve the data condition causing the infinite loop.

838762 Summary

Report Type field is blank in CCDA and Krames interface cancelling a document

Symptoms

An outbound message for CCDA and Krames interface displays in the View Interface Transactions, Status, and I/O menu function and the Report Type field is blank when the user cancels the document.

Cause

When the user cancelled the document, the cancellation process resulted in the ‘title’ information being unavailable in its normal location.

Resolution

The View Interface Transactions, Status, and I/O menu function application has been modified to display the title for cancelled documents.

To test, you need a functional CCDA and Krames interface:

1. Stop the interface.

2. Using the Document List application, save a document and mark it ‘allow online access’.

3. Cancel the document.

4. Using the View Interface Transactions, Status, and I/O menu function, observe that there is an unsent message and that the display is correct, both in the normal and ‘expanded’ view.

5. Start the interface.

6. Using the View Interface Transactions, Status, and I/O menu function, observe that the display is correct. (The message should not be included in the ‘expanded’ view, since that only includes unsent messages.)

7. Repeat steps 1-6, but omit step 3. (This is the regression testing, to ensure that uncancelled documents are handled properly.)








ENH The following reports have been created for clients who have purchased the ePrescribing Module:

GEN - Discharge Medication Statistical Usage Report - The report counts the discharged medications and prescriptions documented within the Home Medication Editor menu function, as well as Procedure Table, ^t, discharged medications.

GEN - Discharge Medication Statistical Usage Download Report - The report counts the discharged medications and prescriptions documented within the Home Medication Editor menu function, as well as Procedure Table, ^t, discharged medications.

GEN - Discharge Medication Print Report - The report prints the discharge medication(s) or discharge prescription(s) to give to a patient and/or for the hospital records.

824786 Summary

Medications that had an Rx name longer than 100 characters created formatting issues with the display name in the Continuity of Care Document (CCD).

Symptoms

When creating the Continuity of Care Document, the medication section creates a formatting issue that generates several unnecessary pages.

Cause

The RxNorm Name for some products included more than 100 characters because each component was included in the RxNorm text. For example: RxNorm code 854977 listed each component of the Pneumococcal Vac Polyvalent Injection.

Resolution

When a procedure is displayed on the CCD with a mapped Rx Norm product name containing more than 100 characters, the CCD will now display the Procedure Name as defined in ^t, Product Identification, Procedure Name.

828808 Summary

An issue occurred in the Continuity of Care Document (CCD) when a data element was documented from the Allergy Symptom Table - ^pt(“ads”). The allergy symptom that allowed for free-text entry of symptoms was not mapped in the Concept Mapping Tool application. The data element did not display the symptoms documented.

Symptoms

When creating a Continuity of Care Document, the document does not pull all free-text information for allergy symptoms/reactions.

Cause

The Allergy Symptom Table data element, which allowed additional, free-text documentation of allergy symptoms, prevented the complete display of the CCD when it was not mapped in the Concept Mapping Tool application.

Resolution

When allergy symptoms defined in the Allergy Symptom Table are not mapped in the Concept Mapping Tool application, the CCD will now include the same text displayed when the user reviews documented allergies and allergy symptoms in QCPR and in the Chart Review menu function.




836167 Summary

An issue occurred with the ‘ARRA Medication Reconciliation Statistical Report’ when the report was run for ED visit types and Observation Only? = ‘yes’. The report included all Emergency patients, even those that did not have an observation procedure documented.

Resolution

When the report is run, and the Observation Only? is entered as ‘yes’, the report will now display a header of ‘Observation Method Only’ and will only include patients that have an observation procedure documented. If Observation Only? is entered as ‘no’, the report now displays a header of ‘All ED Method’ and the report will include all ED visit type patients.

When the Visit Type field contains ‘SP’ for Short Stay, the report will only evaluate for Medication Reconciliation for the visit type and will not be considered for Observation Status.

836518 Summary

An issue occurred in the Clinical Quality Measures Application (eCQM) when more than 1 medication was documented in the procedure result profile-^nt(“rp”) as ‘Not Given’ (medication discharge not done) at discharge. If multiple medication not dones were documented with a Reason Not Given (negation reason code), but one of the documented reasons was not mapped, a code from a different ‘not done’ was incorrectly applied to the unmapped field. This caused the patient to have ‘not done’ documentation that passed criteria it would have otherwise failed due to the unmapped reason.

Symptoms

Medications documented as ‘Not Given’ without a Reason Not Given were evaluated as if a Reason Not Given had been documented. This incorrectly excluded patients incorrectly from the AMI-2 numerator.

Resolution

Code was updated to leave the negation code blank if the choose/^ntt option is not mapped.

836668

837619

Summary

During the creation of a procedure event for audit purposes, when an external document(s) was saved using the save button, the HTML snapshot report, which is uploaded into a Multimedia data element on the result profile for the procedure, did not display.

Symptoms

During the creation of a procedure event for audit purposes, when an external document(s) was saved using the save button, the HTML snapshot report, which is uploaded into a Multimedia data element on the result profile for the procedure, did not display.

Clinical Information Reconciliation Application is created in âtdta

Reconciliation Data Type(s) field is set to ‘All’ in Desktop Application table âtdta

Define Consolidated Med List App field in Desktop Application table âtdta

Define Problem List App field in Desktop Application table âtdta

Specify a procedure in ^%z, Order Comm. System Parameters subfile, Facility-specific level, Miscellaneous Parameters screen, Clinical Reconciliation Procedure field.

1. Click on the Patient List application.

2. Enter the patient name and click on the search button.

3. Select the patient and click on the Go to Patient button.

4. Select a visit and click on the Go to Visit(s) button.

5. Launch the Clinical Information Reconciliation application.

6. Verify the display of the External Documents drop down.




7. Verify the display of each document present under the External Documents drop down.

8. Click the 'SAVE' button on the Left Side Document.

9. An HTML report snapshot of the reconciliation performed on the left pane is created for all selected documents, including the following:

a. Name and status of each document selected as part of the reconciliation

b. Status of each section within each document

c. The indicator/mark (e.g., check) on the left side of which data items were reconciled for each section of each document.

d. Any comments entered for any data items within a section of a document.

10. Return to a document that was previously reconciled in some form (in progress or complete).

11. Create an unscheduled procedure for audit purposes of the reconciliation process.

12. The GEN – HTML Clinical Information Reconciliation Hook Report is uploaded into a Multimedia data element on the result profile for the procedure.

13. Review the event from the Chart Review application. Notice that the HTML snapshot report that is uploaded into a Multimedia data element on the result profile for the procedure does not display.

Cause

When the Result Profile, Multimedia Data Element Type, Constants, Report definition subfield was configured with the GEN – HTML Clinical Information Reconciliation Hook Report, the multimedia object code was not stored in the Result Profile Multimedia Data Element field, causing the report to not display after an event was documented.

Resolution

An issue was resolved with the Multimedia Data Element Type Report Definition field when configured to use the GEN – HTML Clinical Information Reconciliation Hook Report. The multimedia object code was not stored in the Result Profile Multimedia Data Element field, causing the report to not display after an event was documented.

837552 Summary

The eCQM application was not considering the IV solution Procedure Type for VTE-4 measure

Symptoms

An issue occurred in the Clinical Quality Measures Run menu function (eCQM) when run for VTE-4 (Venous Thromboembolism Patients Receiving Unfractionated Heparin with Dosages/Platelet Count Monitoring by Protocol or Nomogram) where the Procedure was defined for a Heparin Protocol as an IV solution in the Procedure Table ^t, Facility Level, Department Processing sub-file, Procedure Type field then the Clinical Quality Measures Application (eCQM) application was not considering the IV solution route for the event.

Additionally an issue occurred in the Clinical Quality Measures Run menu function (eCQM) when a Result Profile, choose data element was mapped in the Clinical Concept Mapping tool to the “Treatment adjusted per protocol” SNOMED-CT code the Clinical Quality Measures Run menu function (eCQM) did not consider the IV solution route for the event.

Cause

The Clinical Quality Measures Run menu function (eCQM) was not considering the IV solution Procedure Type.

Resolution

The Clinical Quality Measures Run menu function (eCQM) has been updated to consider the IV solution Procedure Type.




837711 Summary

An issue occurred for HL7 Orders Interface when changes were made to orders scheduled for a future date and time. The orders were being sent immediately to receiving systems such as Pyxis.

Cause

There was an issue with the order scheduler component which caused changes to be sent with the original order start date and time.

Resolution

Interface messages for change orders that have no change in frequency will now be sent no earlier than the effective date/time of the change. Additionally, if the frequency of the order included ‘and then’ and ‘followed by’ these terms will now be skipped if already completed or if the change order is written before these terms start.








ENH An enhancement has been made to the Report Formatter Data Dictionary, ârfd. The 'table edit archive:edit number:mailing code location' record has been created to record when a given mailing code/location association has started or ended.

ENH SNOMED-CT UK, ICD-10-4E, and ICD-10-UK are now available. The tables are provided by the third-party vendor, Health Language, Inc. (HLI). The users configure the coding schemes for each problem list type defined in the Problem List Type Table, ^nt(“plty”), Coding Scheme Definition field, Primary Code Scheme or Secondary Code Scheme(s) subfields.

ENH An enhancement has been made to the System to allow multiple entries for Medi-Span API URLs.

An Add/Delete Editor has been added to the System Parameter Table, ^%z, Order Comm System Parameter subfile, System-specific level, Pharmacy Parameters screen, Server URL field to allow multiple URLs to be defined. QCPR attempts to connect to the first server on the list. If the System fails to connect, and more than one URL is defined, the System attempts to connect to the next one on the list. The System continues down the list until it either connects or there are no more URLs identified. When no connection is made, the System returns an 'unavailable' error.

781022 The Report Formatter Operator Table, ârfo, ‘Hash String’ operator has been created to allow clients to hash data to pass into URLs.

The operator expects the following two parameters:

• Bitlength: Length in bits of the desired hash.

Acceptable values are: 160 (SHA-1), 224 (SHA-224), 256 (SHA-256), 384 (SHA-384) or 512 (SHA-512)

• Text: String to be hashed.

String content can be URL, Name, Password, etc.

The operator returns a readable hex string.

The syntax for calling this operator in an expression field is as follows:

hash string(160,’string’), where 160 is the integer for one of the allowable bit lengths and ‘string’ is the string to be hashed.

825605 An issue occurred with the GEN - Data Security Realtime report. The audit information was not included in the report.

Run AF Loop 35 'rebuild âlog event types’.

831399 An issue occurred in the Home Medication Editor menu function. When an active procedure existed for the same drug selected in the Medication field, the System incorrectly displayed the Default Dosage Selection screen defined in the System Parameter Table, ^%z, Order Comm System Parameters subfile, Facility-specific level, Consolidated Medication List Parameters screen, Selection Screen/Tree Table Definition field, Dosage Selection Screen subfield. The Dosage Selection Screen defined in the Procedure Table, ^t, Product Information screen, Medication Component(s) field, Component Definition screen, Dosage Definitions field, Dosage Selection Screen subfield should have displayed.




835282

835431

837874

The following issues occurred in the Clinical Quality Measures Run menu function:

When interpreting data for VTE-1 and VTE-2, patients who had a surgical procedure code that matched the documented principle procedure code should have been excluded from the VTE measures. However, these patients were included.

SNOMED code 445060000 was not internally mapped to SNOMED code 30164005 (specifically for AMI quality measures). This incorrect mapping caused patients with a discharge type of ‘Against Medical Advise (AMA)’ to be included.

Previously, events for non-medication procedures that were cancelled or documented as 'not done' were not evaluated in the Clinical Quality Measures Run menu function. The original logic looked for 'not done' in a result profile. Now, events that are cancelled or documented as 'not done' are also evaluated based on the following new fields in the Procedure Table, ^t, Cancel/Resolve/Reschedule Information screen. These new fields enable codification of events that were cancelled because the procedure was not performed. This new cancel solution requires mapping with the reason code continuing to be based on the cancel reason mapping. The new fields are described below:

Cancel Coding Scheme(s) – Defines the code used to identify a cancelled event that was not performed. When this field is defined, and an event for the procedure is cancelled, the System stores the defined code to be evaluated in the Clinical Quality Measures Run menu function. When this field is not defined, no code is stored and the cancelled event is not codified nor evaluated in the Clinical Quality Measures Run menu function.

The code for the reason why an event was cancelled is still defined in the Selection Screen Table, ^nt(“s”), Cancel Screen subfile. The code for the data topic (e.g., device applied to the cancelled event) is based on the code defined in this new field.

The following fields provide new options to enforce the collection of codified data on the Cancel Comment screen for Quality Measures.

Allow Cancel Freetext? – Defines whether the user can document a free-text reason when cancelling an event for the procedure. This field is not required and displays only when the Cancel Comment Screen field in the same screen is defined.

Allow Cancel Multi-Select? – Defines whether the user can select multiple cancel reasons when canceling an event for the procedure. This field is not required and displays only when the Cancel Comment Screen field in the same screen is defined.

837398 An issue occurred in the Order Entry application, the Department Order Review Queue application, and the Department Order Review Queue menu function. When the user’s facility did not match the patient’s facility, the System generated a ‘null pointer exception’ error.

838174 The Problem List Mapping tool has been enhanced to now run on QCPR releases 6.0.1 and higher.



The following AF loop needs to be run for this update:

Rebuild ^alog event types





N/A Crosswalk data for SNOMED to ICD-10 is now available. The crosswalk is provided by the third-party vendor, Health Language, Inc. (HLI).

The crosswalk is invoked when a user selects a term/code to add to the patient's problem list. The System uses the selected code as the primary coding scheme and automatically retrieves any secondary codes from the crosswalk.

Client users configure the secondary coding schemes for each problem list type defined in the Problem List Type Table, ^nt("plty"), Coding Scheme Definition field, Primary Coding Scheme or Secondary Coding Scheme(s) subfields. Once the user configures a secondary coding scheme, the crosswalk data is available/licensed.

833289

835661

The following issues occurred in the Continuity of Care Document CCD:

When documented data contained an ampersand (&) sign, a 'Bad xml' error was generated.

The text '(Pending)' displayed in the Results section when the ordered procedure had a result profile defined with one data element. When another procedure was present and the result profile contained more than one data element, the text '(Pending)' did not display on the first procedure.

834291 An issue occurred in the Order Entry application, Consolidated Medication List tab. When home medications were copied to visit medications, and the home medication had a dosage containing a decimal value to the thousandth, or three-digits, only the first two decimal places were copied.

834780

834986

836432

836573

836595

837256


When one of the records in the population for the run had an error, the run did not complete. Now, when a record has an error, the run continues until complete and displays the status of 'Complete with Errors'. The errors can be reviewed by clicking the (E) View Errors processing option.

The documentation of why a discharge medication was not given caused the run to err due to an incorrect OID.

When a visit contained an EP to IP to EP conversion, and the final EP visit was still open, the System generated the '<zddif>' error.

Documentation related to Stroke Education was not included. The issue occurred when an assessment screen used for education documentation in the Assessment Screen Table, ^nt("as"), contained an Assessment Category/Data Element Table, ^nt("ac"), Multiple Field Assessment data element.

835021 There was an issue in the Problem List application. When a user selected a problem, and then selected an order set from the Order Entry application, Order Selection tab, the problem did not populate the field created from the Order Entry Profile Table, ^nt(“op”), Active Problem(s) data element.

835042 An issue occurred in the Canadian Medi-Span Flat file when running the loop to populate the Procedure Table, ^t, Product Information screen, Medication Component(s) field, DKV Drug Name(s) and DKV AHFS Class(es) subfields. The loop failed to populate the fields.

Run AF Loop 'populate Procedure Table, ^t, DKV Drug Name(s) field and AHFS Class(es)' after loading the updated global ^pmedf.

836989 An issue occurred in the Chart Review menu function. When the Procedure Table, ^t, Chart Review Information screen, Result Suppression field was defined as 'partial', 'unverified', or 'both partial and unverified', partial results did not display. However, when the (B) View/Search processing option was clicked, the suppressed results displayed.

837047 An issue occurred in the Instrument Interface View Utility menu function for customers with Condo functionality. When attempting to view a specimen, the System generated a ‘global subscript length error’.

837286 An issue occurred in the View Interface Transactions, Status, and I/O menu function. When a secondary number was defined to be used as the patient number, the secondary number did not display as the Medical Record Number in the View Interface Transactions, Status, and I/O menu function or in the message detail of the interface transaction. The issue occurred when interface messages were sent between facilities and one facility had the secondary number defined as the patient number and the other facility did not.




837782 An issue occurred in the Solution Maintenance menu function. When IV solutions were dispensed from floor stock, the Solution Maintenance menu function, IV Order Display screen, Solution ID column displayed the value as ‘1000000000…’ (the zeros continued on). The value caused any report that contained solution IDs to print a large number of pages.

Now, when an IV solution is dispensed from floor stock, the text ‘flr stk’ displays in the Solution ID column.



The following AF loop needs to be run for this update:

SNOMED to ICD10 crosswalk needs to be loaded before running Af Loop 57 ‘add ICD10 codes to existing snomed problems’





744238 An issue occurred in the Film/Chart Checkin menu function. When a ‘partial’ check-in was performed on an individual volume, the entire folder was checked in.

784362 An issue occurred in the Personal Procedure Selection Tree Table, ^nt(“psp”). A 'Missing $true condition error in %zu2t%f' error was generated when a procedure was added to the Personal Order level, Procedure field.

807364 An issue occurred in the Order Entry application when configured to ‘order/print/collect’ laboratory orders.

When the System Parameter Table, ^%z, Reg/ADT System Parameters subfile, Facility-specific level, Miscellaneous Data screen, Recent Downtime Processing? field was defined as ‘yes’, and a lab specimen order was accepted, the user was unable to enter a specimen number or select ‘Auto Assign’, as these options were missing from the screen. The System now displays check boxes for ‘Auto Assign’, ‘Unknown Collector’, and ‘Unknown Collection Date’. Logic has been added to prevent a duplicate specimen number from being entered.

823188

834327

An issue occurred in the Medication/IV Administration menu function when barcoding was enabled. When more than one drug was selected to be administered, and the drugs all had the same name, the list of ‘Matching Events’ displayed without the procedure name.

829811 An issue occurred in the Drug Query (API) application, when launched from the main desktop. Only one product from a medication order with multiple components allowed selection of Drug Information or participated in alert checking.

The Drug Query (API) application has been enhanced. The Medication Column has been added to the Drug List frame on the Dose Query screen to now display the procedure name for the order. The screen now displays a row for each component of the order. The Medication column can display the same information in multiple rows, with the corresponding product in the Product column. Each row can be selected to view Drug Information.

For example:

Medication Product

Demerol/Vistaril Demerol 50 mg injectable

Demerol/Vistaril Vistaril 25mg injectable

831712

831715

832462

An issue occurred in the Electronic Mail menu function and in the E-Mail application that prevented users from copying text from an email message into a Word document.

Users can now copy text from a QCPR e-mail when the e-mail is generated by a user. When QCPR generates the e-mail, it cannot be copied.

833016

833252

833595

835945

833612

The following issues occurred in the Continuity of Care Document (CCD):

When laboratory results were displayed, the Values column displayed an asterisk “*” instead of the numerical result value.

When a resulted item was defined to be included on the CCD, it did not display as expected when statused as ‘partial’.

The Vaccine Refusal information did not display when the data element fields had been rearranged on the result profile.

When more than one symptom was documented for an allergy, the CCD failed validation.

833990 An issue occurred with Drug Product Selection when performed from the Order Entry application, Order Entry menu function, and Department Order Review Queue application or menu function. The issue prevented the correctly suggested drugs from being selected by the System and required the user to select them from a list of products linked to the procedure being ordered.




834386

834490

835996

An issue occurred in the Clinical Quality Measures Run menu function. The report runtime was extensive when a visit record included in the criteria was part of a patient merge.

834452 An issue occurred in the Order Entry application. The ‘Unhold’ processing option was not available when the user attempted to ‘unhold’ an order that was in a 'Hold' status.

834777 An issue occurred in the Medication/IV Administration menu function, when barcoding was enabled. When the user chose to override the product confirmation instead of scanning the selected medications for documentation, if the result profile contained required fields, the user was brought back to the eMar after pressing Enter. The medications previously selected remained undocumented.

835255 The following issues occurred in the GEN – HTML Patient Medication Discharge Instructions' (rev3) report:

The Prescription Order, Rx Instructions was not included in the report.

The Quantity reflected the total quantity across all fills of the prescription, rather than the quantity to be dispensed for the new prescription and each refill.

836159 An issue occurred with order profiles. When an order profile contained a field created from the Order Entry Profile Table, ^nt("op"), Rx Number Of Refills data element, the field displayed for procedures defined for order entry instead of prescriptions.

836307 An issue occurred with the Assessment Category/Data Element Table, ^nt("ac"), Patient Education data element. When Krames was not in use for patient education information, and the Patient Education data element was documented, the System generated a 'global subscript' error.

836697 An issue occurred in advisory alert checking. After Advisory Warning Checks were performed, a 'global subscript length' error occurred when there were duplicate alerts and the resulting alert had more than 255 characters.

836841 An issue occurred in the Order Entry application. A Java error occurred when the user attempted to save an order to ‘Favorites’.

836983

836995

An issue occurred in the Order Entry application when the frequency was defined as a 'Now' dose. When the 'Now' dose was added at the end of an order entry session, prior to accepting the order, the 'Now' dose was not sent to Pyxis. If the order was entered with a frequency of 'Now and then', the dose was sent to Pyxis.

837099 An issue occurred in the Product Pricing Barcode Maintenance application. When users were verifying barcodes, an error was generated that prevented the unverified barcodes from being verified.

837323 An issue occurred in the Order Entry application. When users were writing discharge prescriptions, the order type defaulted to ‘order’, even though the Desktop Application Table, ^at("dta"), Order Entry application, Non-Facility Parameters, Primary Order Type field was defined as ‘prescription’.

837325 An issue occurred in the Word Processor data element. When users attempted to document an event that contained the Word Processor data element, and the data element contained information that was previously copied forward, a java error was generated. The issue occurred with both the Result Entry Profile Table, ^nt("rp"), and the Assessment Category/Data Element Table, ^nt("ac"), Word Processor data elements.

No screen rebuild is required.

837334 An issue occurred in the Result Entry Profile Table, ^nt("rp"), Controlled Vocabulary data element. When a coding scheme was defined in the Coding Schemes Constants field, a 'coding server unavailable' error was generated when the user documented the field created from the Result Entry Profile Table, ^nt(“rp”), Controlled Vocabulary data element.




The following screens need to be rebuilt:

order profiles






815145 When building all the translated components from the Alternate Language Translation utility, the job aborted with numerous errors.

822195 An issue occurred in the Physician Inbox Across Patients and Physician Inbox applications. Result review items were not routed to the physician when the following scenario occurred:

1. The physician placed the order, but had no association to the patient (that is, was not defined as the attending, consulting, etc.)

2. The procedure linked to the order had the following Procedure Table, ^t, Chart Review Information screen fields defined:

Result Suppression field defined as ‘both partial and unverified’

Queue Routing? field defined as ‘yes’

3. The event status went through the following documentation sequence:

Partial

Unverified

Complete

Unverified

Supplemented

4. The supplemental information was documented using the Result Verification menu function

827214 An issue occurred in QCPR when interface messages were sent to Pyxis. The System sent the incorrect start date and time. For example, when a daily order was entered at 11:00 am today, and the default daily time was today at 09:00 am, the first event to be scheduled is tomorrow at 09:00 am. The interface message sent the start date and time as the current day (today) at 09:00am.

833588

836006


When users selected ‘New’, entered information into the screen driver fields, and accepted the information, the report did not display. The report did not fully execute because there was an event that had several CMV codes defined for the Principal Procedure screen driver field.

A java error occurred when attempting to run the Clinical Quality Measures Run menu function.

833600 An issue occurred in the Continuity of Care Document. When ‘No Known Allergies’ were documented for a patient, the Adverse Event Type field displayed ‘Allergy to substance (disorder)’ instead of the text ‘No Known Allergies’.

836311 An issue occurred in Alert Checking. After Advisory Warning Checks were performed, an error occurred when the resulting alert had more than 255 characters.

836684 An issue occurred in the Consolidated Medication List application (within the Order Entry application). When a visit medication was copied to a prescription, an error occurred, which prevented the prescription from being produced.








N/A During the administration process for multi-component medications (e.g., IVPB antibiotics), when one component has been processed (i.e., scanned, overridden, commented upon, etc.), the System proceeds with processing the components that follow. If the user is presented with an override for any subsequent components during processing, and the user decides not to override that component, the System returns the user to the Medication/IV Administration menu function, Product Scan Summary screen without voiding the processing for any prior components.

832211 An issue occurred in the Order Entry application. When events were ordered using the procedure name, the procedure name did not display on reports printed from the Resource Schedule View/Print menu function.

833956 An issue occurred with the Continuity of Care Document (CCD). The Encounter section of the report was missing dates and times.

835004 An issue occurred when a Continuity of Care Document (CCD) was exported. HTML errors occurred preventing the document from being exported.

835008 An issue occurred in the Document List application. When a microbiology lab result was recorded as free-text for an organism, the System generated an error message instead of producing the document.

835013 An issue occurred in the Product Table, ^pt(“p”), Facility-specific level, Charging & NDC(s) Definitions field. When charge information was edited and the user clicked (A) Accept, instead of saving the information, the QCPR session ended.

835070 An issue occurred with Multiple Field assessment data elements. The issue caused results to display as abnormal when they were within normal limits.

835309 When a patient is registered in Affinity, the interface does not send over the country code if it matches the system default. In most parts of QCPR, the default country code is displayed when this occurs. There was an issue with creating accounts for Patient Access Module (PAM) for these patients, presenting an error ‘Country is required’ message. The application has been modified to use the default country code in PAM account creation if it is not specified on the patient record.

835322 An issue occurred with generating a Continuity of Care Document (CCD). When the Continuity of Care Document (CCD) contained a documented Home Medication with no product, the lack of product prevented an RX Norm Code from being associated to the Home Medication, causing an error.

836045 An issue occurred with Multiple Field result profile data elements. The issue caused a Java Error to be generated which prevented trend data from being reviewed. The issue occurred when the Multiple Field result profile data element was defined to accept a free-text entry, and the user entered free-text that contained more than one comma (for example, AC-VC,,).


The following screens need to be rebuilt:

Assessment multiple field screen drivers (^nt(“ac”))






N/A An enhancement has been made to the System to allow multiple entries for Medi-Span API URLs.

An Add/Delete Editor has been added to the System Parameter Table, ^%z, Order Comm System Parameter subfile, System-specific level, Pharmacy Parameters screen, Server URL field to allow multiple URLs to be defined. QCPR attempts to connect to the first server on the list. If the System fails to connect, and more than one URL is defined, the System attempts to connect to the next one on the list. The System continues down the list until it either connects, or there are no more URLs identified. When no connection is made, the System returns an 'unavailable' error.

825714 An issue occurred in the Patient Priority List menu function. When a patient was placed on a specific wait list, then moved from one wait list to another, the System displayed the (A) Accept processing option before the user selected the new waitlist. When the user clicked (A) Accept before selecting the new waitlist, the original wait list entry was lost.

The (A) Accept processing option now displays after the new wait list is selected.

830052 An enhancement has been made to the System to prevent the use of free-text for alert comments. The prevention of free-text is now based on configuration. The following enhancements have been made to the System Parameter Table, ^%z, Order Comm System Parameters subfile:

System-specific level, Miscellaneous Parameters screen, Advisory Comment Definitions field, Allow Free-Text Advisory Comments? Subfield has been added to define whether users can enter free-text comments for non-DKV alerts. This subfield defaults to ‘yes’, allowing free-text comments to be entered. When defined as ‘no’, users cannot enter a free-text comment for non-DKV alerts. The System displays a list of Advisory Comments and prompts for an option to be selected. The Advisory Comment Table that displays is defined in the Advisory Comment Definitions field, Advisory Comment Table subfield.

Facility-specific level, Drug Knowledge Parameters screen, Advisory Comment Definitions field, Allow Free-Text Advisory Comments? Subfield has been added to define whether users can enter free-text comments for DKV alerts. The subfield defaults to ‘yes’, allowing free-text comments to be entered. When defined as ‘no’, users cannot enter a free-text comment for DKV alerts. The System displays a list of Drug Advisory Comments and prompts for an option to be selected. The Drug Advisory Comment Table that displays is defined in the Advisory Comment Definitions field, Drug Advisory Comment Table subfield. The Drug Advisory Comment Table field previously existed on the Miscellaneous Parameters screen. It is now a subfield beneath the Advisory Comment Definitions field.

831815 An issue occurred where background jobs were identified incorrectly. Multiple entries of the Audit Viewer application were identified as performed by 'System Startup (IPL)' when no system activities were present during that time. The Audit Viewer and Audit History jobs are now identified as performed by 'Caretaker'.

832564 An issue occurred in the French Canadian implementation of QCPR. When processing orders in the Department Order Review Queue menu function, users were unable to select a medication from the list by double-clicking or by selecting the row number and pressing Enter.




832858

833301

833333

833335

833546

833591

834119

834451

834677

835347

An issue occurred in the Department Order Review Queue menu function and application. When an order was changed using the Change Order functionality, the System failed to perform drug product selection. As a result, the pharmacist was required to manually perform drug product selection.

834464

834780

834982

835122

835231


When the Decision to Admit Date/Time procedure was documented as an unscheduled procedure or filed as unscheduled (as a result of an ADT message from a third party system), the logic did not look for data recorded using an unscheduled procedure.

Data was not captured when the Assessment Data Element/Category Table, ^nt(“ac”), Multiple Field data element was defined as either a Choose or Hard Coded Selection Screen.

Data regarding diagnostic study result markers was not captured.

When a patient had medication included in the quality measure criteria, and one medication had been documented as ‘not done’, no more checking was performed for additional medications documented as ‘not done’.

Patients with ICU levels of care were not evaluated correctly when the inpatient admission date/time was the same as the ICU level of care start date/time.

834582

834758

834759

834841

835015

835024

The following issues occurred in the Product Pricing Barcode Maintenance application:

When barcodes were scanned, a 'bad transaction proxy' java error was generated.

The textbox to manually enter barcodes did not display.

Newly entered barcodes were auto-selected as the 'primary barcode'.

When the checkbox was deselected and filed, the barcode continued to display as the primary barcode.

834659 An issue occurred in the French Canadian implementation of QCPR. When accessing the Growth Chart Percentile Table, ^nt("gcp"), no percentiles displayed.

834793 An issue occurred in the Order Entry menu function when defined to allow ordering, printing, collecting, and accessioning. When specimens were processed using the configured Order Entry menu function, outbound interface messages were not generated.

The Order Entry menu function now calls the correct Collection Interface hook.

835107

835241

An issue occurred with DKV checking. When a medication order for Zosyn was placed for a patient, the user was unable to accept the order.

The DKV message sent from Medi-Span for the patient was greater than 512 KB.

The issue was a rare occurrence. The messages that were returned were based on the patient's profile and medications. The System can now handle messages greater than 512 KB.