Features
Formulary Setting: Refrigerator Timer Options
There is now a formulary setting that enables Hospitals to decide whether a Refrigerator Expiration Timer is automatically started upon Tagging. The Options are Always, Never, and User Decision - which allows the user to decide whether or not to start the refrigerator timer at the time of Tagging.
For Always or Never, the Start Refrigerator timer is greyed out with the chosen option shown. For User Decision, the Start Refrigerator functionality is accessible and the user is able to toggle it on or off.
Updates & Fixes
Update: Faster Load Time: Kits Page
This update greatly increases the speed at which the Kits page will load. The Search Bar for Physical Labels has been moved to the left, aligned under the Kit Master, Location, and Cart filters.
Update: Error Messaging — Batch Verification
There is an update for error messaging when the same user who associated a batch attempts to verify the batch. Previously, the error message simply stated 500 Internal Server Error. Moving forward, the error message will read: The same user who tagged the item cannot verify it.
Fix: Optional Fields do not Allow Blank Spaces
This update fixes an issue with how entities within KitCheck are named. Specifically, KitCheck would produce an error whenever a user attempted to name an entity with a string solely consisting of spaces. The entity’s name would not be updated, although no explicit error was shown. Moving forward, KitCheck will now display the same error as when a User attempts to enter a “null” string as an entity name and the name will not be updated.
Fix: FX9600 Reader
This update fixes issues related to the FX9600 reader. Specifically, there was an issue where an “interrupted scan” would cause the reader to enter a state where subsequent scans would report no items/EPCs even when they should have been detected.
Fix: Charge Sheet, Billing Sheet, Pick List Font Size
This update fixes an issue where Charge Sheets, Billing Sheets, and Pick List were printing with small font. This issue was caused by an update in web browser configurations.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article