Procura®7 Release Notes Procura Health Management Systems Copyright © 1992-2011 Procura. All rights reserved Procura Version :Document: Date Created: Doc. Version: 7 Release Notes 2016-03-08 v.7.02 Corporate Office Victoria, BC 623 Discovery Street Victoria, BC Canada V8T 5G4 T :1.877.776.2872 F: 250.380.1866 U.S. Headquarters 900 Oakmont Lane, Suite 308 Westmont, IL USA 60559 T: 888.428.6614 F: 250.380.1866 www.goprocura.com Australian Headquarters 50 Sylvan Rd, Unit 1 PO Box 1000 Toowong, QLD Australia 4066 T: 07.38702852 F: 07.3870.2835 Confidentiality and Distribution Limitations Intended Recipient The information contained in this document is privileged and confidential information intended for the use of the individual or entity to which it is distributed by an authorized employee of Develus Systems Inc. If you are the reader of this document and did not receive it directly from an authorized employee of Develus Systems Inc. or if you are not an employee or agent who is responsible to deliver this document to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this document is strictly prohibited. Confidential Information, Distribution Limitations This document is submitted by Procura (incorporated as Develus Systems Inc.) in good faith guided by the following principles: This document is for informational purposes only and does not constitute a contract or an offer to contract. Copyright of this document is retained by Procura, and Procura hereby grants the intended recipients (known hereafter as the “Customer”) unlimited rights to copy and distribute this document to evaluation staff and advisors under the following conditions: 1. The Customer will consider this document to be confidential and proprietary to Procura and will not release this document to any persons, other than internal evaluation staff and advisors, without first obtaining Procura’s express written permission. 2. The Customer agrees that all information contained in this document, and any additional information supplied by Procura, is confidential and proprietary to Procura and is presented solely for use by the Customer for the purposes of review and analysis. The Customer agrees that other use thereof, including disclosure of this information to third parties, is strictly prohibited without the expressed written consent of Procura, except under the following conditions, where all conditions must be present: a) The express, prior written consent of Procura has been requested and received; b) The disclosure of information is for the sole purpose of review and analysis; c) All third parties are explicitly named, including: i) Given and Surname, ii) Affiliation to the Customer, iii) Employer and/or contractor name, iv) Position and title; d) A written agreement is signed by the Customer and Third Parties to respect the proprietary and confidential nature of Procura and all related documentation; e) The Customer will send a copy of said written agreement to Procura prior to the disclosure of the information; and f) The Customer will not make any reference to Procura, or any customers of Procura that are disclosed herein, in any literature, promotional materials, brochures or sales presentations without the express written permission of Procura. 3. The Customer will not assign or transfer any rights and privileges contained in this document without obtaining the written consent of Procura. Procura respectfully requests that should any of the above noted conditions be deemed unacceptable to the Customer, that a representative of the Customer immediately contact Procura for discussion and revision of the conditions before proceeding with the document review. Please contact: Procura Release Team Phone: 1.877.776.2872 E-mail: release@goprocura.com Announcing Procura 7 Procura 7 brings a fresh approach to daily business processes, like scheduling, and continues the product renewal project. That means Procura gets even better with a fresh look and new scheduling features that reduce the workload of coordinators and provide field employees with an easy approach to managing their work. Also in Procura 7, discover functionality like Best Route, the Clinical Day View, workflow improvements and new PASE question types, that have been delivered in voluntary releases. Seven things you can’t afford to miss are: Cut Scheduling Time: Schedule smarter by automating repetitive processes with Procura’s Scheduling Genius. Based on your organization’s rules, it automatically identifies and ranks the most suitable employees to fill a visit. Even when no employee meets all the criteria, because the list is ranked, you still see the most suitable candidates to fill a visit. Reduce the Time to Fill Visits: Offer work to multiple, suitable employees by e-mail or online in the Procura Employee Portal with the click of a button. No more call outs unless an employee specifically wants to be contacted by phone (Procura will keep a record of that too). Easily review the status of all offers and employee’s responses on a single screen to complete a visit booking. Allow Employees to See When They Work: Procura’s Employee Portal helps you put your employees in control. They can check their upcoming schedule, respond to offers of work, change their availability and view pertinent client information online anytime. Automate Processing of CHRIS Offers & Referrals: The Care Information System (CIS) Inbox allows you to effectively manage your CHRIS offers & referrals by pulling them, on demand, into an easy-to-use, inbox-style workspace. Available in Ontario only. Get Ribbonized: Ribbonized menus that mimic the Windows user interface are found through most of Procura 7. Ribbons allow users to take advantage of context-specific toolbars that place key functionality into logical groups for easy access. Your Day at Your Fingertips: Start, end and run your day from your personal home page in Procura – the Clinical Day View. One-stop access to documentation, schedules, client information and much more puts your day at your fingertips so that you can focus on what is important – delivering care – rather than on which screen you are on. Map Your Day: Procura’s Best Route Mileage Guide helps you to reduce mileage costs and optimize scheduling by providing directions to the client’s home based on the best route so that your nurses spend more time with clients and less time on the road. Procura 7- User Release Notes 3 of 155 FEATURE BUSINESS VALUE V6.0 V6.1 Optimize scheduling and reduce mileage costs with Procura’s Mileage Guide. Available in Australia, Canada and USA. Automatically find the best qualified employee to fill a visit with the new Matching Engine. Offer visits to multiple qualified employees, without ever having to pick up the phone. Allow employees to view and update their own availability to work. $ $ V6.2 V7.0 Scheduling & Availability Best Route Scheduling Genius Scheduling Genius Procura Employee Portal $ $ $ Clinical Improvements Clinical Day View Start, end and run your day from your personal home page in Procura – the Clinical Day View. One-stop access to documentation, schedules, client information and much more puts your day at your fingertips so that you can focus on what is important – delivering care – rather than on which screen you are on. Clinical Pathways Ensure consistency of care by providing your clinicians with a standardized plan of care, based on the VNA FIRST Home Care Steps® protocols and/or a care plan defined by you. Easily access a list of clients who are due for review. Care Connection $ $ $ PASE Enhancements Data link question type Image question types Compare image questions Categorize custom clinical assessments Define a multi-column layout Audit log Procura 7- User Release Notes Link directly to data on the Client Information form from a custom assessment. Add images, like wound pictures, to assessments – edit and annotate the image to provide additional information. Directly compare a series of images – for example, review the healing process of a wound. Quickly find the assessment you’re searching for by reviewing specific categories only. Make the most effective use of your space in the window by listing multiple columns on a page. Review who has made changes to the assessment at any time with a comprehensive audit log. 4 of 155 FEATURE BUSINESS VALUE V6.0 V6.1 V6.2 V7.0 $ $ $ $ Operational Improvements CIS Inbox – CHRIS Offers CIS Inbox – CHRIS Referrals Add an Effective Date Streamline CHRIS offers by pulling them, on demand into Procura. Available in Ontario only. Effectively manage your CHRIS referrals by pulling them, on demand, into an easy-to-use, inbox-style workspace. Available in Ontario only. Add a new bill rate with an effective date in the future, a service dated after the effective date will transition to the new rate. Client & Employee Forms Client and Employee Merge User definable statuses Client Vital Statistics Merge duplicate records together. Determine how you want to track your clients and employees. View client vital statistics in a graph. Service Plan Changes Funder-specific configurations Schedule concurrent PRN visits Authorize hours of service Expiry dates Conflict checking Employee Connection Prevent over-scheduling of a service. Ability to schedule concurrent PRN visits. Service plan authorization can include hours of service in addition to visits. Set an expiry date for service plans so you no longer need to calculate the end of a given authorization. Notified if service plan is scheduled below authorized limit. Manage employee requirements in a single location. Workflow Improvements Workflow and Alerts Engine Automatically launch assessments Promote consistency of action and next step adherence & monitoring. Launch assessments on completion of a task like new Client Intake. OASIS Improvements OASIS-C Auto-populate generic questions View/Copy Previous Answer Review Client Record Procura 7- User Release Notes OASIS-C replaces OASIS-B to meet regulatory changes. Generic questions are now auto-populated with the answer from the prior OASIS form. View or copy the previous answer to an OASIS question. Simultaneously work on an OASIS and review a client record. 5 of 155 FEATURE BUSINESS VALUE V6.0 V6.1 V6.2 V7.0 CallMe! Improvements Generate Mileage Expenses Working Alone Alerts Mileage information from Callme! automatically generates an expense and is attached to a visit. Ensure workplace safety, without disrupting care with exception alerts. New Partnerships CellTrak MedShare CareWatch Skynet Procura 7- User Release Notes Mobile solution with cell phones and BlackBerry. Mobile solution with BlackBerry and eMotion. Telephony solution. Telephony solution. 6 of 155 TABLE OF CONTENTS ANNOUNCING PROCURA 7 ........................................................................................................................................................................................................................3 UPGRADING TO PROCURA 7 ....................................................................................................................................................................................................................21 1.2 Pre-Upgrade Procedures .....................................................................................................................................................................................................................21 1.3 Business Preparation ..........................................................................................................................................................................................................................22 1.4 Performing the Upgrade .....................................................................................................................................................................................................................22 1.5 Performing the Installation .................................................................................................................................................................................................................23 1.6 Post-Upgrade Tasks ............................................................................................................................................................................................................................23 1.7 Creating a Procura ‘Lookup’ Version...................................................................................................................................................................................................24 PROCURA 7 ENHANCEMENTS ..................................................................................................................................................................................................................25 1 GENERAL .................................................................................................................................................................................................................................25 1.1 Ribbonizing ..............................................................................................................................................................................................................................25 1.2 City Field Size ...........................................................................................................................................................................................................................27 1.3 Dated Notes Form - Add access right for emailing ...................................................................................................................................................................28 1.4 Client/Employee Schedule - Performance Improvements when closing form ..........................................................................................................................28 1.5 Allow Multi select when Deleting Tasks...................................................................................................................................................................................28 1.6 Performance Improvement .....................................................................................................................................................................................................28 1.7 Add/Del Access Rights - Extend field length to show long descriptions ...................................................................................................................................29 1.8 Add Filter for Diagnosis List on Client Intake Form ..................................................................................................................................................................29 1.9 CRM, Find Contact Form, Performance Improvements ............................................................................................................................................................29 1.10 Client Merge & Employee Merge .............................................................................................................................................................................................29 1.11 PASE – Addition of Grid capability ...........................................................................................................................................................................................32 1.12 PASE – Additional Workflow events ........................................................................................................................................................................................34 1.13 PASE – Addition of Category filter ...........................................................................................................................................................................................34 1.14 PASE – Addition of new Data Link question type .....................................................................................................................................................................34 1.15 PASE – Addition of new Image question ..................................................................................................................................................................................35 1.16 PASE - Image Question Added Fit to Width scaling ..................................................................................................................................................................37 1.17 PASE - Value Question Type –Accept zero as a valid value .......................................................................................................................................................37 1.18 PASE – Ability to copy questions in design mode .....................................................................................................................................................................37 1.19 PASE – Ability to copy an existing assessment .........................................................................................................................................................................38 1.20 PASE – Audit Log ......................................................................................................................................................................................................................38 1.21 Read Only Department Access .................................................................................................................................................................................................40 1.22 New Administrative Reference Number Access Rights ............................................................................................................................................................40 2 EMPLOYEES .............................................................................................................................................................................................................................42 2.1 User Interface- Update Employee Form ...................................................................................................................................................................................42 2.2 User Interface – Update Employee Availability Form ...............................................................................................................................................................44 3 CLIENTS ...................................................................................................................................................................................................................................45 3.1 User Interface- Update Client Form .........................................................................................................................................................................................45 3.2 Additional field – Consent to Share Data .................................................................................................................................................................................47 3.3 Additional field – Est................................................................................................................................................................................................................48 Procura 7- User Release Notes 7 of 155 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 3.20 3.21 4 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 6 6.1 6.2 6.3 6.4 7 Additional Field – Country of Birth ..........................................................................................................................................................................................49 User Interface Update - Client Order/Episode form .................................................................................................................................................................50 Additional Episode Folder - Dates ............................................................................................................................................................................................51 Episode Service Plan – Enable Conflict Checking ......................................................................................................................................................................54 Service Plan – Auto Service Plan ..............................................................................................................................................................................................54 Service Plan Configurations .....................................................................................................................................................................................................55 Auto Service Plan enhancements ............................................................................................................................................................................................57 Additional fields added to Client Informal Contact form .........................................................................................................................................................57 Additional Information – Ability to have Categories that are not Department specific ............................................................................................................59 Additional Information – set as Primary ..................................................................................................................................................................................59 PASE - User Interface Update - PASE Client Edit form ..............................................................................................................................................................59 Order - Spec. Rate - Reword error message .............................................................................................................................................................................60 Client Diagnosis Edit Form, Performance Improvements .........................................................................................................................................................60 Client Intake Form, Performance Improvements .....................................................................................................................................................................60 Archive Contacts(SHIN-41) .......................................................................................................................................................................................................60 Client Reference Number Management (BC-Spec47+49) .........................................................................................................................................................61 Client Intake – Birthdate defaulting to ‘today’ .........................................................................................................................................................................62 Dated Note – Add Cancel feature (SHIN-42) ............................................................................................................................................................................62 CLIENTS - USA ..........................................................................................................................................................................................................................64 SoC Date on OASIS updated to reflect a change in the SoC on Episode ....................................................................................................................................64 OASIS – Key commands have been applied .............................................................................................................................................................................64 485 - Add Physician Fax # to Verbal Order Printout Change Request .......................................................................................................................................64 OASIS - RFA Restriction Logic ...................................................................................................................................................................................................64 OASIS - New Validator .............................................................................................................................................................................................................66 OASIS - Validation does not work with Inactivation records ....................................................................................................................................................67 OASIS - Send NA when M0063 does not match accepted Values .............................................................................................................................................67 RFA04 - OASIS - M0090 Date field allows dates prior to 5 days with no warning .....................................................................................................................67 OASIS SOC - M0102 not giving validation error if left blank .....................................................................................................................................................68 CLIENTS - CANADA ...................................................................................................................................................................................................................69 CIS Inbox for CHRIS Offers and Referrals..................................................................................................................................................................................69 MDS-HC J2 ...............................................................................................................................................................................................................................69 MDS-HC Medication and Diagnosis Lookup (HISC-32) ..............................................................................................................................................................69 MDS-HC Diagnosis and Medication Changes (SHIN-38) ............................................................................................................................................................69 MDS-HC Increase/decrease number of Medication entries (SHIN-38) .....................................................................................................................................71 MDS-HC Allow for archiving contact, without changes to locked MDS ....................................................................................................................................72 MDS-HC Changes in Assessment Form (MDS-2010) .................................................................................................................................................................72 CLIENTS AUSTRALIA .................................................................................................................................................................................................................73 DVA PASE 2010 - NO63 – Not generating Specific Rate and not validating for staff visit ..........................................................................................................73 DVA - Break in Care logic PASE 6111 Claim Fee Termination ....................................................................................................................................................73 DVA Spiritus Cognitive questionChange Request .....................................................................................................................................................................73 Spiritus DVA Assessment Print Prompt Change Request (Defect 21424) ..................................................................................................................................73 SCHEDULING ............................................................................................................................................................................................................................74 Procura 7- User Release Notes 8 of 155 7.1 7.2 7.3 7.4 7.5 7.6 7.6.1 7.6.2 7.6.3 7.7 7.8 7.9 7.10 7.11 7.12 8 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 9 9.1 9.2 9.3 10 10.1 10.2 11 11.1 12 12.1 12.2 12.3 12.4 12.5 12.6 12.7 Best Route ...............................................................................................................................................................................................................................74 Match Engine...........................................................................................................................................................................................................................74 Offers/Callout ..........................................................................................................................................................................................................................75 User Interface Update - Planner form ......................................................................................................................................................................................79 Group Scheduling – New visit type “Non-Shift” .......................................................................................................................................................................80 Group Scheduling – Ability to add a Status to a Group ............................................................................................................................................................81 Group Scheduling: Schedulable Status Form ............................................................................................................................................................................81 Group Scheduling: Non Schedulable Status Form ...................................................................................................................................................................83 Group Scheduling: Waitlist Status Form ..................................................................................................................................................................................84 Scheduling Environment options - Number of Weeks Option ..................................................................................................................................................85 Durations not updating in Employee Day View when edited ...................................................................................................................................................85 Meals on Wheels - Client Status Change – Work Order SOW4909027161 ................................................................................................................................85 Meals on Wheels - Route Planner – Allow user to add visits to an empty route day ................................................................................................................85 Meals on Wheels - Route Schedule - Performance Improvement ............................................................................................................................................86 Meals on Wheels - Enable Order Service Plans for Meal Deliveries .........................................................................................................................................86 TIMEKEEPING ..........................................................................................................................................................................................................................87 Callme! - Cannot find a visit based on the Phone Number instead of the CVID ........................................................................................................................87 Callme! - Performance Improvements .....................................................................................................................................................................................87 Callme! - Duplicate CVID - Add client phone number to verify correct CVID ............................................................................................................................88 Callme! HL7 import - Callme processing include 0 duration visit (Change Request #21970) .....................................................................................................88 Callme! - Make Pay/Bill Duration enhancements (NW-19) ......................................................................................................................................................90 Callme! - Update the visit Stop Time based on the actual start time .......................................................................................................................................90 Callme! - Ignore Per Visit Records for Duration Exceptions ......................................................................................................................................................93 Callme! - Workflow Queries Performance Improvements .......................................................................................................................................................93 Callme! - Visit Verification – Is set to checked by default .........................................................................................................................................................93 BILLING ....................................................................................................................................................................................................................................94 Billing Rate Records – Ability to Update or Expire records .......................................................................................................................................................94 Batch Payments – Cosmetic issues...........................................................................................................................................................................................99 Data Model changes for payment processing history tracking ............................................................................................................................................... 100 BILLING - USA ........................................................................................................................................................................................................................ 100 UB04 Invoice - Does not report Meals on Wheels .................................................................................................................................................................. 100 Invoices - New Medicare regulation - Update logic condition code UB-04 ............................................................................................................................. 100 ADDITIONAL INTERFACES ...................................................................................................................................................................................................... 101 Additional Interfaces ............................................................................................................................................................................................................. 101 IMPORTS/EXPORTS ............................................................................................................................................................................................................... 103 ADP Payroll Export – Ability to create multiple files .............................................................................................................................................................. 103 Change to GP Payroll export Query ....................................................................................................................................................................................... 103 HL7 Outbound - Use activity change date if newer than visit ................................................................................................................................................. 103 HL7 Outbound - Suppress client phone number .................................................................................................................................................................... 103 HL7 Outbound - Enhancement to employee and visit trigger ref ........................................................................................................................................... 103 HL7 Outbound - Order comments NTE ................................................................................................................................................................................... 103 HL7 Outbound - Send Mobile Employee & Emp. Visits Only Switch ....................................................................................................................................... 103 Procura 7- User Release Notes 9 of 155 12.8 12.9 12.10 12.11 12.12 12.13 12.14 12.15 12.16 12.17 12.18 12.19 12.20 12.21 12.22 12.23 12.24 12.25 12.26 12.27 12.28 13 13.1 13.2 13.3 13.4 13.5 13.6 13.7 14 14.1 14.2 14.3 14.4 14.5 14.6 14.7 14.8 14.9 15 15.1 15.2 HL7 Outbound - Export screen status filter ............................................................................................................................................................................ 103 HL7 Outbound - Do not prompt for report ............................................................................................................................................................................. 103 HL7 Outbound - Attendance type ADT message with address ............................................................................................................................................... 103 HL7 Outbound - Employee Area STF-11.8 .............................................................................................................................................................................. 104 HL7 Outbound - Trusted partner drop-down select on export ............................................................................................................................................... 104 HL7 Outbound - Client supervisor requirement NTE .............................................................................................................................................................. 104 HL7 Outbound - Add employee ID to visit message ............................................................................................................................................................... 104 Removed the last comma in QHR Payroll Export Change Request ......................................................................................................................................... 104 HH-CAHPS Export .................................................................................................................................................................................................................. 104 SAP Payroll Export - Export files were missing hardcoded values .......................................................................................................................................... 104 QB AR Export - Removed Employee Name FARL .................................................................................................................................................................... 104 HL7 - Callme changes - VONCAN-50 ....................................................................................................................................................................................... 104 HL7 - Outbound VON Medshare changes ............................................................................................................................................................................... 104 HL7 import - Retain scheduled visit activities Change Request .............................................................................................................................................. 105 HL7 - Outbound changes for Medshare eMotion (BAYCORP-127) .......................................................................................................................................... 105 HL7 - VON SAP Payroll Export - Disallow specific attendance type ......................................................................................................................................... 105 HL7 import – Callme! processing include 0 duration visit ....................................................................................................................................................... 105 HL7 import - Completed visit detailed dated note ................................................................................................................................................................. 105 Hl7 import – Now allow mileage to be attached to cancelled visits ....................................................................................................................................... 105 HL7 Outbound CellTrak - Attendance Type Address............................................................................................................................................................... 105 HL7 PROHL7X.EXE - Client Status Transmission Change ......................................................................................................................................................... 105 IMPORTS/EXPORTS USA ........................................................................................................................................................................................................ 106 OASIS Export – Default Filename - Prompt or add seconds .................................................................................................................................................... 106 OASIS C Export - Clinician, Supervisor, Team in CMS_USE Change Request ........................................................................................................................... 106 OASIS - ANSI 270 - 99+ patients GS06 and SE02 - increment by 1 ........................................................................................................................................... 106 OASIS - ANSI 270 - Added validation for Rejection 'missing City/State/Zip' ........................................................................................................................... 106 OASIS - ANSI 837 - I- MSP Export is missing items in secondary claim .................................................................................................................................... 106 ANSI 270 - Code BHT06 only for Medicaid ............................................................................................................................................................................. 106 Billing - New Medicare regulation - Update logic condition code ........................................................................................................................................... 106 IMPORTS/EXPORTS CANADA ................................................................................................................................................................................................. 107 PMI Advanced Export - Performance improvements ............................................................................................................................................................. 107 HL7 - Manitoba Client Registry .............................................................................................................................................................................................. 107 HOBIC Export ......................................................................................................................................................................................................................... 107 HOBIC Export – Fixed a problem with the Ampersand character ........................................................................................................................................... 107 HOBIC EXPORT – We now include the Date Time stamp to the file name .............................................................................................................................. 107 HOBIC Export - Encounter ID.................................................................................................................................................................................................. 107 VON SAP AR Export – Now use | to separate elements in item textChange Request ............................................................................................................. 107 CMIPS II Billing Export - Padded SOC date with spaces Change Request ................................................................................................................................ 108 MoHS MRR Export - Question Type Change ........................................................................................................................................................................... 108 IMPORTS/EXPORTS AUSTRALIA ............................................................................................................................................................................................. 108 Compacks Export - NEW ........................................................................................................................................................................................................ 108 HACC Export - Add Information Validation no longer passes 9 values to MDS ....................................................................................................................... 109 Procura 7- User Release Notes 10 of 155 15.3 HACC Export - Background Coordination Time....................................................................................................................................................................... 109 15.4 HACC Export –Field Changes .................................................................................................................................................................................................. 110 15.5 CSTDA Export – Field Changes ............................................................................................................................................................................................... 110 15.6 HACC Export - Changes CMS R2-001 and BC-CR104+139 ........................................................................................................................................................ 110 15.7 DVA CNMDS Export - DVA_2010_AU Validation and export to Excel ..................................................................................................................................... 111 15.8 DVA XLS layout Change Request ............................................................................................................................................................................................ 111 15.9 DVA Export – ValidationChange Request ............................................................................................................................................................................... 111 15.10 CSTDA Use Current Address Change Request ........................................................................................................................................................................ 111 15.11 Palliative (NT51) - Do not validate No Staff Visits found in claim period ................................................................................................................................ 111 15.12 DVA - QC 154 Break in Care date logic Change Request ......................................................................................................................................................... 111 15.13 DVA - Discharge/Death not reported in correct period (6119) ............................................................................................................................................... 111 16 REPORTS ................................................................................................................................................................................................................................ 111 16.1 Billing Details Report - Performance Improvements .............................................................................................................................................................. 111 16.2 Client Listing Report - Performance Improvements ............................................................................................................................................................... 111 16.3 Client Dated Notes Report - Performance Improvements ...................................................................................................................................................... 112 16.4 Client Calendar Schedule - Ability to change format .............................................................................................................................................................. 112 16.5 Visit Counts By Funder And Billing Code - Performance Improvement .................................................................................................................................. 112 16.6 Employee Roster Report - Date Column Headers ................................................................................................................................................................... 112 16.7 Client Assessment Report Enhancement ............................................................................................................................................................................... 113 16.8 Capacity Manager - Call Me Hover Feature ............................................................................................................................................................................ 113 17 REPORTS - USA ...................................................................................................................................................................................................................... 114 17.1 California Reporting - Unduplicated Patient Listing and Count .............................................................................................................................................. 114 18 REPORTS - CANADA ............................................................................................................................................................................................................... 114 18.1 Report Writer - Transport Roster Report - Add visit dates ..................................................................................................................................................... 114 19 REPORTS - AUSTRALIA ........................................................................................................................................................................................................... 114 19.1 CRW - GST Payment Report v1 Paid Invoices ......................................................................................................................................................................... 114 19.2 CRW - Staff Productivity Report ............................................................................................................................................................................................. 114 19.3 Exclude DVA Claim Fee Visits from reports ............................................................................................................................................................................ 114 19.4 DVA ONI - Not printing core ONI in 6.2 .................................................................................................................................................................................. 114 DEFECT CORRECTIONS ........................................................................................................................................................................................................................... 115 20 DEFECT CORRECTIONS ........................................................................................................................................................................................................... 115 1 OASIS spell check corrected ................................................................................................................................................................................................... 115 2 OASIS and 485 – Medications not saving linkage to MEDDB or Custom Medications - BPL 6.2.1.5 ........................................................................................ 115 3 Archived service plans showing on the final 485 .................................................................................................................................................................... 115 4 CIS Inbox – Not finding matches based on bill codes ............................................................................................................................................................. 115 5 CIS inbox - Directions to Home field being overwritten ......................................................................................................................................................... 115 6 CIS Inbox - Permanent Address .............................................................................................................................................................................................. 115 7 CIS Inbox - Allows picking of archived funders ....................................................................................................................................................................... 115 8 MDS-HC Comment Changes grid does not expand with the size of the window .................................................................................................................... 115 9 Australia - NB01 not creating with Propase.bpl ..................................................................................................................................................................... 115 10 Employee Schedule report is double-spaced ......................................................................................................................................................................... 115 11 Callme! - HL7 EDCCALLS Unique ID in AUX_ID Field ............................................................................................................................................................... 115 Procura 7- User Release Notes 11 of 155 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 Billing - HCFA 1500 does not use 15 minute units properly .................................................................................................................................................... 116 Edmonton CCLD Summary Report - Sort is incorrect .............................................................................................................................................................. 116 Schedules Date Format and Employee Availability date format ............................................................................................................................................ 116 Billing Details Navigation Buttons Go Grey ............................................................................................................................................................................ 116 Visit that splits over end-of-billing-batch-date duplicates ..................................................................................................................................................... 116 Promaint.bpl 6.0.1.1 Caused Rate Grouper to be mandatory ................................................................................................................................................ 116 Clients Requiring Re-calculation ............................................................................................................................................................................................ 116 Billing Rates Module: Override Pay ....................................................................................................................................................................................... 116 Expenses add via Quick Vis Intake, Description not available ................................................................................................................................................ 117 Billing Batches - No validation when adding blank, new Billing Batch .................................................................................................................................... 117 PROWAM.EXE - Performance Improvement .......................................................................................................................................................................... 117 Visits matched outside variance not included........................................................................................................................................................................ 117 Callme! - Matching Problems with CVIDs 0000 ...................................................................................................................................................................... 117 CVID of 0000 Caused visits to not be matched ....................................................................................................................................................................... 117 ProHL7 looking to SysNextKeys row EDVisits ......................................................................................................................................................................... 117 Accept Schedules Brings Across Allowance Code ................................................................................................................................................................... 117 Detail Printing Format from Web Portal ................................................................................................................................................................................ 118 Conflict Checking & Verified Visits Change Request ............................................................................................................................................................... 118 Batch Processing Report: Dept Filter ..................................................................................................................................................................................... 118 Callme! - Duplicate alerts after visit change ........................................................................................................................................................................... 118 Callme! Allowances - Using Accept Actual button does not generate mileage ....................................................................................................................... 118 Callme! - Only Timeless visits accept duration as actual. ....................................................................................................................................................... 118 Callme! WAM Task - Link Comments to Call (BAYCORP-115) ................................................................................................................................................. 118 Callme! - Employee Maintenance Not Refreshing .................................................................................................................................................................. 118 Callme! Employee Maintenance: OK not transmitting change ............................................................................................................................................... 118 Automatic update will uncheck the Employee ....................................................................................................................................................................... 119 Complete Task - Modular window ......................................................................................................................................................................................... 119 Web Portal - Users can no longer be prevented from selecting dates. ................................................................................................................................... 119 HL7–only_transmit_current_ status ...................................................................................................................................................................................... 119 NW-21 Not calculating correctly ............................................................................................................................................................................................ 119 Visit Activity Script Request (SEHC/CellTrak) ......................................................................................................................................................................... 119 Client Audit Log - Department status change - hide the date 12/30/1899 ............................................................................................................................. 119 Client Audit Log - order stop date is incorrect when order status changes............................................................................................................................. 119 Order Service Plan - changes ................................................................................................................................................................................................. 120 Service Plan Conflict Errors .................................................................................................................................................................................................... 120 Duplicate Dated Notes generated when editing Order/Episode Start Date & Automatic Dated Notes on Status .................................................................. 120 Dated Note - spell check not working .................................................................................................................................................................................... 120 Care Connection, Display Filter Options................................................................................................................................................................................. 120 Client Intake: Can assign contact without contact type ......................................................................................................................................................... 120 Find Directions - MapQuest bugs out on country code CANADA............................................................................................................................................ 121 Visit History Archived Default ................................................................................................................................................................................................ 121 Find Directions Links - Client Information | Address .............................................................................................................................................................. 121 Procura 7- User Release Notes 12 of 155 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 Error typing full date in to order form ................................................................................................................................................................................... 121 Windows 2008 - 64bit - adding order ..................................................................................................................................................................................... 121 Mobile phone number does not print in client profile report ................................................................................................................................................ 121 Incorrect syntax near 'F' - client intake .................................................................................................................................................................................. 121 Episode Recertify button - allowing duplicate episode dates - same payer source ................................................................................................................ 121 Episode service plan - duration exceeding episode end date ................................................................................................................................................. 122 Client Intake - click OK after select dept causes freezing........................................................................................................................................................ 122 Diagnosis Lookup causing database error on client intake ..................................................................................................................................................... 122 Physician/pharmacy cannot be removed ............................................................................................................................................................................... 122 CRM from Customer form ..................................................................................................................................................................................................... 122 CRM - Error received when viewing Organization contact ..................................................................................................................................................... 122 CRM - Filter for Tasks not working ......................................................................................................................................................................................... 123 Operational Dashboard - SQL Error on import ....................................................................................................................................................................... 123 Dashboard Hour Display ........................................................................................................................................................................................................ 123 Employee - Application folder Theme Issue ........................................................................................................................................................................... 123 GP Export - System Reference for OT calc includes all records ............................................................................................................................................... 123 Cannot terminate employee without planner ....................................................................................................................................................................... 123 After employee intake - Birth Month/Day fields are not populated ...................................................................................................................................... 123 ADP Payroll Export Interface ................................................................................................................................................................................................. 123 When using export in 6.2 - generates Access violation .......................................................................................................................................................... 123 Export does not detect first DVA claim .................................................................................................................................................................................. 123 DVA Export Requirement 5.5 Item codes report staff service ................................................................................................................................................ 123 DVA Export Short Admissions – Reporting Wrong Admission Date ........................................................................................................................................ 124 DVA Export-Item codes paired with specific claim validation ................................................................................................................................................ 124 Requirement /CR 168 Palliative Logic .................................................................................................................................................................................... 124 DVA Bereavement Visits Error Logic (No Staff Service) .......................................................................................................................................................... 124 DVA Palliative visit Date Claim From Issue............................................................................................................................................................................. 124 DVA Break in Care logic issue (Proaus6.1.1.8) ........................................................................................................................................................................ 125 DVA--Requirement 9.4.2 Error No DVA CN Found.................................................................................................................................................................. 125 DVA-Bereavement claim validates next 28 period for staff resource ..................................................................................................................................... 125 HACC 2.0 SLK Logic Error ........................................................................................................................................................................................................ 125 VON SAP Payroll - Attendance type name, pay description, not being exported ................................................................................................................... 125 VON SAP Payroll - Export path is not saved ........................................................................................................................................................................... 126 VON SAP AR Export - Remove Client ID from report Change request ..................................................................................................................................... 126 Rejections on CAHPS manual upload for SHP......................................................................................................................................................................... 126 HH-CAHPS - SHP Export Format Corrections .......................................................................................................................................................................... 126 HH-CAHPS - Export Filename Misspelled ............................................................................................................................................................................... 126 CAHPS export file name ......................................................................................................................................................................................................... 126 HH-CAHPS Export - Label missing & OCS file naming CCN duplication ................................................................................................................................... 126 RFA 3 and 5 not including 0023 line for first visit on RAP & ANSI 837 - exporting 3 LX 0023 lines .......................................................................................... 127 HL7 Outbound - Client activities being sent with Visits .......................................................................................................................................................... 127 HL7 Outbound - Wrong trusted partner options used for client care plan file ....................................................................................................................... 127 Procura 7- User Release Notes 13 of 155 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 HL7 Outbound - only transmit current status is still sending old statuses .............................................................................................................................. 127 GP Pay Export - not calculating OT correctly .......................................................................................................................................................................... 127 SEHC ADP - Attendance Types ............................................................................................................................................................................................... 127 SEHC ADP Payroll Export - Record Counter ............................................................................................................................................................................ 127 Avanti Payroll Export - export Pay Code Reference Value incorrect ....................................................................................................................................... 127 ACCPAC Payroll: Department Selection Grid .......................................................................................................................................................................... 127 ANSI270 99+ patients ST & SE increment update see 21243 .................................................................................................................................................. 127 Rapid Pay export I/O error .................................................................................................................................................................................................... 127 CSTDA NMDS Export - negative values for blank answers...................................................................................................................................................... 128 HL7 - outbound - client directions appearing in ORM message .............................................................................................................................................. 128 HL7 Care Plan Message sent with incorrect comments .......................................................................................................................................................... 128 HL7 transmitting archived task details ................................................................................................................................................................................... 128 CMIPS II export - change format of 2 hours fields .................................................................................................................................................................. 128 HOBIC - PID-4 missing some data ........................................................................................................................................................................................... 128 HOBIC - OBX-11 segment missing S ........................................................................................................................................................................................ 128 HOBIC - Only the primary informal contact should be printed ............................................................................................................................................... 128 HOBIC - PID-15 missing value when primary language not selected. ..................................................................................................................................... 128 Running ANSI 837 Export produces error ............................................................................................................................................................................... 129 Status Processing - Generating Log File to Procura Temp Folder ............................................................................................................................................ 129 Dated Notes - Body text not sent when using Plain Text ....................................................................................................................................................... 129 Check for updates not placing release notes in proper folder ................................................................................................................................................ 129 Spelling error - User environment options ............................................................................................................................................................................. 129 SP9 error with dated note creation on status change ............................................................................................................................................................ 129 Spelling mistake on CIS referral ............................................................................................................................................................................................. 129 Prompt user message not displaying correctly ...................................................................................................................................................................... 129 General - clipping in department reference numbers ............................................................................................................................................................ 129 HL7 - Error checking on import .............................................................................................................................................................................................. 129 HL7 Passive Mode: PID-33 not being populated .................................................................................................................................................................... 129 HL7 Passive Mode - PID-7 should not include time ................................................................................................................................................................ 130 HL7 - Line Breaks parsed from Hazard Comments .................................................................................................................................................................. 130 HL7 - Care Plan Activities - visit care plan activities can be out of order................................................................................................................................. 130 HL7 - /ALLOW_MULTI_CLTDEPT for Attendance Types .......................................................................................................................................................... 130 HL7 Inbound - Restrict unscheduled attendance types (SEHC-64) .......................................................................................................................................... 130 HL7 Inbound - only one dated note created per day .............................................................................................................................................................. 130 HL7 Outbound - attendance type ADT message PID-2, PID-3 ................................................................................................................................................. 130 HL7 - Employee Transmit Button transmits Attendance Types .............................................................................................................................................. 130 HL7 - Client or Employee Transmit buttons use session instead of DB time ........................................................................................................................... 130 HL7 - outbound. /allow_only_att_types location output is incorrect ..................................................................................................................................... 131 Cannot select existing order to update .................................................................................................................................................................................. 131 HL7 - Unscheduled Attendance type visits created when they should not be. ....................................................................................................................... 131 HL7 - Passive Mode - PID Identifier Other is not being parsed. .............................................................................................................................................. 131 HL7 - Passive Mode - if address options are not used don't print them. ................................................................................................................................ 131 Procura 7- User Release Notes 14 of 155 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 HL7 - Passive Mode - cannot transmit without Allow_client_validation ................................................................................................................................ 131 HL7 - Passive Mode - The merge message does not need a 1 ................................................................................................................................................. 131 HL7 Passive mode - AO1 seen when AO8 is expected. ........................................................................................................................................................... 132 F1 creates an error................................................................................................................................................................................................................. 132 Department start date not populated by CIS Inbox ............................................................................................................................................................... 132 Procura invoice and ANSI Overwriting in invoice run ............................................................................................................................................................. 132 Combo Invoice - Spelling Mistake .......................................................................................................................................................................................... 132 Delphi 2009 - SetTabPrintTab - Invoices................................................................................................................................................................................. 132 Invoice Summary Report ....................................................................................................................................................................................................... 132 HCFA 1500 Red Preprinted Form -Setup Not Working ........................................................................................................................................................... 132 Clients without Departments Utility ...................................................................................................................................................................................... 132 Database error when trying to delete default department .................................................................................................................................................... 132 Departments: New Department & Department Taxes ........................................................................................................................................................... 133 CR - CallMe: Attendance Types .............................................................................................................................................................................................. 133 Additional Information Module - Subcategories Label Name - Add blank .............................................................................................................................. 133 Delete Employee utility not bringing back expected results .................................................................................................................................................. 133 MDS - Section G1 - Re-implement Contact Lookup ................................................................................................................................................................ 133 Help option in MDS-HC points to wrong folder & Double-click question title returns error ................................................................................................... 133 Med DB - Sort Results Alphabetically ..................................................................................................................................................................................... 133 MOW Add/Del Meal Package in Client Delivery Schedule ..................................................................................................................................................... 133 MOW Stat Holiday conflict checking not working properly .................................................................................................................................................... 133 MOW Meal Labels Report not printing correctly ................................................................................................................................................................... 133 OASIS - Show M0140-M0150 as needed ................................................................................................................................................................................ 134 OASIS - M1016-NA set on RFA09 ........................................................................................................................................................................................... 134 OASIS C Question M2100 in .rep file ...................................................................................................................................................................................... 134 OASIS - episode end date is not saved properly ..................................................................................................................................................................... 134 OASIS - View and copy previous answer brings invalid answers fwd ..................................................................................................................................... 134 OASIS-M1730 print blank form missing PHQ2 scale RFA 1 and 3 ........................................................................................................................................... 134 RFA 9 M1500 - 'Go to Question' does not work ..................................................................................................................................................................... 134 Dependent questions printing to 485 when not answered. ................................................................................................................................................... 134 Custom question "hooks" not functioning - RFA03 / 04 ......................................................................................................................................................... 134 RFA 4, Recertification date rules are incorrect ....................................................................................................................................................................... 135 OASIS Validation Error - Diagnosis code not valid - Showing wrong question ........................................................................................................................ 135 RFA 6 and 9 cannot enter correct M0906 date ....................................................................................................................................................................... 135 M0175 showing active on RFA 4 and 5 v62 ............................................................................................................................................................................ 135 OASIS being sent with incorrect HIPPS code .......................................................................................................................................................................... 135 OASIS Validation - Error on M0104 ........................................................................................................................................................................................ 135 OASIS M2110 answer 1 does not print................................................................................................................................................................................... 135 OASIS M1016 and M1020 Tabbing out of order ..................................................................................................................................................................... 136 OASIS Gen Quest: not printing question body to blank form ................................................................................................................................................. 136 Validation error - M1620 'go to error' - 'M1620 not found'.................................................................................................................................................... 136 HIPPS/HHRG codes remove from OASIS when moved to other episode ................................................................................................................................ 136 Procura 7- User Release Notes 15 of 155 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 Add OASIS RFA 6, 7, 8 or 9 - bringing in diagnosis - Errors ...................................................................................................................................................... 136 Validation error - M0102 'go to error' - 'M0102 not found'.................................................................................................................................................... 136 OASIS Rept. not printing questions after 18A ........................................................................................................................................................................ 136 OASIS C - M2100 section D if answer is 5 - does not save....................................................................................................................................................... 136 OASIS +7 Fatal file - Invalid Record Length ............................................................................................................................................................................. 136 OASIS M0102 date removing when saved NA then checked .................................................................................................................................................. 136 OASIS-submitted HIPPs cannot have blank HIPPS version ..................................................................................................................................................... 137 OASIS - display issue when opening sent OASIS ..................................................................................................................................................................... 137 OASIS Report: Query Error ..................................................................................................................................................................................................... 137 OASIS Report - Some Sections do not print custom questions ............................................................................................................................................... 137 DSS format of HH-CAHPS contain invalid columns ................................................................................................................................................................. 137 OCS CAHPS export is formatted incorrectly ........................................................................................................................................................................... 137 OASIS access & Clinical Day View........................................................................................................................................................................................... 137 Medications are not being linked with the database ............................................................................................................................................................. 137 Second OASIS export file overwriting initial one .................................................................................................................................................................... 137 Help, About - DLL version numbers not shown ...................................................................................................................................................................... 137 Inserted Objects not saving in dated notes ............................................................................................................................................................................ 137 Coloring for Capacity Manager 0 value .................................................................................................................................................................................. 138 Capacity Manager - Calls Received slowness / incorrect ........................................................................................................................................................ 138 HL7 Inbound - mileage rounding change ................................................................................................................................................................................ 138 6.1 image showing on 6.2 Help .............................................................................................................................................................................................. 138 CRM print out with dated note .............................................................................................................................................................................................. 138 Schedule address field directions popup not working properly ............................................................................................................................................. 138 CRW - Legacy Invoice GST amount incorrect .......................................................................................................................................................................... 138 Create multiple visits: Pay Service not transferred to visits ................................................................................................................................................... 138 Image Compare - duplicate image records are being selected ............................................................................................................................................... 138 PASE Export/Import - Images saved in 6.1 are corrupted in 6.2 ............................................................................................................................................. 138 PASE-Radio Buttons combined with text field writes values .................................................................................................................................................. 139 V6200 PASE Radio button with text, text does not save ........................................................................................................................................................ 139 DVA EXPORT Variation w/Discharge does not stop visit & DVA Variation Defect Discharge .................................................................................................. 139 Defect/CR 22272 Break In care logic (Hosp/Holiday/Rehab) .................................................................................................................................................. 139 NA01 (assessment) creates 2 regular visits ............................................................................................................................................................................ 139 DVA-Break in Care ................................................................................................................................................................................................................. 139 DVA-Calculate Item Number & Generate Claim Fee Visits ..................................................................................................................................................... 139 PASE: Date Question -............................................................................................................................................................................................................ 139 ONI - Dependencies not populating when edited .................................................................................................................................................................. 139 PASE - lookup type answers do not clear from form .............................................................................................................................................................. 139 PASE - Client Supervisor Requirement form missing .............................................................................................................................................................. 140 ONI-CIARR Report - typo in Question 11.1 ............................................................................................................................................................................. 140 PASE-on edit, no prompt to discard changes (using x) ........................................................................................................................................................... 140 Client Assessment Report - Print version unlike screen version of assessment ...................................................................................................................... 140 Visit notes not synching to server. ......................................................................................................................................................................................... 140 Procura 7- User Release Notes 16 of 155 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 ONI Printed Form................................................................................................................................................................................................................... 140 Blue Care Printed From - Facility Name not required ............................................................................................................................................................. 140 Carer Availability Prints as 4 on ONI ...................................................................................................................................................................................... 140 Master Pay Records attached to Employee File ..................................................................................................................................................................... 140 OASIS Final Claim - Est. PPS - adds PPS amounts of multiple OASIS ....................................................................................................................................... 141 Client Aged -Not detailing actual transactions as in pay proc ................................................................................................................................................ 141 Planner Report Header Does not sort by Planner .................................................................................................................................................................. 141 Visits created on laptop synch back as "invisible visits" ......................................................................................................................................................... 141 POC Console not processing check-ins automatically............................................................................................................................................................. 141 POC installer - SQL Express 205 SP3 on XP Pro SP2 = Blue screen of Death! ........................................................................................................................... 141 POC Installer - Database not attached in 6200 ....................................................................................................................................................................... 141 POC Installer – SQL Express 2005 sp2 install fails when msxml6 sp2 is installed .................................................................................................................... 141 Staff Productivity Report CRW/ Total issues .......................................................................................................................................................................... 141 California Reporting – Counts are off ..................................................................................................................................................................................... 142 California Reporting - Count of unduplicated clients and visits .............................................................................................................................................. 142 CRW: Staff Productivity Detail Report - Admin Time percentage incorrect. ........................................................................................................................... 142 Billable Services CRW/Ver. 3 BC-CR140 Date of death logic backwards ................................................................................................................................. 142 FNIH Invoice - Saving to RTF .................................................................................................................................................................................................. 142 JBC HACC Tax Invoice CRW - Taxes are not displayed in report .............................................................................................................................................. 142 Tax Invoice for EACH Version 9 .............................................................................................................................................................................................. 142 JBC-04- GST Summary Report Invoice #1314 hardcoded to report interface .......................................................................................................................... 142 Compliance CRW report - Clients with correct postal codes still displayed. ........................................................................................................................... 142 HACC Tax Invoice CRW - Fees column contains rounding errors ............................................................................................................................................ 142 CRW-Co-payment report crashes when TC value other than "1" ........................................................................................................................................... 142 CRW: Callme! Exceptions by Client - calls within variance showing No Call ........................................................................................................................... 143 OASIS Report Not Printing Image Questions Correctly ........................................................................................................................................................... 143 Expense & Mileage Report Error ............................................................................................................................................................................................ 143 Client Service Summary Report Visit Total Options ............................................................................................................................................................... 143 Revenue Analysis report columns overlap ............................................................................................................................................................................. 143 TK Detail Summary report not adding columns correctly ....................................................................................................................................................... 143 Funder coordinators from expired orders printing ................................................................................................................................................................ 143 Employee Schedule Report .................................................................................................................................................................................................... 143 MDS-HC Profile Report .......................................................................................................................................................................................................... 143 Labour Rule Exception Report not always displaying category .............................................................................................................................................. 143 CRW: Staff Productivity Detail Report - Case Conference type............................................................................................................................................... 144 CMS Cost Report - Not printing NRS totals ............................................................................................................................................................................ 144 CMS Cost Report - Miss-type for Home Health Aide .............................................................................................................................................................. 144 CMS Cost Report - Not printing Patient counts for service disciplines Title XVIII.................................................................................................................... 144 CMS Cost Report - Not printing counts for Other Part I Statistical Data ................................................................................................................................. 144 Status Drop-Down List not populated for report ................................................................................................................................................................... 144 TK Detail by Employee: Department Name Wrapping ........................................................................................................................................................... 144 Reports: Report of Service ..................................................................................................................................................................................................... 144 Procura 7- User Release Notes 17 of 155 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 Employee Roster Report: Attend Types & Employee without Visits ...................................................................................................................................... 144 Employee Roster-Field Masking & Justification Issues ........................................................................................................................................................... 144 Employee Roster Report: Summary Actual Supply Issue & Employee Not Avail showing Supply Total .................................................................................. 144 Employee Roster Report using default availability. ............................................................................................................................................................... 145 Employee Roster Report - Hanging and Index out of bounds errors ...................................................................................................................................... 145 Employee Roster Report Defect ............................................................................................................................................................................................. 145 Availability, Booked Visits, & Actual Supply & Print Max per Day Capacity/Supply Calc Error ............................................................................................... 145 Employee Roster Report - Print Employee Category .............................................................................................................................................................. 145 Client Service Summary -discipline order not printing same as chosen .................................................................................................................................. 145 Defect Revenue Analysis Report ............................................................................................................................................................................................ 145 Physicians Order Rep: effective date not filtering properly ................................................................................................................................................... 145 Employee Calendar Schedule Report rows and columns out ................................................................................................................................................. 145 Timekeeping detail by employee report template ................................................................................................................................................................. 145 Employee Calendar Schedule Report producing black line ..................................................................................................................................................... 146 Access Violation in RTL120.bpl .............................................................................................................................................................................................. 146 PPS Report - 'Print Episode Type' not printing any data ......................................................................................................................................................... 146 Employee Schedule report is double spaced .......................................................................................................................................................................... 146 Contact Profile Report - printing ............................................................................................................................................................................................ 146 Labor Rules Exception report ................................................................................................................................................................................................. 146 Client Service Summary Report - column headings overlap ................................................................................................................................................... 146 Client Mailing Labels - Access Violation rtl140.bpl ................................................................................................................................................................. 146 MDS-HC - CAPS section - right click help error ....................................................................................................................................................................... 146 User defined settings cause DB error ..................................................................................................................................................................................... 146 Remove broken button from MDS-HC form ........................................................................................................................................................................... 146 OASIS Report PASE Dependency ............................................................................................................................................................................................ 146 Access Right - Attendance Types... ........................................................................................................................................................................................ 147 HST not displaying on invoice ................................................................................................................................................................................................ 147 Error Posting Message HPG Service: Incoming document not XML ........................................................................................................................................ 147 Archived MDS-HC assessments can still be added in MDS tab ............................................................................................................................................... 147 TK - Define Periods Date change ............................................................................................................................................................................................ 147 'Copy Invoice To' prints arbitrary visit start/stop times on invoice copy ................................................................................................................................ 147 Workflow: Error when deleting tasks .................................................................................................................................................................................... 147 HL7: Attendance Types transmitted with blank CVID ............................................................................................................................................................ 147 User dept access prevents message matching but still display............................................................................................................................................... 147 CIS Inbox not matching department/funder w multiple partners .......................................................................................................................................... 148 CIS Inbox - Allow fields to be double-clicked on - to open a display window ......................................................................................................................... 148 CIS Inbox - Print capabilities .................................................................................................................................................................................................. 148 Employee Schedule Report – Address Field overwriting ........................................................................................................................................................ 148 Callme! Comparison screen creates error Invalid Tag Allowance Claims ................................................................................................................................ 148 Employee Schedule Report - Client Name / Phone Number................................................................................................................................................... 148 CRW - Client Consistency Report - Missing attendance types ............................................................................................................................................... 148 CRW - Client Consistency rpt - Rebooked employee counts incorrect .................................................................................................................................... 148 Procura 7- User Release Notes 18 of 155 306 CRW - Client Consistency rpt - SQL Error found...................................................................................................................................................................... 148 307 CR - PASE Supervisor Requirements include archived in list................................................................................................................................................... 148 308 Client Profile report ............................................................................................................................................................................................................... 149 309 CMS 1500 1000 Claims Rejected Box 24E Diagnosis Pointer .................................................................................................................................................. 149 310 V7 - (New) Billing Details Report Template not holding Funder ............................................................................................................................................. 149 311 V7 - Released Code for QB Invoice incorrect value in one field .............................................................................................................................................. 149 312 Calculation in QB export enhancement not rounding ............................................................................................................................................................ 149 313 Medication Monographs ....................................................................................................................................................................................................... 149 314 HL7 outbound - clients listed in error log for employees........................................................................................................................................................ 149 315 V7 - Scheduling Group Confirmation Popup ........................................................................................................................................................................... 149 316 V7 - HCFA 1500 - Cell 30 not being used ................................................................................................................................................................................. 149 317 V7 - Status change in workflow module................................................................................................................................................................................. 149 318 V7 - Employee Merge Utility - Error on Merge ....................................................................................................................................................................... 150 319 V7 - Employee Schedule Grid: Show Labor Rule Totals .......................................................................................................................................................... 150 320 V7 - Linked PASE document will not upload unless reference is set ....................................................................................................................................... 150 321 V7 - NW-21 - Custom Mileage Rules - Change to Cancelled Visits .......................................................................................................................................... 150 322 V7 - General - change local filtering date format logic ........................................................................................................................................................... 150 323 Access Violation rtl120.bpl error when Closing TK Periods .................................................................................................................................................... 150 324 V7 -Visit History Generation System Log Entry shows 0 records created ............................................................................................................................... 150 325 HL7 Client export - should explicitly exclude attendance types ............................................................................................................................................. 150 326 HL7 - Attendance Type Message Construction incorrect (6.0) ................................................................................................................................................ 150 327 V7 - Wildcard reporting allow free-form typing in area field.................................................................................................................................................. 151 328 Upload License Data - Invalid Pointer Operation ................................................................................................................................................................... 151 329 Dated Notes – being saved/sent to recipient if deleted ......................................................................................................................................................... 151 Clients | Select | Dated Notes folder ..................................................................................................................................................................................................... 151 If the user entered a recipient into the To: field in a Dated Note, and then removed that recipient and clicked Save/Send, the note was emailed to that recipient, even though it had been removed. This problem has been fixed. Dated Notes that do not contain a recipient name will ever only be saved..................... 151 330 Availability/Employee Roster Report - Midnight Start ........................................................................................................................................................... 151 331 V7 - Task Event Client status activation not working ............................................................................................................................................................. 151 332 V7 - Schedule Generation - File & System Log ........................................................................................................................................................................ 152 333 V7 - Weekly Planning Rpt converting repeating durations incorrect ...................................................................................................................................... 152 334 V7 - Celltrak - HL7 - Inbound - Unscheduled client visit .......................................................................................................................................................... 152 335 V7 - URN number on Client Co Payment Report only displays 9 digit ..................................................................................................................................... 152 336 Defect/CR: HH-CAHPS Min CMS Export CSV .......................................................................................................................................................................... 152 337 V7 - Client Service Summary Report - Wrong Table Queried .................................................................................................................................................. 152 338 BC SPEC 50 Waitlist Status not option for Scheduling Group ................................................................................................................................................. 152 339 SEHC-ADP Payroll Export ....................................................................................................................................................................................................... 152 340 Medication Profile Report columns overwriting .................................................................................................................................................................... 153 341 Client Ref no Stat Rep points to wrong table ......................................................................................................................................................................... 153 342 HL7 - Duplicate visit / travel time entries ............................................................................................................................................................................... 153 343 V7 - Client schedule: employee search filter inaccuracies ...................................................................................................................................................... 153 344 V7 - 'Copy Invoice To' prints arbitrary visit start/stop times on invoice copy ......................................................................................................................... 153 Procura 7- User Release Notes 19 of 155 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 V7 - Refresh issues in payment processing Filters and visits .................................................................................................................................................. 153 V7 - Batch payments - edit reversal from unposted batch - error .......................................................................................................................................... 153 V7 - Premium Pay Utility - Rounding error with start/stop time? .......................................................................................................................................... 153 V7 - status generation is stopping the schedule records from generating forward ................................................................................................................ 153 V7 - Callme - visits showing zero's in mileage column ............................................................................................................................................................ 153 V7 - Close TK Period - Check for unverified visits ................................................................................................................................................................... 154 V7 - TK - Previous period visits showing in current ................................................................................................................................................................ 154 Client Care Connection spelling error in filter options ........................................................................................................................................................... 154 ONI--Prox.bpl 6.1.1.8--Equipment comments exceed deselect .............................................................................................................................................. 154 Work Order JBC-20 incorrectly totaling hours ........................................................................................................................................................................ 154 Reports: Collection Letter Report/Client Aged ....................................................................................................................................................................... 154 HL7 - Transmission - Performance Improvements ................................................................................................................................................................. 154 Availability/Employee Roster Report - Midnight Start ........................................................................................................................................................... 154 QB AR Export - FARLs from wrong funder being applied ........................................................................................................................................................ 155 Client Aged Report - Templates and Specific Transactions ..................................................................................................................................................... 155 V7 - Show Labor Rules in Scheduling - Colors disappear ........................................................................................................................................................ 155 OASIS Calculate PPS on the fly Access Rights ......................................................................................................................................................................... 155 Duplicate CVID - Same Employee Same Day possible ............................................................................................................................................................ 155 155 Procura 7- User Release Notes 20 of 155 Upgrading to Procura 7 1.2 Pre-Upgrade Procedures System Administrator Pre-Upgrade Tasks This document outlines the procedures that should be followed by the System Administrator performing an internal or self upgrade. It will cover the installation of Procura V7, as well as the instructions on upgrading your database. The following outlines the tasks that should be completed in preparation for the upgrade: 1. Access the Discussion Forum: a) Go to this link: www.goprocura.com. b) Click the Discussion Forums link and login. If you have not registered on the Forum, please follow the instructions on the screen to register. You will need to know your Procura Tracker User Login name to register. 2. Download the following items: These will be located on the Discussion forum http://24.68.237.6:235/viewtopic.php?t=549 a) Procura 7 Upgrade Webinar b) ProcuraInstaller_DatabaseUpgrade_7.exe or database upgrade script (optional) c) ProcuraInstaller_Basic_7.exe d) ProcuraInstaller_POC_7.exe e) Upgrading the Procura Database Guide f) Installing and Upgrading Procura g) Installing and Upgrading Procura for POC h) Procura 7 Release Notes 3. View/Attend Upgrade Webinar: The Webinar will be conducted by a Procura Release Management team member. It is highly recommended that you attend prior to upgrading. 4. Review Documentation: Prior to upgrading, we recommend that your System Administrator: a) Arrange for IT/IS Contacts and other Contacts to attend the Webinar. b) Print and reviewUpgrade and Installations Guides. c) Print and review Release Notes. 5. Plan for the upgrade: Typically, an upgrade will take approximately 1 - 2 hours. So, please prepare your staff for the down time. If the down time is too long, try using a backup as a lookup-only access. See appendix A “Creating a lookup version”. 6. Perform a backup: The database upgrade will perform a backup for you. Your IT personnel should confirm that there is enough disk space to completely backup the database. The Upgrader will backup the data to your MS SQL Server’s default backup path. If the upgrade fails or a Procura 7- User Release Notes 21 of 155 database problem is detected, the Database Upgrader will perform the restore as well. 7. Ensure that the PC that will be used to upgrade the database has the appropriate database management tools and email capabilities, as well as access to the files required for the upgrade. 1.3 Business Preparation Procura 7 has innovations that will help you to improve your operations, streamline processes, and provide additional supports to your end-users, direct service staff, clients, and other stakeholders. In order to take the best advantage of the solutions that we offer, we suggest that your business leaders plan your upgrade by: 1. Review Procura’s Release Notes and highlight the items that you wish to implement. You may wish to request that your System Administrator upgrade a Training/Test database so that you can review these new features and capabilities, determine how they will fit within your business, improve process, and decide upon an end-user training programme that will ensure that you take best advantage of the new innovations. 2. Obtain professional assistance: Procura offers Application Consulting services to help you with the planning and training of the v.7 solutions. If you are interested in engaging Procura to help you with the business-level preparations for the upgrade, please contact your Account Manager. 1.4 Performing the Upgrade You can perform these steps to upgrade your Test/Training database, and also for upgrading your Live/Production database. We recommend that a training or test environment be upgraded prior to upgrading your production environment. This process will take approximately 1 to 2 hours to complete: 1. We ask that you notify the Procura Support team by e-mail and let them know of the date/time that you plan to upgrade your live database. 2. If you are upgrading a test/training database, when you run the installer please remember to direct the install to a separate folder than the default c:\Program Files\Develus\Procura. This will ensure that you don’t overwrite your production installation (Procura takes a backup of the files, however it will save time to point to a path such as c:\Program Files\Develus\Procura\7). 3. Ensure that all synchronization users have synchronized and checked in their information to the server database. 4. Ensure that no users are logged in to Procura. 5. Uninstall your Procura 6.x from Add\Remove Programs (Control Panel). 6. If you are using the PoC, you also need to uninstall SQL Express (same as above). 7. Run the Procura 7 Database Upgrade utility ProcuraInstaller_DatabaseUpgrade_7.exe. See the document Upgrading the Procura Database for instructions on running this utility. By default, the Procura 7 Upgrade utility will create a backup of your Procura database. If any errors occur during the database upgrade process, the Procura 7 Upgrade utility will also restore your database using the backup it took. NOTE: If the option to create a backup is NOT selected, it is highly recommended that you cancel the database upgrade utility and manually create a backup of your database before restarting the database upgrade process. If an error occurs, contact the Procura Help Procura 7- User Release Notes 22 of 155 Desk at 1-877-776-2872 ext 1 or email Support@goprocura.com. 1.5 Performing the Installation 1. Run the Procura 7 installer ProcuraInstaller_Basic_7.exe on each workstation that has the Procura client installed. For more information on using the Procura 7 installer, see the document Installing and Upgrading Procura for step-by-step instructions. You must run Procura v.7 installer on all client workstations or application servers that require an upgrade. You must complete this step for at least one workstation in order to proceed with the upgrade procedure. For installation instructions for Procura on POC Devices, refer to Installing and Upgrading Procura for POC. 1.6 Post-Upgrade Tasks The following outlines the tasks and checks after the upgrade has been performed: 1. After completing the upgrade, email the license data to Procura. 2. Update your CRW Data Dictionary files: a. Download the files from the Discussion Forum: Upgrade Files | Service Packs and Library Updates | Procura v.7 Upgrade Files. (Right-click on v.7_CRW_Data_Dictionary.zip, select Save As, and save to a local drive). b. Unzip the files. c. Load Procura using a User Name that has System Administrator privileges. d. Select Maintenance | Administration | Load Data Dictionary. e. Click Load Data Dictionary Tables. Browse for and select the file: 1-RPTTABLE.PDD. f. Click Load Data Dictionary Fields. Browse for and select the file: 2-RPTFIELD.PDD. g. Click Load Data Dictionary Joins. Browse for and select the file: 3-RPTJOINS.PDD. 3. Log in to Procura using a User Name that has System Administrator privileges. 4. Go to Maintenance | Utilities | Check Database Structure to check the database structure. There should be no missing Metadata in the left-hand column. Additional Metadata can exist if you are using any kind of Procura customization, (e.g., dashboards) within normal operating parameters. However, if there is missing Metadata, contact the Procura Help Desk immediately. 5. When logged in to Procura as the System Administrator, go to Maintenance | Administration | Update Procura Tables. You will be prompted to continue. When the update is completed click OK. 6. Once the update of Procura tables is complete, update the System Administrator access rights. This is done by going to Maintenance | Administration | User Administration and by giving the System Administrator’s access group all new access rights for Actions, Forms, Menus, Menu Options and Reports. Refer to your Release Notes for lists of the new access rights that are available. 7. Update other User Groups as needed. Procura 7- User Release Notes 23 of 155 8. If you use any standalone applications, (e.g., Generation, Status update, Visit History Calculation), you must ensure that you replace these executable files with the new files. These can be found under Procura v.7 Upgrade & Installation Files. 9. If your agency uses Synchronization, see the document Installing and Upgrading Procura & POC. 10. Allow the end users to log back into Procura when their PC’s have been upgraded with the new executable file. 11. Ask your users to select Help | Check for Updates. This will automatically download updates and provide them with the ability to install them. 1.7 Creating a Procura ‘Lookup’ Version 1. Backup your Procura database. Create a new database and restore the backup you just created to this database. 2. On a user's computer, create a new database connection to the “Lookup” database using ODBC or the Procura Connections utility. For more information, see the appendices in the document Installing and Upgrading Procura & POC. 3. Copy the Procura application files that are usually found in C:\Program Files\Develus\Procura to a new temporary location. 4. On the user’s desktop, create a new shortcut to the WinPro.exe you have just moved. Right-click on the shortcut and select Properties. On the Shortcut tab in the Target window you will see the path to the Winpro.exe. Type -d after WinPro.exe followed by the name of the database connection created in step 2 above. 5. Test the connection by logging into Procura. 6. Add a reminder message to remind users that this database is for “Lookup only”. This can be done by going to Maintenance | Administration | System Options and clicking the Prompt Users tab. Enter an appropriate message and make sure that the “Prompt Users with message when logging into Procura” checkbox is checked. Procura 7- User Release Notes 24 of 155 PROCURA 7 ENHANCEMENTS Note: These release notes provide the detail for enhancements applied from Version 6.2 to 7. Please refer to 6.0–6.1 and 6.1-6.2 release notes for details on enhancements released in the voluntary upgrade versions. 1 GENERAL Title 1.1 Description Ribbonizing Ribbonized menus that mimic the Windows user interface are found through most of Procura 7. Ribbons allow users to take advantage of context-specific toolbars that place key functionality into logical groups for easy access. ID # Roadmap Item Selecting ‘Minimize the Ribbon’ via a right mouse click from the task bar will give you the ability to ‘hide’ icons. Throughout Procura, you will see a little Hammer/Wrench icon. This will provide access to configuration options. Procura 7- User Release Notes 25 of 155 Reports are now available on the tabs to which it pertains to. For example, the Client related reports will be found under the Client tab. These reports are still available under the Reports tab and the Management tab and the access rights still apply. A Widget well down has been added to the Procura title bar. This allows the user to add Favorites and Tasks to the title bar. The Favorites panel replaces the old Configure Tools option. This will get you linked to other documents, web sites, etc… Procura 7- User Release Notes 26 of 155 Select items can be added by clicking on the Add option within the Favorites box. The following form will be displayed; This form allows you to browse for select items that the user prefers to have accessible from Procura. There is also a Widget available to add Tasks. This will expose a Task panel which simply provides a smaller footprint of tasks. They are still accessible from the Scheduling tab under Tasks or from the Planner. 1.2 City Field Size The City description field has been increased to allow for 30 characters throughout Procura. Procura 7- User Release Notes 21741 27 of 155 1.3 Dated Notes Form - Add access right for emailing We have added a new access right called ‘Email Dated Note’ that affects Dated Notes. If this access right is active, the Save/Send buttons and prompts will display as ‘Save’ whenever there is no access to the Send function. In addition, everything that relates to email will be hidden from view on the Dated Notes form. This access right will be ignored when using the paging functionality and the various read-only dated note functions, (e.g., email license information, etc). 22621 1.4 Client/Employee Schedule Performance Improvements when closing form Allow Multi select when Deleting Tasks Scheduling | Client/Employee Schedules Initially, there were significant performance issues occurring whenever a client/employee schedule was closed. This update improves how the options in client and employee scheduling are read and saved to the system registry. Users should see an overall improvement in the performance of between 28% and 34% from previous versions of Procura. 22169 Scheduling | Tasks | Enable multi-select Initially, if multiple tasks were selected and the user right-clicked any one of them, both the ‘Complete’ and the ‘Postpone’ shortcut menu options would affect all of the selected tasks. We have extended this solution so that users are now allowed to multi-select tasks for deletion. Note that this functionality is limited to user-generated tasks only. We have changed the compiler settings for the WinPro.exe utility so that the performance is improved. 22123 1.5 1.6 Performance Improvement Procura 7- User Release Notes 22464 28 of 155 1.7 1.8 Add/Del Access Rights - Extend field length to show long descriptions Add Filter for Diagnosis List on Client Intake Form 1.9 CRM, Find Contact Form, Performance Improvements 1.10 Client Merge & Employee Merge Maintenance | Users | User Administration The field length on the Access Rights form has been extended so that access rights that have long names can be seen in full on the following forms: Users | Access Rights | Add/Del Groups | Group Access Rights | Add/Del Rights | Access Rights 21656 Clients | Client Intake | Find Client | Client Intake The drop-down boxes for the Diagnosis Code and descriptions on the Client Intake form now display only nonarchived diagnosis records. 22353 Maintenance | Customer Relationship Manager The loading and operation performance of the Find Contact/Contact Found form that is used by the Customer Relationship Manager (CRM) has been improved. We have changed the form so that it now displays records based on the filters that are selected by the user, instead of displaying all records. Duplicate client or employee records may accidentally be created. Therefore, we have created Client Merge and Employee Merge utilities to enable the user to merge into one record the information that is stored in the duplicate records. 22068 Procura 7- User Release Notes Roadmap Item 29 of 155 Note: records that are attached to Scheduling Groups and those that are checked out to the Point of Care Server cannot be merged. Maintenance | Utilities | Client Merge Utility or Employee Merge Utility 1. 2. 3. Select the Client to Keep via the Select Client button. Select the Client to Delete via the Select Client button on the right side of the Cilent Merge Form. Click Merge. 4. You will be prompted with a confirmation form. Procura 7- User Release Notes 30 of 155 5. 6. 7. Procura 7- User Release Notes Click Yes and another confirmation prompt is displayed. Click Yes again and Procura will display the following prompt indicating that the merge is complete and suggests the user review the results. Click OK and Procura will bring you to the client record for review. 31 of 155 Note: Procura’s System Log will record the merge for reference. 1.11 PASE – Addition of Grid capability PASE Design We have enhanced PASE to provide the ability to display questions differently. Previously, questions displayed vertically. The grid option allows you to alter the display of the questions. Roadmap Item The user now has access to a ‘Layout’ tab within the properties of a page. Procura 7- User Release Notes 32 of 155 The layout tab provides the ability to determine how many columns will be displayed for every row of questions. Further to the number of columns, you can also define what percentage of real estate the question will use. Procura 7- User Release Notes 33 of 155 1.12 PASE – Additional Workflow events Maintenance | General Setup | Assessments We have added two additional workflow events that occur whenever a PASE document is saved. See also defect #19467: Adding/Editing a PASE Document to a Client – Save event type. “PASE – SAVE” Event Editing a Client's existing PASE Document - Save event conditions. “PASE Document” Condition 1.13 PASE – Addition of Category filter Maintenance | General Setup | Assessments A new filter has been added to the Assessments/Surveys form, which enables the user to filter by the assessment category. 1.14 PASE – Addition of new Data Link question type We have added a new Data Link question answer type to the design of PASE assessments. The Data Link answer type provides a link from a PASE document to a specific folder in the Client Information form. Clicking the link will open the form, and then display the specified folder. Note that the user will have limited use of that form. The following is a list of available data link answer types: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Procura 7- User Release Notes Roadmap Item Additional Information Allergies Attributes Care Plan Comments Contacts Dated Notes Meals Meds/Drugs Nutrition Physical Environment Service Requirements Visit History Vitals 34 of 155 1.15 PASE – Addition of new Image question We have added an Image answer type which will provide for an image to be inserted into an assessment question. When the assessment is delivered, the user can use a built-in editor to modify the image or to add annotations to it. Procura 7- User Release Notes Roadmap Item 35 of 155 A Compare Images form (located from the Assessment page in the client record) enables the user to compare annotated or modified images. This is helpful if they want to relate images that are taken during the course of a client's order or episode, or when they want to compare images from one order or episode to another. For example, they might illustrate the healing progression of a wound using a comparison of photographs that were taken while the client was receiving service from your organization. Procura 7- User Release Notes 36 of 155 1.16 PASE - Image Question Added Fit to Width scaling 1.17 PASE - Value Question Type – Accept zero as a valid value 1.18 PASE – Ability to copy questions in design mode The user can now set PASE image questions that contain a default image so that they will automatically be scaled to fit within the image question section. We have also added the ability to scale the image so that it fills the width of the section, without affecting its height. 21860 Previously, if a value of zero was entered for a ‘Value’ question type, it was treated in the same way as it would if the question was unanswered. So it was not saved. Now, Zero values are stored with the question, and are both displayed and printed. This enhancement also applies to PASE answers for Value type and Value Range type questions as well. The record will be considered unanswered only if these fields are left empty. We have enhanced the PASE designer to give the user the ability to copy PASE questions from one page to another or from one document to another during the design mode. This option if available via right mouse click on the question via design mode or under the Edit menu. 22196 Procura 7- User Release Notes Roadmap Item 37 of 155 1.19 PASE – Ability to copy an existing assessment We have enhanced PASE to give the user the ability to copy a PASE assessment within the client record. This option is available via the ‘copy’ icon when a particular assessment is highlighted. Roadmap Item 1.20 PASE – Audit Log This is a customer sponsored enhancement that supports the ability to maintain a history of changes for PASE document content. This enhancement will be enabled as a Procura licensing option labeled PASE Audit Log. When the license is enabled, the Assessment folder/page will display a View Changes icon. Roadmap Item To display the Changes to a given PASE document, the user will highlight the PASE document and then click the View Changes icon. A display that summarizes the changes will be presented to the user. Procura 7- User Release Notes 38 of 155 Should the user wish to display a more detailed view of the changes for a given Change record, the user will highlight the record and click the Details button. Following are the types of PASE changes that will be audited: Procura 7- User Release Notes Edits that change PASE question values Removed values from PASE questions 39 of 155 1.21 Read Only Department Access Editing Completed PASE documents Custom Question type value changes This is a customer sponsored enhancement that provides a business solution where their Procura users see more of the client record so that they are able to understand the client's needs in relation to other activities which are ongoing or historical. This need would involve allowing configured users to view but not edit or report on limited information in departments other than those for which they have been granted access. Essentially, this provides a user read only access to Client Department information provided the client is registered to a Department that the user has access to. 22792 Configuration steps: 1. To take advantage of this functionality you will need to add the Cross Department View-Only system reference with a value of Yes. Under the Maintenance | System Options menu on the Reference tab you will need to add the Cross Department View-Only system reference. 1.22 New Administrative Reference Number Access New Access rights are available for Client, Employee and Episode References. They are; Name Administration Client Reference Numbers – Delete Procura 7- User Release Notes Allows the user to delete a Client Reference values. 40 of 155 Rights Administration Client Reference Numbers – Edit Administration Client Reference Numbers – View Administration Employee Reference Numbers – Delete Administration Administration Administration Administration Administration Procura 7- User Release Notes Employee Reference Numbers Employee Reference Numbers Episode Reference Numbers – Episode Reference Numbers – Episode Reference Numbers – – Edit – View Delete Edit View Note: the user must also have access to ‘Edit’ in order to delete. Allows the user to edit a Client Reference value. Allows the user to view the Client Reference value. Allows the user to delete an Employee Reference values. Note: the user must also have access to ‘Edit’ in order to delete. Allows the user to edit an Employee Reference value. Allows the user to view the Employee Reference value. Allows the user to Delete an Episode Reference value. Allows the user to Edit an Episode Reference value. Allows the user to View an Episode Reference value. 41 of 155 2 EMPLOYEES Title 2.1 Description User Interface- Update Employee Form We have updated the Employee Information form to use the ribbon interface. It has also been updated from a Tab View to a Page of Folder view. ID # 22562 The user has the option to configure which pages/folders are displayed and in which order they are sorted. This is configured by clicking on the hammer/wrench icon in the top left hand corner of the form. The Employee Form Options is displayed. Deselect items that you would like hidden from view and use the up /down arrows to sort the folders in order of preference. Procura 7- User Release Notes 42 of 155 Procura 7- User Release Notes 43 of 155 2.2 User Interface – Update Employee Availability Form Procura 7- User Release Notes We have updated the Employee Availability form to use the ribbon interface. 21926 44 of 155 3 CLIENTS Title 3.1 Description User Interface- Update Client Form ID # We have enhanced the Client form to use the ribbon interface. It has also been updated from a Tab View to a Page of Folder view. Note: the PASE tab is now referred to as the Assessment folder. The user has the option to configure which pages/folders are displayed and in which order they are sorted. This is configured by clicking on the hammer/wrench icon in the top left hand corner of the form. The ‘Client Form Options’ is displayed. Deselect items that you would like hidden from view and use the up /down arrows to sort the folders in order of preference. Procura 7- User Release Notes 45 of 155 Procura 7- User Release Notes 46 of 155 3.2 Additional field – Consent to Share Data This is a customer sponsored enhancement that includes a checkbox called Consent to Share Data located on the Client General form. This gives the user the ability to mark whether or not they have received consent from the client to share data. Default is on. There is an option to disable the field via a system reference. Field Label Value Other fields Procura 7- User Release Notes Value DISABLE_CLIENTS_CONSENT Must be YES Other fields within the System Reference will be ignored and therefore can have any value. 47 of 155 3.3 Additional field – Est. This is a customer sponsored enhancement that adds a Est. checkbox beside the Birthdate field. This gives the user the ability to mark whether or not the Date of Birth has been Estimated. Default is unchecked. There is an option to disable the field via a system reference. Field Label Value Other fields Procura 7- User Release Notes Value DISABLE_CLIENTS_ESTBIRTH Must be YES Other fields within the System Reference will be ignored and therefore can have any value. 48 of 155 3.4 Additional Field – Country of Birth This is a customer sponsored enhancement that adds an additional lookup called Country of Birth on the Client General form. A new Procura lookup table has been added called CountryofBirth that will contain customer defined values. There is an option to disable the field via a system reference. Procura 7- User Release Notes 49 of 155 Field Label Value Other fields 3.5 User Interface Update Client Order/Episode form Procura 7- User Release Notes Value DISABLE_CLIENTS_COUNTRYBIRTH Must be YES Other fields within the System Reference will be ignored and therefore can have any value. We have enhanced the Client Order/Episode forms to use the ribbon interface. 22081 50 of 155 3.6 Additional Episode Folder - Dates Procura 7- User Release Notes This is a customer sponsored enhancement that includes the addition of a new folder within the client Episode called Dates. This allows the ability to store multiple occurrences of date driven activities at the Episode level. 51 of 155 Additional Lookup table set up is required to populate the Episode Date form; Refer to the online help menu for detail set up instructions: Procura 7- User Release Notes 52 of 155 Procura 7- User Release Notes 53 of 155 3.7 Episode Service Plan – Enable Conflict Checking We have enhanced Procura to enable Service Plan Conflict Checking. In order to enable the Service Plan conflict checking, the Department must be configured as shown below. This configuration is required for every Department you wish to enable this for. Roadmap Item 3.8 Service Plan – Auto Service Plan For some Funders that have pre-defined Service Plans that are common for every Order/Episode, we have enhanced Procura to auto-populate predefined Service Plans when client order/episodes are added. This is configurable at the Funder/Department. Roadmap Item The user adds them via Maintenance | Billing Setup | Funders | Department | Auto Serv. Plans tab It should be noted that the Auto Service Plan records will only be added to the new Orders that are entered after the defaults are defined on the Auto Serv. Plan tab. Any existing Orders are not changed. Procura 7- User Release Notes 54 of 155 3.9 Service Plan Configurations Procura 7- User Release Notes Service Plans are configurable at the Department/Funder level. The following options are available; Label Service Plan Use Discipline Value YES Service Plan Auth Required YES Service Plan Auth Lookup Service Plan Auth Free Form a valid lookup table YES Service Plan is Required YES SP Conflicts Force to Planner YES Roadmap Items Action Displays unique DISCIPLINES for the orders default bill table. Otherwise, displays bill tables SERVICE TYPES. Service Authorization will be a required field to save service plan A drop-down box will be displayed instead of a textbox. Note: A lookup table must be defined in order for the drop-down box to display. The user may enter free form in the drop down control Does not allow user to close Order/Episode Edit form without adding at least one Service Plan. The following Error message will be displayed "ERROR: Service Plan required for Client Order/Episode.". During conflict checking, the user will not be allowed to book the conflicted visits. The user still has the 55 of 155 SP Override Client Audit Log YES SP No Disciple/Service Type YES SP Authorization Required YES SP Conflict Custom Service YES Service Plan Auth Mask YES ability to delete the conflicted visits. During the Schedule generation, the visits will be booked to the Planner. If a user books a conflicted service plan visit then a Client Audit Log record will be generated to indicate that a service plan conflict was booked. Note: only if SP Conflicts Force to Planner is not specified If no service plan by Disciple or Service Type is found for the visits, this generates a conflict. If the service plan does not have a value in Authorization field this generates a conflict. Any Custom service plans will generate a conflict but will be defaulted to booked. So, they will still be schedulable and will be conflicted for information only. Enables you to set up a field mask for the Service Plan Authorization Field. Note: The mask is limited to 20 characters. If you have a license to use the Meal Delivery module, you can set up the following Funder/Agency Reference Labels (FARLs): Procura 7- User Release Notes Label Service Plan Use Discipline Value YES Service Plan Auth Required YES Service Plan Auth Lookup Service Plan Auth Free Form a valid lookup table YES Service Plan is Required YES Service Plan Auth Mask YES MD-SP Ignore Zero $ Rates YES Action Displays unique DISCIPLINES for the orders default bill table. Otherwise, displays bill tables SERVICE TYPES. Service Authorization will be a required field to save service plan A drop-down box will be displayed instead of a textbox. Note: A lookup table must be defined in order for the drop-down box to display. The user may enter free form in the drop down control Does not allow user to close Order/Episode Edit form without adding at least one Service Plan. The following Error message will be displayed "ERROR: Service Plan required for Client Order/Episode.". Enables you to set up a field mask for the Service Plan Authorization Field. Note: The mask is limited to 20 characters. Meal Packages can also be used to incorporate no- 56 of 155 MD-SP Authorization Required YES MD-SP No Discipline/ServType YES MD-SP Conflict Custom ServPlan YES MD-SP Conflict: Force Planner YES MD-SP Override: Cl. Audit Log YES cost (to client) add-ons to deliveries, such as to give instruction on the type of beverage to be supplied. Detects if the scheduled Meal Packages’ Service Plan has an Authorization value defined for it. Detects if the scheduled Meal Packages’ Service Type (or Discipline) has a Service Plan defined for it. Alerts the user via Conflict Checking if the Meal Delivery Visit contains Meal Package(s) that have a Service Type (or Discipline) that has a corresponding Custom Service Plan entry. Prevents the user from fully booking visits that encounter a Service Plan Conflict When a Service Plan conflict is detected. and the default “Planner” Scheduling Action is assigned to them, if the user overrides the Planner action and proceeds with a Book action, the override will be recorded in the Client’s Audit Log 3.10 Auto Service Plan enhancements Maintenance | Funders | Departments | Auto Service Plans Auto Service Plans now supports PRN with expiry dates. Auto Service Plans now display service types that are for MEALS. Estimated Counts on Order/Episode Service Plan Tab - now displays Number of Meals and Total Costs for MEALS. 3.11 Additional fields added to Client Informal Contact form This is a customer sponsored enhancement that includes the addition of several new fields on the Client Informal Contact form. The new fields are; Label Gender Date of Birth Est. Checkbox option with default as unchecked. Ethnicity This is a lookup field that references the Ethnicity Lookup table. This is a Lookup field that uses a new lookup table called COUNTRYOFBIRTH. Lookup field that uses a new lookup table called RESIDENCYSTATUS. This Country of Birth Residency Status Procura 7- User Release Notes Description This is a Lookup that references the Gender lookup table. Date field with Calendar. 21749 Details Allows the user to select a Gender option. Allows the user to select a Date of Birth option. Allows the user to indicate whether the Date of Birth has been Estimated. Allows the user to select an Ethnicity option. Allows the user to select a Country of Birth option. Allows the user to select the appropriate Residency Status 57 of 155 Procura 7- User Release Notes Main Language at Home lookup table is populated with the following values: 1. Co-resident Carer 2. Non-resident Carer This is a lookup field that references the Languages lookup table. Multiple Care Recipients Checkbox option with default unchecked. Characteristics This is a lookup field that uses a new lookup table called CARERCHARACTERISTICS. that defines the type of residency situation of the Informal contact, type Carer. Allows the user to select the main language spoken in the home. Allows the user to indicate if there are multiple care recipients. This allows the user to choose characteristics (that are provided in the lookup table) to describe the Informal Contact. They also have the ability to indicate a primary characteristic for the contact. 58 of 155 3.12 Additional Information – Ability to have Categories that are not Department specific This is a customer sponsored enhancement that allows the ability to store client attributes (stored in additional information) at the client level instead of the Department level. The user will be able to select non department specific categories. Non Department categories must be created in the Additional Information table located within the Maintenance menu. Access Maintenance | General Setup | Additional Information. When adding a new Client Category, a new Department specific checkbox is displayed. This allows you to indicate whether the category and subsequent sub categories are Department specific. 3.13 Additional Information – set as Primary This is a customer sponsored enhancement that allows the user to select which additional information category is the primary. To set as Primary, click the 1 icon. This will bold the highlighted item. 3.14 PASE - User Interface Update - PASE Client Edit We have enhanced the user interface for the PASE Client Edit form to use the ribbon interface. Procura 7- User Release Notes 21946 59 of 155 form 3.15 Order - Spec. Rate Reword error message 3.16 Client Diagnosis Edit Form, Performance Improvements 3.17 Client Intake Form, Performance Improvements 3.18 Archive Contacts(SHIN41) Client Order | Spec. Rates When trying to delete an Order Specific Rate that has been attached to visits, the user will receive a message that the rate record cannot be deleted because it is attached to visits. We have improved the performance when the user adds or edits the diagnosis in the Diagnoses/Procedures folder. 21968 Clients | Client Intake | Find Client | Client Intake There have been improvements made to the performance of the Client Intake form. Previously, the Diagnosis drop-down boxes, (i.e., Code and Description), were filled in when the Client Intake form was first opened. But, for those customers who have large diagnosis tables, this caused some performance problems. So the two drop-down boxes are now populated only when the user selects a diagnosis. This customer sponsored enhancement allows Client Contact records to be archived. Client contacts can now be archived from the Contacts folder of the Client Information form or from the Customer Relationship Manager (CRM). Both forms will allow archived contacts to be viewed in a ‘history’ display, from which they can be re-activated if necessary. 22071 22069 09227 When a contact is selected, an archive option is available via right mouse click or by selecting the Archive Contact icon. Archived contacts are not deleted so they can be re-activated. However, while they are archived, they cannot be used and do not appear on most forms. Exceptions to this include the assessment forms, (i.e., PASE, OASIS, 485, Verbal Order, MDS, Pathways), where archived contacts will still be shown on Procura 7- User Release Notes 60 of 155 assessments started before the contact was archived. 3.19 Client Reference Number Management (BCSpec47+49) The types of contacts that can be archived include the following: Client Formal Contacts Client Informal Contacts Customer Relationship Manager Contacts This customer sponsored enhancement enables you to configure a Client Reference Number to autogenerate on intake. The number is auto-generated when a new client is added and then the user selects Yes to the following Confirmation prompt. 22394 This enhancement will ensure that a client will always have a unique client reference generated upon Adding/Intaking a new client. This enhancement is independent of the current ability to generate a reference when a status change is applied. 1. To enable this capability, one of more Procura System References will be configured via menu path: Maintenance | System Options | References. Following are set up requirements for the System Reference: Field Label Value Other fields Procura 7- User Release Notes Value, Notes Generate Client Reference Must equal the Procura Client Reference Number Name for the client reference that is to be generated. Other fields will not be used and therefore can contain any value. 61 of 155 2. 3.20 Client Intake – Birthdate defaulting to ‘today’ 3.21 Dated Note – Add Cancel feature (SHIN-42) A Client Reference number must be configured that has the same Name value as the value that is stored in the Generate Client Reference System Reference. Clients | Intake Initially, when intaking new clients, the Birthdate field was being populated with today's date because the date was being transferred from the Client Find form, which defaulted empty dates to today’s date. We have solved this problem where the Client Find form will now only pass parameters, such as name, birthdate, etc., if the relevant checkboxes are checked. Otherwise, the Intake form fields will be empty. This customer sponsored enhancement allows a dated note to be cancelled. The user simply fills in a follow-up note that provides the reason for the cancellation. Cancelled dated notes will not be deleted; they will be displayed with a strikethrough. The ability to use this functionality is controlled by user access right called Cancel Dated Note. If a user has access, they will see a Cancel option via Right mouse click from the Dated Note they wish to cancel. 21711 21787 Upon the cancel action, a follow up screen with a status of Cancelled will be displayed. The user will be required to complete the Notes section in order to complete the cancellation. Procura 7- User Release Notes 62 of 155 The Cancel action will create a strikethrough line to appear on the Dated Note form for that Dated Note Record. The Cancel action will update the status of the Dated Note to Cancelled and add the Follow up Note that will provide the name of the user, date/time stamp and the reason for the cancel. Procura 7- User Release Notes 63 of 155 4 CLIENTS - USA Title 4.1 4.2 4.3 4.4 Description SoC Date on OASIS updated to reflect a change in the SoC on Episode OASIS – Key commands have been applied 485 - Add Physician Fax # to Verbal Order Printout Change Request OASIS - RFA Restriction Logic Procura 7- User Release Notes ID # When changing the SoC date on an Episode, the SoC (M0030) date on the corresponding OASIS did not change. This prevented the OASIS from being submitted if the date on the OASIS fell outside the date range of the episode. 21610 The OASIS form has been modified to conform to the Procura standard for shortcut key commands. So F7 will now launch the spell-check feature, and Control+F7 and Control+F8 will move to the next/previous pages. The Physicians fax number is now printed to the verbal order. 21729 When the user chooses to Add an OASIS document, a filter called Show All RFAs will be displayed on the M0100 – Reason for Assessment form. When checked, all RFAs will be displayed. When unchecked, only RFAs that meet the Recommended listing requirements (below) will be displayed. The filter option is controlled with an access right called; OASIS-Display All RFA Override. All of the validation rules will be overridden to display all RFAs if the Access Right is granted to the user. This will account for the potential of an exceptional circumstance being present that is relevant for a non-Medicare use of OASIS. 21460 22350 64 of 155 RFA01 – Start of Care as Only Option: If the episode has an episode sequence of 1 and no other OASIS records exist, RFA01 will not be displayed for the Episode if a completed RFA01 already exists. RFA03 – Resumption of Care as Only Option: RFA03 is displayed when the immediately preceding RFA for the Episode is an RFA06 (Transfer to Inpatient, no Discharge). RFA04 is displayed as the only option where: Episode Sequence is 2 or greater, and no other OASIS documents exist for the Episode.RFA04 will not be displayed for the Episode if a completed RFA04 already exists. RFA05 – Other Follow Up: is displayed if one of the following conditions is true for the Episode: a completed RFA01 exists, or a completed RFA03 exists, or a completed RFA04 exists. RFA06 – Transfer to Inpatient (no discharge): is displayed if one of the following conditions is true to for the Episode: a completed RFA01 exists, or a completed RFA03 exists, or a completed RFA04 exists. RFA07 – Transfer to Inpatient (with discharge)is displayed if a completed RFA01 exists, or a completed RFA03 exists, or a completed RFA04 exists. When a completed RFA07 exists for the episode, the user will be prompted and prevented from adding other assessments. Procura 7- User Release Notes 65 of 155 RFA09 – Discharge from Agency is displayed if one of the following conditions is true for the Episode: a completed RFA01 exists, or a completed RFA03 exists, or a completed RFA04 exists. When a completed RFA09 exists for the episode, the user will be prompted and prevented from adding other assessments. RFA08 – Death at Home is displayed if one of the following conditions is true for the Episode: a completed RFA01 exists, or a completed RFA03 exists, or a completed RFA04 exists. When a completed RFA08 exists for the episode, the user will be prompted and prevented from adding other assessments. RFA08 Special Circumstance: If RFA08 is entered and completed for the client, then no other RFA should be available for selection in any episode. The user will be prompted when clicking the Add button. 4.5 OASIS - New Validator Procura 7- User Release Notes Clients | OASIS OCS has released a new version of the OASIS validator. The new Validator adds some helpful error messages and corrects a few cases where error messages should have been warnings and where error messages were being displayed inappropriately. Validator Change Details Updates To Error Messages: Correcting text of error messages (the correct logic was triggering a different error message): “Count of unstageable deep tissue pressure ulcers (M1308-d3) should be answered” "Count of unstageable deep tissue pressure ulcers present at SOC/ROC (M1308-d3) should be answered." New errors: M0060 Zip code cannot be incomplete (five digits required) M0018 Physician NPI can only be numbers, no alpha or blank characters, except blank allowed when N/A is checked. M1022 When a severity rating has been entered without a corresponding other diagnosis 1-5 The OCS Verification Toolkit has been updated to generate an error for all time points when M0150 (Payer source) is not identified. Previously, M0150 generated a warning when payer was not identified in RFA 1 (SOC) and 3 (ROC). This was consistent with the OASIS-C User Manual and expectation that payer be identified at SOC and ROC. The reason for change was due to some clients unable to submit other assessments when M0150 was blank. Updates To Error Messages: An error is generated when M1307 is in the future M0110 (episode timing) cannot be NA if Payment = Medicare (Traditional) Changed RFA from 03 to 04 – M0110 cannot be NA Version_CD1 can only be “C-082009” or “C-072009”, otherwise an error will be generated M150 has Medicare (Traditional), then M2200 NA on RFA 01 or 04 will generate an error 21618 & 21785 & 21885 & 22569 & 21724 66 of 155 4.6 OASIS - Validation does not work with Inactivation records 4.7 OASIS - Send NA when M0063 does not match accepted Values RFA04 - OASIS - M0090 Date field allows dates prior to 5 days with no warning 4.8 Procura 7- User Release Notes Updates To Warning Messages: Changed message text from bedfast to chairfast in the following warning messages (to match the selected answer for M1860): "Warning: Most patients who are chairfast (M1860-5) are not fully independent in upper body dressing, even when clothes are laid out (M1810)." "Warning: Most patients who are chairfast (M1860-5) are not fully independent in lower body dressing, even when clothes are laid out (M1820)." "Warning: Most patients who are chairfast (M1860-5) are not fully independent in bathing (M1830)." "Warning: Most patients who are chairfast (M1860-5) are not fully independent in toileting (M1840)." "Warning: Most patients who are chairfast (M1860-5) are not fully independent in transferring (M1850)." "Warning: Most patients who are chairfast (M1860-5) are not fully independent in preparing light meals (M1880)." M150 has Medicare (Traditional), then M2200 NA on RFA=03, 05 will generate a warning Moving several errors to warnings: "Warning: The plan of care synopsis indicates that falls prevention interventions are not applicable because the patient is not assessed to be at risk for falls (M2250-c), but the falls risk assessment indicates that the patient is at risk (M1910)." "The plan of care synopsis indicates that intervention(s) to prevent pressures are not applicable because the patient is not assessed to be at risk for pressure ulcers (M2250-f), but the assessment indicates that the patient is at risk (M1302)." "The plan of care synopsis indicates that intervention(s) to monitor and mitigate pain are not applicable because there is no pain identified (M2250-e), but the pain assessment indicates severe pain (M1240)." Previously, OASIS Inactivation records (type X1) could not be validated. To solve this issue, the Edit | Validate menu option and right-click shortcut options will be disabled if an Inactivation record is being viewed. If the record is re-activated, these options will be enabled. The OASIS Export already skips validation on Inactivation records. If M0150 is set to ‘2 - Medicare (HMO/Managed Care/Advantage Plan)’ and the number that is used for M0063 is not a valid Medicare number, Procura will now generate a warning message during validation. On export, the invalid number will be ignored and M0063 will be set to NA. The CMS rules require that an OASIS RFA04 follow-up assessment for the subsequent 60-day episode be completed between the 56th and 60th days of the current period. To ensure that this requirement is met, Procura has added a validation to RFA04. In addition, when an OASIS RFA 04 is being completed for a Medicare episode, if the M0090 date is not within five days preceding the start date of the episode, the validation will display a warning, instead of an error. 21629 22094 21861& 22053 67 of 155 4.9 OASIS SOC - M0102 not giving validation error if left blank Procura 7- User Release Notes According to the CMS specifications, if M0102 is left empty, the M0102 NA checkbox must be checked. But, previously, the OASIS validator was not reporting an error in this situation. Instead, if M0102 was empty, M0102 NA was being checked before the validation or export was performed. This update prevents the checking of the M0102 NA checkbox. If M0102 is empty and M0102 NA is not checked, the validator and the export will report an error. 21820 68 of 155 5 CLIENTS CANADA Title Description ID # 5.1 CIS Inbox for CHRIS Offers and Referrals Effectively manage your CHRIS Offers and Referrals by pulling them, on demand, into an easy-to-use, inboxstyle workspace. This is available in Ontario only. Contact your Account Manager for more information. 5.2 MDS-HC J2 19456 5.3 MDS-HC Medication and Diagnosis Lookup (HISC-32) Client | MDS-HC This update enhances the capabilities of the ‘smart search’ so that, when the user types in the first few characters of a word, (e.g., diabetes), everything that contains that word in the Description area will be extracted. This is a customer sponsored enhancement that adds the standard Find feature for Medication and Diagnoses to the MDS form. The enhancement adds the Find Diagnosis buttons on MDS question J2 and Find Medications buttons on MDS question Q5. The buttons launch the same dialogs as are launched from the Client Diagnosis/Procedures form and the Client Medications form. The find dialog forms have not been changed. For MDS J2, the filter is set to diagnoses only, but because it is a standard dialog the ability exists for the user to change it to show procedures, and then pick a procedure. If this occurs, the user will receive an error message as the MDS form does not allow procedures in J2. 5.4 MDS-HC Diagnosis and Medication Changes (SHIN-38) This customer sponsored enhancement implements the following changes to the MDS Medications (Q5) and Diagnoses (J2) sections. The changes are controlled by system references: Diagnoses entered in the J2 section are specific to the MDS assessment only. They are no longer linked to the client diagnoses. Therefore, they will not appear in the Diagnoses/Procedures folder in the Client Information form. Diagnoses in that folder and in the J2 section of an MDS assessment are independent of each other and the diagnoses on an MDS assessment are independent of those on all other assessments. In order to preserve current functionality, a System Reference will be set up to trigger the “hide” MDS-HC Diagnoses on the client’s Diagnosis Tab. 22178 Field Label Value Procura 7- User Release Notes Roadmap Item 22251 Value Must be MDS-HC Hide Diagnosis on Tab Must be YES 69 of 155 Other fields Other fields within the System Reference will be ignored and therefore can have any value. System References are configured via Maintenance | Users | System Options | References Tab. If the System Reference is not present, or if it does not have the correct value, the MDS-HC Diagnoses will continue to be displayed on the Client Diagnosis Tab. Medications entered into the Q5 section are specific to the MDS assessment only. They are no longer linked to the client medications. Therefore, they will not appear in the Medications folder of the Client Information form. Medications in that folder and in the Q5 section of an MDS assessment are independent of each other and the medications on an MDS assessment are independent of those on all other assessments. In order to preserve current functionality, a System Reference will be set up to trigger the “hide” MDS-HC Medications on the client’s Medications Tab. Field Value Label Must be MDS-HC Hide Meds on Tab Value Must be YES Other Other fields within the System Reference will be ignored and therefore fields can have any value. Procura 7- User Release Notes 70 of 155 System References are configured via Maintenance | Users | System Options | References Tab. If the System Reference is not present, or if it does not have the correct value, the MDS-HC Medications will continue to be displayed on the Client’s Meds Tab. Important Note: A database (SQL) script must be run after this update is enabled (that is, after the relevant system references are set up, but before using MDS assessments). The script updates MDS, diagnoses and medications records to break the link between MDS diagnoses and Client diagnoses and the link between MDS medications and Client medications. The actions of the script are not reversible; a backup of the database should be made and verified before the script is run. Please contact the Procura help desk for more information. 5.5 MDS-HC Increase/decrease number of Medication entries (SHIN-38) This customer sponsored enhancement allows you to increase or decrease the number of medications that can be entered in an MDS assessment Q5 section. The number of medication lines can range from 1 to 26. Note that, if MDS assessments exist in the database, it is not recommended to reduce the number of medication lines in Q5 section to less than 11 in order to preserve historical data. Field Value Label Must be MDS-HC Q5 Medications Count Value Must be any number between 1 and 26 Other Other fields within the System Reference will be ignored and therefore fields can have any value. 222178 System References are configured via Maintenance | Users | System Options | References Tab. If the System Reference is not present, or if it does not have the correct value, the number of entries allowed on Q5 of the MDS-HC assessment will be 11. Procura 7- User Release Notes 71 of 155 5.6 MDS-HC Allow for archiving contact, without changes to locked MDS 5.7 MDS-HC Changes in Assessment Form (MDS-2010) In MDS-HC, section G is a reference to the informal contacts in the client record. If a client contact becomes deceased, divorced or changed, the user cannot delete them from the client record. They must unlock the MDS-HC assessment, and then delete them from the assessment. Therefore, the Informal Helper records in section G of the MDS assessment are no longer linked to the client’s informal contacts. The contacts can now be archived by way of a system reference. The contact is retained in MDS-HC and is not used as ‘next of kin’ in the contact section. See item 3.7 Archiving Contacts for more information. Update the MDS assessment to the 2010 standard (2008 CAPs standard). 222167&1 1805 222105 There has been a new section added to the MDS-HC form, called X, which relates to hospitals stays. Sections BB4 and BB7 have been modified so that there are new radio button options. New CAPs-related questions have been added. These question did not previously affect CAPs, but now they do, so they have been modified to support CAP processing: F1, G2 & O2 (used in the Abusive Relationship CAP) P4 (used in the Activities of Daily Living ADL CAP). We have also made a variety of changes to the following: CAP Details Display form Procura 7- User Release Notes MDS Profile Report Health, End-Stage Disease and Symptoms and Signs (CHESS) Scale Calculations SCALES: ADL, IADL Involvement, IADL Summary, IADL Difficulty, Pain, Cognitive Performance, Depression Rating, Pressure Ulcer Risk, Method for Assigning Priority Levels Caps Calculations CAPS: Physical Activities Promotion, Instrumental Activities of Daily Living (IADLs), Activities of Daily Living (ADL), Home Environment Optimization, Institutional Risk, Cognitive Loss, Delirium, Communication, Mood, Behavior, Abusive Relationship, Informal Support, Social Relationship, Falls, Pain, Pressure Ulcer, Cardio-Respiratory Conditions, Dehydration, Feeding Tube, Appropriate Medications, Urinary Incontinence, Bowel Conditions 72 of 155 6 CLIENTS AUSTRALIA Title 6.1 6.2 Description DVA PASE 2010 - NO63 – Not generating Specific Rate and not validating for staff visit DVA - Break in Care logic PASE 6111 Claim Fee Termination 6.3 DVA Spiritus Cognitive questionChange Request 6.4 Spiritus DVA Assessment Print Prompt Change Request (Defect 21424) Procura 7- User Release Notes This update fixes a problem with an order specific rate record that was not being generated for NO63. The DVA export will now generate an error if no staff visit is found in the 28-day period for NO63, which is a one-off claim. This update changes the processing of the claim fee visits for a Discharge DVA PASE assessment. On completion of a Discharge DVA PASE assessment that contains discharge start and end dates, the claim fee visits are now generated up to the discharge start date. This establishes a Break in Care. Claim fee visits are then generated, beginning on the discharge end date. If the DVA PASE assessment specifies multiple discharge start and end dates, then the claim fee visits will end on the first discharge start date and will not be generated until the last discharge end date. We have updated the DVA CNMDS export so that, in an SLNS_ONI assessment that is used for exporting a client’s data, if the questions RESPONSIBILITIES FOR OWN MEDICATION and ABILITY TO HANDLE FINANCES are answered and they have a combined weight of 2 or greater, the client will now have a code of N (No) in the Cognitive Behaviour column (column T) of the export file.Otherwise, the code will be Y (Yes). This update enhances the printing of PASE assessments that contain an Assessment type question with answer choice references of 001 (ONI) and 004 (DVA). If the user chooses reference 004 (DVA), they will now be prompted to print the ONI report and/or the DVA Veterans Only report. See also enhancement #22275. ID # 2 22256 2 22272 22302 22303 73 of 155 2 2 7 SCHEDULING Title Description ID # 7.1 Best Route Procura’s Best Route Mileage Guide helps you to reduce mileage costs and optimize scheduling by providing directions to the client’s home based on the best route so that your nurses spend more time with clients and less time on the road. Please contact your Account Manager for licensing information. Roadmap Item 7.2 Match Engine Schedule smarter by automating repetitive processes with Procura’s Scheduling Genius. Roadmap Item The Match Rules tab in the Department Module window enables you to customize each of the rules by which your employees are considered as appropriate matches when scheduling visits to your clients. The rules listed on the tab are those that would normally be seen as filters on the Employee Search form. Each of these rules can be weighted according to their level of importance, (i.e., the relative weight that you want to be added to the overall score for the visit for those employees who meet the rule). Please refer to the Online help menu (press F1) for detailed setup instructions: Procura 7- User Release Notes 74 of 155 7.3 Offers/Callout Offer visits to qualified employees without ever having to pick up the phone. Offers can be sent to the employee’s email address, mobile or to the new Procura Employee Portal being released soon. Roadmap Item Procura has been enhanced to automate the process of sending out offers to employees who are suitable to fill visits. The new ‘Create Offers’ feature is found on the employee search form. From the Planner, click Search to access the Employee Seach form. Procura 7- User Release Notes 75 of 155 Procura 7- User Release Notes 76 of 155 With the Employee Seach form displayed, click Create Offers. The Visit Offers feature allows you to automate the process of sending out offers to each of the employees who are suitable to fill the visit. The Visit Offers feature then generates the offers electronically, either by email or mobile phone, and stores them in a log file for future reference. Simply specify the following conditions and click OK. Procura 7- User Release Notes Create Offers for Top xx employee(s) sorted by Start Date - Where xx is the number of employees to which you want to send an offer to fill the visit. Expire Offers in xx hour(s) - Where xx is the number of hours during which the offer will be valid. Make Onetime Offer (subsequent visits in pattern will not have offers generated) - Generates a One-Time offer for the first visit in the pattern. 77 of 155 The offers are displayed at the bottom of the Planner. Procura 7- User Release Notes 78 of 155 7.4 User Interface Update Planner form Procura 7- User Release Notes We have enhanced the Planner form to use the ribbon interface. 221967 79 of 155 7.5 Group Scheduling – New visit type “Non-Shift” This is a customer sponsored enhancement that will allow employees whom are associated to the same scheduling group the ability to create (shift or non-shift) visits, whether or not they have a shift assigned to them. Essentially, this allows for visits to be assigned to scheduling groups without making them a shift or part of a shift. This removes the option to “Mark as Traditional” and replace with “Mark as NonShift” which will keep the visit with the group. The visit types have been renamed to provide clarity with the new visit type. Visit Name pre V7 Traditional Visit Group Visit Shift Visit N/A Procura 7- User Release Notes Visit name post V7 Traditional Visit Client Shift Shift Non-Shift Visit 80 of 155 7.6 Group Scheduling – Ability to add a Status to a Group This is a customer sponsored enhancement that allows statuses to be assigned to Scheduling Groups. This will support customers using a business model that supports referrals, admissions,discharges and waitlists via Scheduling Groups. The Client Group form has been updated to provide the ability to manage client’s status within the scheduling group. When adding a client to multiple groups, you will also have the ability to select a status to apply to those groups. When adding a client to a scheduling group, the user will be prompted with a Group Status form. The details on the form will differ depending on the status that is selected. The Status forms include: Schedulable Status form Non-Schedulable Status form Waitlist Status form Form details are provided below. 7.6.1 Group Scheduling: Schedulable Status Form Procura 7- User Release Notes The Schedulable Status form: 81 of 155 Procura 7- User Release Notes Field Name Status Effective Date Reason Notes Required field. Required field. The Status Reason drop down is derived from the Department Status reason lookup table. No dropdown option is available if a reason lookup table has not been attached to the Department status. It can be made a Required field by adding the following Department Reference: Referral Source Referral name/Details The Referral Source lookup table is derived from the REFSOURCE Procura lookup. Values for this table will be customer defined. The Referral Information grid box will display the Add Referral form. Choose from Existing Referral Choose Referral from CRM The drop down will contain all Client Scheduling Group referrals sorted by referral date. Choosing this option will open the Customer Relationship Manager to allow the user to select a contact Referral. Note: When adding a client to multiple Scheduling Groups, the radio button ‘Choose from existing Referral’ will be disabled. 82 of 155 7.6.2 Group Scheduling: Non Schedulable Status Form The Non-Schedulable Status form: Field Name Status Effective Date Reason Notes Required field. Required field. Required field. Reason drop down is derived from the Department status lookup. No dropdown option is available if a reason lookup table has not been attached to the Department status. It can be made a Required field by adding the following Department Reference: Procura 7- User Release Notes 83 of 155 Failed Admission The Failed Admission Reason is derived from a new lookup table Name = 7.6.3 Group Scheduling: Waitlist Status Form The Waitlist Status form: Field Name Status Effective Date Last Visit Date Reason Date Waitlisted Priority Rating Tool Priority Rating Review Date Procura 7- User Release Notes Notes Required field. Required field. Will auto populate based on last visit scheduled. Required field. Reason drop down is derived from the Department status lookup. No dropdown option is available if a reason lookup table has not been attached to the Department status. Date field. The Priority Rating Tool drop down is derived from a new Lookup Table Name = PRIORITYRATETOOL. Values for this table will be customer defined. Text field allowing the entry of numeric values only. Click the Add button to display the Scheduling Group Review form. 84 of 155 7.7 Scheduling Environment options - Number of Weeks Option Schedules | Client/Employee Schedules | Options tab | Environment Options We have enhanced the Environment Options for the Client Schedule and Employee Schedule forms. If the Number of Weeks that is selected is less than or equal to that which is specified in the Initial Weeks Before Current Date box, we will now display a warning message. 222459 7.8 Durations not updating in Employee Day View when edited 222703 7.9 Meals on Wheels - Client Status Change – Work Order SOW4909027161 Schedules | Employee Schedules | Employee Day View When editing visit start and stop times, if the Automatically Update Billing Duration and Automatically Update Pay Duration boxes are checked in the Environment Options window, the bill and pay duration for visits will now be updated along with the visit duration. This is a customer sponsored enhancement that applies several updates to the Meals on Wheels module: 7.10 Meals on Wheels - Route Planner – Allow user to add visits to an empty route day Procura 7- User Release Notes Previously, when a Meal Delivery order with meal visits attached was deleted by the user, the order was being deleted without a warning. The user is now warned of this and the order is not deleted. Previously, the user was able to delete an invoiced meal visit without being warned. The user is now warned of this and the meal delivery visit is not deleted. Previously, when an employee was assigned to a route, and then their department was deleted, no warning was displayed and the employee remained attached to the route. The user is now warned of this and the department is not deleted. Previously, when an employee was assigned to a route day that had a Regular pattern, and then their status was changed from Schedulable to Non-Schedulable, their filled visits would become unfilled visits. The status of the visits is no longer changed. Previously, if the user selected a route that had a Regular pattern, and then they selected a route day that precedes the start date of the employee schedulable status, clicking Search to load the Volunteer Search form caused a problem where the employee could still be assigned to the route. The employee is now hidden if their status for the selected route day is invalid. Meal Delivery | Route Schedule | Planner Previously, when the Route Planner was loaded for a Route Day in which no meal deliveries were scheduled, the options Create Onetime Delivery and Create Regular Delivery were disabled. This update enables both options. As these options are selected, the Client Lookup will display, regardless of whether meal deliveries exist. The user will be able to schedule any client for delivery. 221769& 21781& 21784& 21783 221803 85 of 155 7.11 Meals on Wheels - Route Schedule - Performance Improvement 7.12 Meals on Wheels - Enable Order Service Plans for Meal Deliveries Meal Delivery | Route Schedule We have enhanced the performance of the Route Schedule for the Meal Delivery feature. 222063 We have enabled order service plans for the Meal Delivery module. The following areas have been enhanced to support this enhancement. 221771 Client Delivery Schedules: Conflict Checking 1. Added Conflict Details to bottom of Form to display Service Plan Conflicts and Client Status Conflicts 2. Add Display Conflicts Only (with drop down to display specific types of conflicts) 3. Added Service Plan Conflict Checking with the following FARL Options: a) Service Plan Use Discipline b) MP-SP No Discipline/ServType c) MP-SP Authorization Required d) MP-SP Conflict: Force Planner e) MP-SP Conflict Custom ServPlan f) MP-SP Override: Cl. Audit Log g) MP-SP Ignore Zero $ Rates Updated Meals Service Plan Descriptions to support Number of Meals and Total Billed for the following Forms. a) Orders Service Plan Tab b) Meal Delivery Conflict Checking c) Client Schedules - Service Plan Information d) Schedule Conflict Checking - Service Plan Information e) Client Day View f) Clinical Day View EHR Frame Schedule Generation Updated to Support Service Plan Conflict Checking from Meal Deliveries. a) Service Plans (Before) b) Service Plans (After) c) Service Plans (Extra Meal) d) Service Plans (Extra Dollars) e) Service Plans (Not Planned) f) Service Plans (Custom Plan) g) Service Plans (UnAuthorized) h) Service Plans (No Service) i) Service Plans (No Discipline) Schedule Generation New Conflict Table added to Conflict Log a) 11. MEAL DELIVERY SERVICE PLAN CONFLICTS Procura 7- User Release Notes 86 of 155 8 TIMEKEEPING Title 8.1 Description Callme! - Cannot find a visit based on the Phone Number instead of the CVID Timekeeping | Batch Callme! Processing Timekeeping | Build Timekeeping This update allows Callme! users to enter four zeros (0000), instead of a visit CVID, when entering a Callme! call at a client’s residence. The Callme! verification process will then search for a matching visit using the client’s phone number, the employee’s ID number and the time of the call. Once a visit match is found, the call will automatically be updated with the CVID of the matching visit. This reduces the amount of information that is required for the employee to successfully complete a Callme! call. With the use of the system reference CALLME_FIND_CVID, agencies can change this four-digit number to any four-digit number they want. Field Label Value Other fields 8.2 Callme! - Performance Improvements Procura 7- User Release Notes ID # 2 21710 Value Must be CALLME_FIND_CVID Must be any 4 digits for example 0000 Other fields within the System Reference will be ignored and therefore can have any value. We have improved the performance of the query on the Callme! Comparison Form, Visit Query, Call Query and Exception query. 2 22095 87 of 155 8.3 8.4 Callme! - Duplicate CVID - Add client phone number to verify correct CVID Callme! HL7 import Callme processing include 0 duration visit (Change Request #21970) This change adds an additional check of the client’s phone number to the Callme! visit processing. This ensures that, when duplicate visit CVIDs are encountered in the same timekeeping period, the Callme! calls are correctly matched to visits. 22208 We have enhanced Callme! processing so that it will now process unscheduled attendance type visits that have a zero duration, and then create the associated mileage records. This requires a system reference with a reference value that matches the attendance type. 22799 Field Label Value Other fields Procura 7- User Release Notes 2 2 Value Callme! Allow Zero Dur ATT Must be the same name as the Attendance Type Other fields within the System Reference will be ignored and therefore can have any value. 88 of 155 Procura 7- User Release Notes 89 of 155 8.5 Callme! - Make Pay/Bill Duration enhancements (NW-19) This is a customer sponsored enhancement that will determine which visit durations will be updated with the actual visit duration obtained from Callme!. This requires a System Reference where the value is equal to (PAY, BILL or BOTH). Field Label Value Other fields 2 21595 Value Must be Callme! Accept Actual Duration Must be either PAY, BILL, or BOTH Other fields within the System Reference will be ignored and therefore can have any value. If the System Reference does not exist or does not have the value (PAY, BILL or BOTH) then all visit durations will be updated with the actual duration from Callme. Note 1: For Batch Callme! Processing the system reference will only be a applied if "Retain Scheduled Values for Records within Variance" is Un-Checked and all three visit durations are equal. Note 2: For Callme! Visit Comparison form the system references will only be applied when using "Accept Actual" button. 8.6 Callme! - Update the visit Stop Time based on the actual start time Procura 7- User Release Notes This customer sponsored enhancement enables Callme! processing to automatically update a visit stop time with the visit start time + duration when the visit is within variance. This can also be done manually when selecting the Match, Accept Scheduled and Accept Actual options in Callme! Visit Comparison.If 2 22205 90 of 155 Retain Visit Values is checked in Callme! System Maintenance and the system reference "Callme! Update Visit Stop Time" has value of "YES" then the visits will have their start times updated and the stop times calculated based on the actual start time + the visits duration. Maintenance | Employee Setup | Callme! System Maintenance Maintenance | System Options | References tab Field Label Value Other fields Procura 7- User Release Notes Value Must be Callme! Update Visit Stop Time Must be Yes Other fields within the System Reference will be ignored and therefore can have any value. 91 of 155 Procura 7- User Release Notes 92 of 155 8.7 Callme! - Ignore Per Visit Records for Duration Exceptions This enhancement adds the ability for Callme! to ignore the "Actual Duration Greater than" or "Actual Duration Less than" exceptions when processing visits that are billed on a per-visit basis. This requires a System Reference Callme!-Ignore per-Visit Recs. 2 22190 Maintenance | System Options | References tab Field Label Value Other fields 8.8 8.9 Callme! - Workflow Queries Performance Improvements Callme! - Visit Verification – Is set to checked by default Procura 7- User Release Notes Value Must be Callme!-Ignore per-Visit Recs Can be ignored. Other fields within the System Reference will be ignored and therefore can have any value. We have improved the performance of Callme! Late Open/Close queries. Previously, when the registry was cleared, all checkboxes on the Callme! Visit Verification Report Options form were unchecked. This update defaults the options ‘Print Actual Visits that have Allowances ‘and ‘Print Unmatched Scheduled Visits that have Expense/Mileage Records’ to checked by default when the registry is cleared. 22739 22375 93 of 155 2 2 9 BILLING Title 9.1 Description Billing Rate Records – Ability to Update or Expire records ID # The billing module has been enhanced to allow for users to Update, Expire or Delete existing Billing Rate records. The Billing Rate Module form now displays new fields. There is a new filter to show Records for an Effective Date. Additional columns have been added to display a start date and a stop date. There is also a History button that will allow the user to view the history of a billing rate record. The form has been enhanced to perform various actions via a right mouse click. They include; Option Add/Edit/Print Update Procura 7- User Release Notes Notes The Add/Edit and Print options are now also available via right mouse click and will operate the same way as clicking on the ADD/EDIT/PRINT buttons. The Update option allows the user to apply updates to any property of an existing billing rate record except for the ‘Billing Type’ field. When the user selects the Update option, they will be prompted with a Confirmation form. 94 of 155 After confirming the change, Procura will create a new billing rate record with the updates applied effective today’s date. Clicking on the History button will display a copy of the old billing rate record with a stop date applied. It will also display a copy of the new billing rate record. Procura 7- User Release Notes 95 of 155 The new rate record will be applied to visits effective the same date as the start date on the record. The new rate record will also be applied to; Expire Order default rate Target Order rate and Target Order Client charge rate Department Order default rate Care Plan activities – (only after billing calculation is performed) Meal packages – (only after billing calculation is performed) The Expire option allows the user to expire a billing rate record. Expired rate records require a target billing rate record to move existing visits/charge records that exist after the expiry date to another billing rate record. Essentially, another billing rate record must exist within the Billing table to expire one. Expense/Mileage rate records must have another Expense/Mileage record to ‘expire to’. When the user selects the expire option, they will be prompted with an expiry effective date form; Once the date is confirmed, the user will be prompted with a Select Billing Record form. The user must select another billing record to apply the visits too. Procura 7- User Release Notes 96 of 155 Click OK and the user will receive a Confirm prompt confirming the action as once this is confirmed, the action is not reversible. Once the date is confirmed, the billing rate record will be expired without having to create a new one. New color-coding then identifies those billing records that have expired. The result displays the expired record in red until after the effective date has passed. Then the record will only be accessible from the History button. Procura 7- User Release Notes 97 of 155 Procura 7- User Release Notes 98 of 155 Delete The Delete option is only available for records that do not have any visits or billing charge records attached. The user will receive a Confirm prompt. The delete action will only be completed if the record is not attached to any visits or billing charge records. If the billing rate record is attached to visits, then the Delete Visit Bill Records form containing the names of clients with those visits will be displayed preventing you from deleting the record. 9.2 Batch Payments – Cosmetic issues Procura 7- User Release Notes Billing | Batch Payments This update fixes a number of cosmetic issues with the grid on the Batch Payments form. 2 22099 99 of 155 9.3 Data Model changes for payment processing history tracking Customers who use the Payment Processing feature to manage receivables have a requirement to maintain a history of transaction activity. Therefore, the following enhancements have been made to make this process easier: We have designed a Payment Processing Transaction History table that stores the status history for a given transaction, with a date/time/user stamp that appears on the change. This table includes a place for comments so that notes can be entered. We now allow the user to create a Dated Note for an invoice transaction. The Dated Note is stored and retrievable as history for the transaction. The user can e-mail the note, use Note Templates and Note Type access rights to manage it, etc. 2 22623 10 BILLING - USA Title Description 10.1 UB04 Invoice - Does not report Meals on Wheels 10.2 Invoices - New Medicare regulation - Update logic condition code UB-04 We have enhanced the UB04 invoice to report Meal Delivery billing records. Procura 7- User Release Notes Medicare claims now require that condition codes be used for field location 18 on the UB04. The following Funder Episode Reference (ERL) is required. ID # 22091 2 2 22581 100 of 155 11 ADDITIONAL INTERFACES Title Description ID # 11.1 Additional Interfaces Additional Interfaces have been moved to a new grouping from the Procura main menu. Many require license activation and/or access rights to access them. Please contact support when you are ready to perform your upgrade to ensure the appropriate licenses can be activated. The tables below identify which interface requires a license activation and/or access assigned: Version 6.2.0.0 Additional Interface Name New Location Name of Access Right BC MoHS MRR Export QHR Payroll Export Avanti Payroll Export Imports/Exports | Billing Imports/Exports | Payroll Imports/Exports | Payroll BC MoHS MRR Export QHR Payroll Export Avanti Payroll Export License Activation Required? Yes Yes Yes Version 6.1.0.0 Procura 7- User Release Notes Additional Interface Name New Location Name of Access Right Respite Attendance Report Transport Roster Report Meal Roster Report MYOB Premier Payroll Export CSTDA NMDS Export Client Service Co-Payment Report QHR Manitoba Payroll Export Custom Pay Premium Calculation Utility Reports | Scheduling Reports | Scheduling Reports | Scheduling Imports/Exports | Payroll Respite Attendance Report Transport Roster Report Meal Roster Report MYOB Payroll Export Imports/Exports | Billing Reports | Billing CSTDA NMDS Export Client Service Co-Payment Report QHR Payroll Export Yes No Custom Pay Premium Calculation Utility Yes Imports/Exports | Payroll Imports/Exports | Payroll License Activation Required? Yes Yes Yes Yes Yes 101 of 155 Version 6.0.0.0 Additional Interface Name New Location Name of Access Right Clarity Job Cost layout Payroll Export Paris Billing Export MDS-HC Export MYOB Premier Payroll Export CSTDA NMDS Export SEHC-ADP Payroll Export SAP AR Export Competency Matching Report Budget Capacity Report Imports/Exports | Payroll Clarity Payroll Export License Activation Required? Yes Imports/Exports | Billing Imports/Exports | Exports Imports/Exports | Payroll Paris Billing Export MDS-HC Export MYOB Payroll Export Yes Yes Yes Imports/Exports | Billing Imports/Exports | Payroll Imports/Exports | AR/GL Reports | Statistical CSTDA NMDS Export SEHC-ADP Payroll Export SAP AR Export Competency Matching Report Budget Capacity Report Yes Yes Yes No Custom Premium and OT Utility Pre-Authorized Payments-CB Virtual Pre-Authorized PaymentsBMO Employee Roster Report Custom Pay Premium Calculation Utility SAP Payroll Export Yes Custom Premium and OT Utility PAP-CB Virtual POS Credit Card Processing PAP-BMO User Interface Employee Roster Report Custom Pay Premium Calculation Utility SAP Payroll Export Procura 7- User Release Notes Management | Fiscal Management Imports/Exports | Payroll Billing | Processing | Remittance Billing | Processing | Remittance Reports | Scheduling Imports/Exports | Payroll Imports/Exports | Payroll Yes Yes Yes No Yes Yes 102 of 155 12 IMPORTS/EXPORTS Title Description 12.1 ADP Payroll Export – Ability to create multiple files 12.2 Change to GP Payroll export Query 12.3 HL7 Outbound - Use activity change date if newer than visit 12.4 HL7 Outbound - Suppress client phone number 12.5 HL7 Outbound Enhancement to employee and visit trigger ref The option Create Separate Files for each Temp Local Dept has been added to the ADP Payroll Export. This option allows for the capability for creating multiple files. 12.6 HL7 Outbound - Order comments NTE 12.7 HL7 Outbound - Send Mobile Employee & Emp. Visits Only Switch 12.8 HL7 Outbound - Export screen status filter 12.9 HL7 Outbound - Do not prompt for report 12.10 HL7 Outbound Attendance type ADT message with address Procura 7- User Release Notes We have changed the GP Payroll export so that the query specifies the index that it uses. This has improved the performance of the export. We have enhanced the HL7 export so that, when visit level activities are in scope, the export will check the change date of all of the activities for that visit. If any of the activities has a change date that is more recent than the change date of the visit, the export will use it as the visit change date. We have enhanced the HL7 export so that it now suppresses the client phone numbers in ADT and SIU messages PID segments 13 and 14. Previously, there was no way to trigger the removal of an employee from the CellTrak portal during the HL7 Export. If an employee record was sent with a status of I instead of A, it was being removed. We have now added another function to the trigger reference for the export. Therefore, if the value in the specified reference is Inactive, the employee record will be exported with a value of I in STF-7, instead of the current default for all employees, which is A. For the HL7 export, we have added all active order comments to NTE segment when the switch ‘/allow_nte_order_comments’ is present. We have added an HL7 Trusted Partnership switch. The switch causes the export to find a Reference Number Name, and then examine the employee record. If the Reference Number exists, the employee will be considered a Mobile employee and will be exported. We have added a checkbox to the HL7 export that acts as a filter for sending only those records that have a Schedulable status. This will apply to client and employee exports, (i.e., ADT and MFN message types). It will create a message file for that client/employee, in the departments in which they have a Schedulable status. Previously, when the HL7 export was used to manually export data, problems such as clients without client ID references, employees without employee ID references, etc., would cause a prompt to display to the user. The prompt would ask the user if they wanted to view the validation report. This would then cause the export to have to wait for a response from the user. Therefore, we have enhanced the export to display a validation error report prompt when the user has selected the Display Report option or when validating. There is currently a partner option for visit type messages that allows the user to export attendance type visits. But, previously, there was no way to communicate the actual attendance types themselves to CellTrak in order to populate them on their portal. Therefore, we have added a new trusted partner option that allows for the sending of attendance types as ADT client messages only. ID # 2 22116 2 22306 21969 21974 2 2 2 21964 2 21851 2 21740 2 21763 21764 21757 103 of 155 2 2 12.11 HL7 Outbound - Employee Area STF-11.8 12.12 HL7 Outbound - Trusted partner drop-down select on export 12.13 HL7 Outbound - Client supervisor requirement NTE 12.14 HL7 Outbound - Add employee ID to visit message 12.15 Removed the last comma in QHR Payroll Export Change Request 12.16 HH-CAHPS Export 12.17 SAP Payroll Export Export files were missing hardcoded values 12.18 QB AR Export - Removed Employee Name FARL 12.19 HL7 - Callme changes VONCAN-50 12.20 HL7 - Outbound VON Medshare changes Procura 7- User Release Notes As part of the SEHC CellTrak implementation, SEHC has added a requirement for Employee Discipline to be communicated to CellTrak via the HL7 interface. They are storing the Employee Discipline in the Area field. Therefore, the Employee Area will now be written to the STF-11.8 position. Note that STF-11.7 is currently not used and will be indicated by an extra element delimiter. For customers with a large number of departments, it was necessary to add a filter to the HL7 export screen in order to allow for the re-uploading of data to third-party HL7 applications. Therefore, we have added a drop-down box to the export form to allow for the selection of a trusted partner. When a partner is selected by the user and the Validate or Transmit action is taken, all departments to which the trusted partner is validated by department reference will be included in the export. We have added a switch to the HL7 export called allow_supertype "Case Manager". When the trusted partner option is used, only those clients who have supervisory requirements that pertain to a specific type of supervisor will be exported. Previously, when two visits for the same client on the same day were assigned the same CVID, CellTrak would read them both as updates to the same visit. This meant that one of them was never actually displayed on the mobile device. Therefore, in order to prevent those visits that have already been completed using the existing numbering system from being affected, we have added a partner option with a date parameter. We have added employee ID to SCH message segment one (1). We have fixed a problem where the last comma on the QHR payroll export file was causing errors. This comma will now be removed and will no longer be exported. We have made numerous changes to the HH CAHPS export. These include cosmetic changes to the menu option name and to the interface, as well as changes to the functionality. We have fixed a problem with the SAP Accounts/Receivable export where some of the columns in the resulting CSV file were missing values. We have added a Funder Agency Reference Label (FARL) that removes the employee’s first name from the export so that it does not display on the QB Invoice. This change adds the ability to process Allowance Codes that have been entered by field staff when closing calls in Callme! or from HL7 messages transmitted to Procura. We have added the following to the HL7 export: Visit frequency field (i.e., visit pattern) Shift Code field Trusted partner option /allow_visit_pattern. This option adds the interpreted text of the visit pattern frequency to the SCH-11.2 element for all visits that have a SCHED_ID, (i.e., the text that is displayed in schedule generation for the Regular pattern). For example, if the schedule associated with a visit contains a pattern of WX for every week, the text ‘Every 1 Weeks’ will be entered into the SCH-11.2 element. 2 21776 2 21778 2 21779 2 21951 22524 22201 2 2 2 22587 2 21844 22380 2 2 22342 104 of 155 12.21 HL7 import - Retain scheduled visit activities Change Request 12.22 HL7 - Outbound changes for Medshare eMotion (BAYCORP-127) 12.23 HL7 - VON SAP Payroll Export - Disallow specific attendance type 12.24 HL7 import – Callme! processing include 0 duration visit 12.25 HL7 import - Completed visit detailed dated note 12.26 Hl7 import – Now allow mileage to be attached to cancelled visits 12.27 HL7 Outbound CellTrak Attendance Type Address 12.28 HL7 PROHL7X.EXE - Client Status Transmission Change Procura 7- User Release Notes Previously, when importing completed visit ORU messages into Procura, all Activities were removed from the Scheduled Visit before the completed activities were added from the ORU message OBX segments. Therefore, we have added a trusted partner option to retain the Activities attached to the currently scheduled visit with existing durations intact. Any unscheduled Activities that are found in the ORU message OBX segments will be added to the existing scheduled visit Activities. The full Activity list will be included in the Client Vitals entry for that visit, as well as the Detail Dated Note. If a Visit Activity is contained in an OBX segment that does not already exist on the visit, it will be added to it. For example, if a visit is scheduled with Activities A, B and C, and the completed visit that is imported has Activities A and D completed and Activity B and C not completed, the resulting visit in Procura will retain all ActivitiesA, B, C and D. We have made the following changes to the HL7 Outbound partner type ‘Procura HL7 – Outbound’: 2 22297 22392 2 The trusted partner option /allow_multi_cltdept now includes the department name and ID number in segment PV1-3. We have added a new trusted partner option called /filter_IN1_dept. This option requires the trusted partner option listed above. The trusted partner option listed above will be change to include IN1 segments in the ADT message for those orders that exist in the department for which the ADT message is created. We now allow IN1 segments to be included in ADT^A03 messages. We have enhanced the SAP Payroll Export to allow for the capability of excluding specific attendance type visits by way of a system reference. Any attached expense/mileage records will continue to be exported. We have enhanced the batch Callme! processing function to include unscheduled attendance type visits that have a duration of 0. This will result in the creation of a payable, Home Visit with a zero duration and an attached payable mileage record. This functionality requires a system reference. We have developed visit detailed dated notes, which allows for the export of a dated note in NTE segment. We have enhanced how the HL7 import handles a cancelled visit so that Callme! processing can create a mileage record for the visit. We have enhanced the HL7 export so that, if an Attendance Type has an address, an extra PV1 or PID segment will be added to the message for that Attendance Type. Previously, the PROHL7X.EXE utility and the menu-based export utility PROXHL7.BPL would transmit all client statuses in their outbound client files. If a status was future-dated, it would also be sent and processed immediately by the receiving system. This resulted in an immediate discharge of planned future discharges. Therefore, we have enhanced the HL7 export to only transmit statuses when their start date is less than or equal to the date on which the utility is run. 2 22948 2 21970 22029 2 2 21981 2 22506 21762 105 of 155 2 13 IMPORTS/EXPORTS USA Title Description 13.1 OASIS Export – Default Filename - Prompt or add seconds 13.2 OASIS C Export Clinician, Supervisor, Team in CMS_USE Change Request 13.3 OASIS - ANSI 270 - 99+ patients GS06 and SE02 increment by 1 13.4 OASIS - ANSI 270 Added validation for Rejection 'missing City/State/Zip' 13.5 OASIS - ANSI 837 - IMSP Export is missing items in secondary claim The export and log file names will now include the seconds as a suffix. Therefore, the name format will be XOASIS_ YYYYMMDDHHNNSS. For example, if the current date/time is 01/05/2010 9:23:45, the file names will be XOASIS_20100105092345. Previously, the OASIS export would add extra data to the AGENCY_USE field in the OASIS submission record. For OASIS-C, the AGENCY_USE field was removed. That field was used for storing statistical and benchmarking services. Therefore, it will now be stored in the CMS_USE1 and CMS_USE2 fields when the OASIS record is exported. This is compatible with OASIS-C submission record requirements. This update stores GS06 and GE02 in the ANSI 270 Benefit Eligibility Inquiry Export with the same value as is used in ST02 and SE02. 13.6 ANSI 270 - Code BHT06 only for Medicaid 13.7 Billing - New Medicare regulation - Update logic condition code Procura 7- User Release Notes This update validates segment 2100C:N4 in the ANSI 270 Benefit Eligibility Inquiry Export. It also indicates if the subscriber is missing information from the City, State or Zip field. This updates includes an enhancement that ensures that, when a secondary claim is reported by the claiming person, the client’s date of birthis recorded in segment 2320:DMG. Cents will no longer be reported if the amount contains zero cents. For example, 100.00 will be reported as 100. This correction affects segments 2300:HI:BE 01 thru 2300:HI:BE 12, as well as 2300:AMT:C4. We have updated the ANSI 270 export to exclude segment element BHT06 for Medicare type funders. ID # 2 21628 2 21743 22534 2 2 22528 22678 2 2 21797 The Conditions codes are now sorted alpha-numerically. A new Funder Client Reference Label (ERL) has been added to report an additional condition code for the segment 2300:HI:BG:01-02. 22518 106 of 155 2 14 IMPORTS/EXPORTS CANADA Title Description 14.1 PMI Advanced Export Performance improvements 14.2 HL7 - Manitoba Client Registry 14.3 HOBIC Export This update improves the performance of the PMI Advanced Export. ID # 2 22064 This update includes the development of the Manitoba client registry Passive mode. The Manitoba client registry is an HL7 export of client information. We have made the following enhancements to the HOBIC export: 2 22395 21933 2 14.4 HOBIC Export – Fixed a problem with the Ampersand character 14.5 HOBIC EXPORT – We now include the Date Time stamp to the file name 14.6 HOBIC Export Encounter ID 14.7 VON SAP AR Export – Now use | to separate elements in item textChange Request Procura 7- User Release Notes For PV1 segment, the first formal contact will be the case manager For Seq 52, the second formal contact will be the primary physician For Seq 7, the third formal contact will be the referring physician For Seq 8, the fourth formal contact will be the consulting physician For Seq 9, the health card number and province in the health card field will be separated with a carrot (^) because they are separate components. For example, previously, the field was being exported as 2223331119&CA-ON. It will now be exported as 2223331119^CA-ON. We have removed the space from within the postal code. In the OBX segment (field 3), the Diagnosis on Admission was being exported as DIAGADMIN. It is now exported as DIAGADM. If the CCAC Service Code field is blank, we will now export the value 60. We have enhanced the HL7 export so that the ampersand (&) character that precedes the telephone extension will be replaced with a dash (-) character. 21987 We have added to the HL7 export file namea Date/Time stamp that includes minutes and seconds. The stamp will be formatted as YYYYMMDDHHMMNNSSZZZ. 22003 For the HL7 export, when changing the client status to either Discharge, Deceased or Reactivated, the Encounter Number should always reference the Latest Active Client Status History record ID number for that department. Therefore, we have enhanced the export accordingly. Because the SGTXT field contains a date, a comma, a space, and then a name, the VON SAP Accounts/Receivable export will now use the character | to separate elements in item text. 2 2 2 22007 22713 107 of 155 2 14.8 CMIPS II Billing Export Padded SOC date with spaces Change Request 14.9 MoHS MRR Export Question Type Change We have enhanced the CMIPS II Billing Export so that the SOC Obligated date is now padded with spaces whenever no date has been recorded. The BC MoHS MRR Export has been updated to retrieve the answers to the following questions from the Text field, instead of from the Value field: Question Question Question Question Question Question 3.51 3.53 4.14 4.19 4.20 4.21 - 2 22193 2 22227 Activities of Daily Living (ADL) Long Form Scale (S.11 MRR) IADL Involvement Scale (S.13 MRR) Temporary Rate Reduction Amount (S.24 MRR) Daily Amount for Home Support (S.28 MRR) Monthly Rate for Residential Care AMOUNT (S.27 MRR) Monthly Charges for Assisted Living (S.27 MRR) 15 IMPORTS/EXPORTS AUSTRALIA Title Description 15.1 Compacks Export - NEW Imports/Exports | Exports | Compacks/HAH Export ID # This is a new export that will provide client service details for the purpose of online claims submissions.The report information is extracted and reported from information found in the Client record, PASE documents and Visit information. The detail setup and information is stored in the Procura online help menu: Procura 7- User Release Notes 108 of 155 15.2 HACC Export - Add Information Validation no longer passes 9 values to MDS 15.3 HACC Export Background Coordination Time Procura 7- User Release Notes The Additional Functional Profile questions, (i.e., Item 66, positions 1-5), had logic added to them previously so that, if these questions were not answered, a warning would display on the validation report and a 9 would no longer be passed through to the MDS. This was done for positions 2-5. However,this logic should also apply to position 1. Therefore, if the question is not answered or if the answer reference equals 9, (i.e., text is not answered or unanswered), an error message will now display in the report and the client will not be exported. Imports/Exports | Billing | HACC Export When the output from the HACC export is expressed in Time, the Background Coordination Time will now be calculated for those visits where the Record Type for the attached billing record is defined with the same value as that of the Hours. This applies to BGT Direct, BGT Indirect and BGT Other record types. 2 22759 2 22381 109 of 155 15.4 HACC Export –Field Changes Procura V7 contains a number of new fields that allow data elements that are included in the HACC and other exports to be stored as part of the Client and associated records instead of a PASE question answer.The extract logic change to allow reading data from the new core fields is enabled by the presence of a System Reference with the following properties. Field Label Value Reference Number 1 Other fields Value Must be HACC v7 Field Changes Must be Yes Must be HACC Other fields within the System Reference will be ignored and therefore can have any value. If the system reference is not present then the extract logic will not be changed. Note: Reference section 3 ‘Clients’ for information on the new data fields. 15.5 CSTDA Export – Field Changes 15.6 HACC Export - Changes CMS R2-001 and BCCR104+139 Procura 7- User Release Notes Procura V7 contains a number of new fields that allow data elements that are included in the CSTDA Export and other exports to be stored as part of the Client and associated records instead of a PASE question answer. The extract logic change to allow reading data from the new core fields is enabled by the presence of a System Reference with the following properties. Imports/Exports | Australian Exports | HACC Export See SRS-HACC_2.0_Export_v.2.07.doc for details. 2 22466 110 of 155 15.7 DVA CNMDS Export DVA_2010_AU Validation and export to Excel 15.8 DVA XLS layout Change Request 15.9 DVA Export – Validation Change Request 15.10 CSTDA Use Current Address Change Request 15.11 Palliative (NT51) - Do not validate No Staff Visits found in claim period 15.12 DVA - QC 154 Break in Care date logic Change Request 15.13 DVA - Discharge/Death not reported in correct period (6119) Imports/Exports | Billing | DVA CNMDS Export This update fixes a problem with the DVA CNMDS export where it was creating a comma-delimited CDS file that was then opened in MS-Excel. The export will now create an XLS file instead. Imports/Exports | Billing | DVA CNMDS Export This update fixes a problem where, when the Excel file was generated by the DVA CNMDS export, the background of certain cells in the file was colored yellow. All cells are now saved with a background color of white. For the DVA CNMDS export, wound care will now only be reported on the first claim item code for a given 28-day period. If the reporting period is greater than 28 days, wound care will also be reported on the first claim within the next 28-day range. For example: Claim date May 1 - Wound Care is Reported Claim date May 9 Wound Care is not Reported Claim date May 29 - Wound Care is Reported Claim date May 30 - Wound Care is not Reported For the DVA CNMDS export, the client’s current address will be used for columns 8a, 8b, 8c, and 8d of the Service Users, (i.e., Client Data), record layout, instead of their permanent address. Palliative (NT51) visits for the DVA CNMDS export are no longer validated for staffing visits. 2 22096 2 22264 2 22222 22911 2 2 21532 The Break in Care date for the DVA CNMDS export is now determined based on the clients claim period, (i.e., Claim Date + 28 days), instead of on the export period dates. Previously, the DVA CNMDS export was not validating that the previous assessment was actually in the previous export period. This issue has been fixed. If the previous claim is in current export period, the discharge/death claim will now be exported. 2 21540 2 21566 16 REPORTS Title Description 16.1 Billing Details Report Performance Improvements 16.2 Client Listing Report Performance Improvements We have improved the performance of the Billing Details report. Previously, the query would display all of the records in the entire database. Now, the report examines the references for each order to determine which records to display. Previously, the Client Listing report was very slow when filtering by a specific Care Plan activity. We have now improved the performance of this report. Procura 7- User Release Notes ID # 22066 22085 111 of 155 2 2 16.3 Client Dated Notes Report - Performance Improvements 16.4 Client Calendar Schedule - Ability to change format 16.5 Visit Counts By Funder And Billing Code Performance Improvement 16.6 Employee Roster Report Date Column Headers Procura 7- User Release Notes We have improved the performance of the Client Dated Notes report. 2 22086 This update allows for the capability of changing the font size of the Days per Week. In the previous format of the calendar, visually impaired clients had trouble seeing the small type. Therefore, we have added the option to print the report onto Legal Size Paper and to select a larger font, to a maximum of 12 points. We have improved the performance of the Visit Counts by Funder and Billing Code report. 1 18661 2 21722 The Date columns in the Employee Roster Report are now displayed using the Windows ‘short date’ format. 2 21833 112 of 155 16.7 Client Assessment Report Enhancement Reports | Client | Client Assessment Report The Client Assessment report has been enhanced with the ability to print more client information contained in the client record. 16.8 Capacity Manager - Call Me Hover Feature Procura 7- User Release Notes The Capacity Manager now includes all CallMe! calls in its count of received calls, no matter what the status of the call is. The CallMe! batch process does not need to be run for a call before the Capacity Manager will count it. 2 21744 113 of 155 17 REPORTS - USA Title Description 17.1 California Reporting Unduplicated Patient Listing and Count CRW Report The CRW Report has been updated so that it sorts patients in alphabetical order. ID # 2 21941 18 REPORTS - CANADA Title Description 18.1 Report Writer - Transport Roster Report - Add visit dates The CRW Transport Roster report now displays the visit start and stop times in the AM/PM format beneath the visit information. ID # 2 22900 19 REPORTS AUSTRALIA Title Description 19.1 CRW - GST Payment Report v1 Paid Invoices 19.2 CRW - Staff Productivity Report Previously, the date range on the GST Payment report referred to Invoice Date on the report interface. Therefore, we have changed the label on the report to Payments-Date Range. This release corrects an issue where the types of visits that were counted when the Indirect% and Admin% values were calculated was incorrect. Now, all attendance type visits are excluded from the indirect% count, and both Administration Time and Case Conference are counted as part of Admin%. This update now excludes from the Client Services Co-Payment Report those records that use employees with 'DVA Claim Fee' as a last name. This update enhances the printing of PASE assessments that contain an Assessment type question with answer choice references of 001 (ONI) and 004 (DVA). If the user chooses reference 004 (DVA), they will be prompted to print the ONI Report and/or the DVA Veterans Only Report. See also enhancement #22303. 19.3 Exclude DVA Claim Fee Visits from reports 19.4 DVA ONI - Not printing core ONI in 6.2 Procura 7- User Release Notes ID # 21923 2 2 22833 2 22414 22275 114 of 155 2 DEFECT CORRECTIONS 20 DEFECT CORRECTIONS Title 1 2 3 4 5 corrected Description OASIS spell check OASIS and 485 – Medications not saving linkage to MEDDB or Custom Medications BPL 6.2.1.5 Archived service plans showing on the final 485 CIS Inbox – Not finding matches based on bill codes CIS inbox - Directions to Home field being overwritten 6 CIS Inbox Permanent Address 7 CIS Inbox - Allows picking of archived funders 8 MDS-HC Comment Changes grid does not expand with the size of the window Australia - NB01 not creating with Propase.bpl 9 10 11 Employee Schedule report is double-spaced Callme! - HL7 Procura 7- User Release Notes ID # Clients | OASIS Previously, if the user entered text into questions POC21/22, and then saved the OASIS, returning to the OASIS and running the spell-check feature on these fields would produce an error. This update corrects the problem. Client | OASIS Client | Episode | Physician Orders Previously, when changes to medications in OASIS or 485 were saved, the link from the existing records to the Medications database and Custom Medications would be broken. This update corrects this issue. Clients | Episodes | Physician Orders | Plan of Care (485) Report Archived service plans will no longer be reported on the Plan of Care (485) Report. Clients | CIS Inbox This update fixes an issue where funders were not matching properly on bill codes. 21729 Clients | CIS Inbox This update fixes an issue where, if there were directions to the client’s home, they were being deleted if the CHRIS CIS Inbox Referral did not specify those directions. Client | CIS Inbox This update fixes an issue where the client’s permanent address was being updated by the CIS Inbox Referral processing if the Update checkbox was not checked. Clients | CIS Inbox This update fixes an issue where archived funders were still available for selection on the Service Referral and Service Offer processing forms. Client | MDS-HC This update fixes a problem where the Changes grid on the MDS-HC Follow-up/Special Comments form did not resize if the form was resized. Clients | PASE This update corrects an issue where a NB01 Claim Fee visit was not being generated when the PASE assessment was completed. Reports | Scheduling | Employee Schedule Report This update fixes an issue where the format of the Employee Schedule Report was double-spaced. Imports/Exports | Imports | HL7 Import 22746 22537 22446 22755 22660 22756 22411 22243 22206 22698 115 of 155 12 EDCCALLS Unique ID in AUX_ID Field Billing - HCFA 1500 does not use 15 minute units properly 13 Edmonton CCLD Summary Report - Sort is incorrect 14 Schedules Date Format and Employee Availability date format 15 Billing Details Navigation Buttons Go Grey 16 Visit that splits over end-of-billing-batch-date duplicates 17 Promaint.bpl 6.0.1.1 Caused Rate Grouper to be mandatory 18 19 calculation Clients Requiring Re- Billing Rates Module: Override Pay Procura 7- User Release Notes We have resolved an issue where duplicate opening and closing calls were being created in Callme! Billing | Invoices | Print Invoices Previously, if the Funder Agency Reference Label (FARL) with the label ‘15-Minute Units’ and a value of Yes was defined, the billing durations of visits was not being translated into units properly. This update fixes this problem and prints the duration to Box 24G on the HCFA 1500 form. Reports | Billing | CCLD(Edmonton) Report This update fixes a problem where the first row of the CCLD Edmonton Summary Report (HCIS) was displayed when it should not have been. This resulted in duplicate rows appearing on the report, which was affecting the totals. Employees | Availability When creating a new employee specific rotation, which involves a time that exceeds 12:00 noon, that time was displayed in 24-hour format within the calendar. However, in the Day Details section, it displayed in the standard 12-hour format. This problem has been fixed. We have updated the Employee Availability form to format time based on the option ‘Display 24-Hour Time’ in the Environment Options window. Billing | Details In Billing Details, if the user selected a client that was not part of the batch, the navigation buttons for Previous and Back-To-First were disabled. This issue has been corrected. Users will now be able to use the Back/Next buttons to navigate. Billing When a visit is split over midnight of the last day in a billing batch for a client, and the user recalculated the billing for that client, the portion of the visit that would normally fall into the next billing batch was replicating itself in the billing records. This problem has been fixed. Maintenance | Billing Setup | Billing Rates Module When the user using a non-USA database attempted to add a new billing rate after applying a new .bpl file, the Rate Grouper field was mandatory, but not functional. Therefore, they could not add a new billing rate. This issue has been corrected. The Rate Grouper is no longer mandatory for nonUSA databases. Billing | Clients | Clients Requiring Recalculation If the Timekeeping order for a client was changed to an order that started before the billing period started and that ended before the billing period ended (but after the period started), that client would not display in the list requiring recalculation. This issue has been resolved. Maintenance | Billing Setup | Billing Rates Module | Billing Records When the user created a new Billing Table, the Override Pay Rate drop-down box would be blank, even when the appropriate Pay Tables and Labour Agreements were validated. This caused the Override Pay Rate drop-down box to be empty when they added or changed a billing record in a new Billing Table. This update has corrected the issue. 22219 22481 22179 22225 21633 21603 22310 22279 116 of 155 20 Expenses add via Quick Vis Intake, Description not available 21 Billing Batches - No validation when adding blank, new Billing Batch 22 PROWAM.EXE Performance Improvement 23 Visits matched outside variance not included Callme! - Matching Problems with CVIDs 0000 24 25 CVID of 0000 Caused visits to not be matched 26 ProHL7 looking to SysNextKeys row EDVisits Accept Schedules Brings Across Allowance Code 27 Scheduling | Employee Schedules | Quick | Expenses | Add When the Expenses button was used to open the Expense/Mileage Record Information form from the Quick Visit Intake form, the drop-down boxes for the Description, Pay Record Type, Select Order To Bill and Bill Record fields were lost behind the form. This update ensures that these lists will always appear on top of the form. Billing | Billing Batches | Add When the Description field in the Calculation Batch window was left blank and the user clicked the OK button, no error message displayed, even though the Description field is a required field. This problem has been fixed. This update improves the performance of the PROWAM.EXE utility. Previously, the check for existing workflow tasks query was filtering based on data within a memo/text field and could not be indexed. 21593 This update fixes a problem where allowance codes were not being processed for matched CallMe! calls that were outside of variance. Timekeeping | Callme! This update corrects an issue for Callme! users that use the four zeros (0000) for the CVID. If an opening Callme! call had an incorrect phone number with no closing call, the call was not being matched to the correct visit. So subsequent calls from that employee, which did have the correct phone numbers, were not matched because their visits where already matched to the incorrect call. With this update, opening Callme! calls will now only match calls to clients using the opening call telephone number and they will only use the closing call telephone number if the opening call number is incorrect. Timekeeping | Callme! When a Callme! User was using the four zeros (0000) for the CVID, all of the visits that were entered in Callme! were being ignored by Batch Processing and the PROWAM.EXE utility. A visit that was assigned a CVID of 0000 was causing the Batch Callme! Processing to skip the telephone matching logic for CallMe! Visits. This issue has been resolved. Note that customers using the Working Alone solution will need to use PROWAM.EXE 6.0.0.9 or higher to receive this correction. This update fixes an error in the main query where the table name EDCVISITS was misspelled. This caused the values entered by ProHL7 to conflict with pre-existing values. Timekeeping | Adjust | Callme! | Callme! Visit Comparison When an unmatched Scheduled Visit was selected, Procura was attempting to find a corresponding Actual Visit. If it did not find the corresponding Actual Visit, the cursor would remain on the previous Actual Visit, even if it was already matched to another Scheduled Visit. So, when the user clicked the ‘Accept Scheduled’ option, the Allowance Codes for the prior record were added to the unmatched Scheduled Visit. 22574 21700 22527 21931 22172 22271 22371 This problem has been fixed. Now, when a user selects an unmatched Scheduled Visit, if Procura cannot find a potential unmatched Actual Visit and the cursor is sitting on an Actual Visit that is already matched to a different Scheduled Visit, that Actual Visit will be deselected. The user will then be required to find a different match. Procura 7- User Release Notes 117 of 155 28 Detail Printing Format from Web Portal 29 Conflict Checking & Verified Visits Change Request 30 Batch Processing Report: Dept Filter 31 Callme! - Duplicate alerts after visit change 32 Callme! Allowances Using Accept Actual button does not generate mileage 33 Callme! - Only Timeless visits accept duration as actual. Callme! WAM Task Link Comments to Call (BAYCORP-115) 34 35 Callme! - Employee Maintenance Not Refreshing 36 Callme! Employee Maintenance: OK not transmitting change Procura 7- User Release Notes The following problems have been fixed in the Client Detail report for Callme!: 22351 Client Name should be in the format: First Name and Last Initial General Information should exclude the Birthdate Client Numbers should not be reported Scheduling | Client/Employee Schedules Previously, it was possible to send Verified Visits to a planner via conflict-checking of Employee Availability. Once they were listed on the planner, these visits could not be removed. So we have adjusted the checking for availability conflicts so that Verified Visits will be ignored. Conflicts with Employee Availability will no longer be generated for Verified Visits. Note that Verified Visits will still cause availability conflicts for Unverified Visits. Timekeeping | Callme! | Print When the Department filter was used for the CallMe! Batch Processing Report, unmatched visits for employees who were not assigned to the selected department were being included when they should not have been. This issue has been resolved. Only those employees who are valid for the selected department will now be printed. After a Callme! call is opened, a task is generated for a visit. But, previously, if the user edited that visit in the Scheduling module, new visits were generated with new visit ID numbers. A subsequent opening call would then cause another task to be generated for the new visit. This problem has been fixed in the PROWAM.EXE utility. If the change date of the visit is later than the stop/start dates of the visit, the visit will not be included for generation of workflow tasks or email notification. This update fixes a problem with Callme! Visits to which allowances were attached, such as expense/mileage. Previously, if those visits fell outside of variances, the visit was not verified, nor did it have expense/mileage generated. If the user clicked the Accept Actual button, the visit was verified, but the allowances that were attached to it did not generate expense/mileage records. With the application of the Callme! Accept Actual Duration enhancement, visits with a start and stop time were not being processed correctly. Only timeless visit were being correctly processed. This problem has been fixed. See also enhancement 21595. Timekeeping | Adjust | Callme! Visit Comparison The Callme! WAM process can create tasks if calls are not received when they are expected to be. But these tasks were only visible on existing task forms, not on the Callme! Comparison form. This problem has been fixed. Now, a grid is displayed in the lower left-hand corner of the form, which lists any of these special tasks that are attached to the selected visit. Only a subset of the task information is shown in the grid. But double-clicking a row in the grid will display all of the task information. If the visit has none of the special tasks associated with it, the grid will be empty. Maintenance | Employee Setup | Callme! Employee Maintenance The Employee Maintenance form was not being refreshed after the user made edits to the Callme! options for an employee. This issue has been corrected. Maintenance | Employee Setup | Callme! Employee Maintenance When the user made edits to the Callme! options for an employee, the OK button was not automatically transmitting the changes. This issue has been corrected. 22421 22462 22505 22103 21730 & 21271 22092 22246 22247 118 of 155 37 Automatic update will uncheck the Employee 38 Complete Task Modular window 39 Web Portal - Users can no longer be prevented from selecting dates. 40 HL7– only_transmit_current_ status 41 NW-21 Not calculating correctly 42 Visit Activity Script Request (SEHC/CellTrak) 43 Client Audit Log Department status change - hide the date 12/30/1899 44 Client Audit Log order stop date is incorrect when order status changes Procura 7- User Release Notes Maintenance | Employee Setup | Callme! System Maintenance When updating the Callme! Information for an employee, errors that were received from the call service were turning the Auto-Update Option off in Callme! System Maintenance. This problem has been fixed. An Update button has been added to the Callme! Employee Maintenance Edit form that will be enabled if the Auto-Update Option is disabled in Callme! System Maintenance. This will allow users to manually update the Callme! information for a single employee if they do not wish to use the Auto-Update method. Scheduling | Tasks | Edit Task | Complete Button When the user chose the option ‘The task cannot be completed’ without choosing a reason from the drop-down box, the error message that was displayed was lost behind the window. This problem has been fixed. Previously, users were able to select a date range on the Procura Employee Portal via the Show Schedule button. But this action was not always desirable. Therefore, we have added the option USERPICKDATES to the CONFIG.PHP file, which the System Administrator can set to T (true) or F (false). This will determine whether the Show Schedule button will display to the user. Imports/Exports | HL7 Transmission When the –only_transmit_current_status option is enabled on the Trusted Partnership and a ‘0’ is specified at the end to support varying time zones, the current date was not being updated correctly. This was causing the utility to export all statuses. This problem has been fixed. Timekeeping | Build Attendance type visits other than ‘Home Visit’ were being included in the Custom Mileage Rules calculation. This was adjusting the calculations incorrectly. This issue has been corrected. Only attendance type visits for ‘Home Visit’ will be included for the purposes of the Custom Mileage Rule calculation. When visit-specific activity durations were used as a means of providing information about the length of a visit, the HL7 utility was removing the activity for the visit if the employee who operated CellTrak did not ‘Complete’ it on the device. This caused the visit to be billed and paid at an incorrect rate. This problem has been fixed. Clients |Select | Audit Log folder Clients |Select | Department folder When the user changed the Department status from Active to any other status, and then viewed the edit log file that was generated, the date ‘12/30/1899’ was displayed in the Removed Value section. This problem has been fixed. Clients | Select | Order/Episode folder When the user added an Episode/Order, and then changed the start or end date, multiple entries were generated in the Client Audit Log file. This problem has been fixed. 21954 21978 21916 22218 22343 22296 21668 21670 119 of 155 45 Order Service Plan changes Clients |Select | Orders folder | Service Plan This update fixes the following issues with the Service Plan: 21678 When a service plan record is edited, we will change the Units from ‘other values’ to ‘PRN’. 46 47 Errors Service Plan Conflict Duplicate Dated Notes generated when editing Order/Episode Start Date & Automatic Dated Notes on Status We now include the text ‘Over 1 Visit’ in the description, (e.g., 2 Hours Over 1 Visit Per Week for 6 Weeks), when the Units has a value <> PRN, (e.g., Hours over 1 visit Per Week). We now include the text ‘2 PRN Hours over 1 Visit’ in the description when the Units has a value = PRN, (i.e., 2 Hours over 1 PRN visit). We have changed the default for the Expire/Discharge date to that of the Effective date. If the user did not physically re-select the date, and then save, the date was not being saved. So we now retain the current date in the field and save it when the user saves the record. Scheduling | Client/Employee Schedules Monthly service plans, which had effective dates that did not start on the 1st of the month, were generating conflicts incorrectly in the months that followed. This problem has been fixed. Service Plan conflict checking was looking at a service plan in the future, rather than the one that was currently in effect. So it was factoring in visits that were not billable. Clients/Employees | Select | Order/Episodes folder Maintenance | General Setup | Department Module | Edit | Status tab We have fixed the following issues by updating Status Generation to create a Dated Note even if visits are not affected. This will occur for both Schedulable and Non-Schedulable client, employee and order status changes: 48 Dated Note - spell check not working 49 Care Connection, Display Filter Options 50 Client Intake: Can assign contact without contact type Procura 7- User Release Notes 21848 21864 & 21835 Duplicate Dated Notes were being generated when the user edited the Order/Episode start date When Dated Note types were attached to all clients statuses, they were only generating for statuses that are non-schedulable Clients | Select | Dated Notes folder When typographical errors in the body of a Dated Note were corrected by running spell-check, they were reverting back to their original spelling when the spell-check was completed. This problem has been fixed. Clients/Employees | Care/Employee Connection | Display | Filter Options The sort order of the filters was not being saved. This problem has been fixed. The Filters Setup form now saves the sort order of the filters to the registry. Clients | Intake When switching between formal and informal contact types via the Client Intake form, the Contact Type drop-down box was being cleared automatically. This allowed the user to assign a contact to a new client, without selecting a contact type for that contact. This problem has been fixed. The Add button will now be disabled if the user leaves the Contact Types drop-down box empty. 21924 & 21691 21557 22550 120 of 155 51 52 Find Directions MapQuest bugs out on country code CANADA Default Visit History Archived 53 Find Directions Links Client Information | Address 54 Error typing full date in to order form 55 Windows 2008 - 64bit - adding order 56 Mobile phone number does not print in client profile report 57 Incorrect syntax near 'F' - client intake 58 Episode Recertify button - allowing duplicate episode dates - same payer source Procura 7- User Release Notes Clients | Select Addresses folder When clicking the Find Directions link in Clients Addresses, the MapQuest program would sometimes attempt to look for the client’s address in the United Kingdom, even when using the country code for Canada. This problem has been fixed. Now, if both the client and system country codes are changed to ‘CA’ through the Maintenance system options, MapQuest will correctly identify the location. Clients | Select | Visit History folder Employees | Employee Information | Visit History folder When a Visit History note was created in the client's record, and then it was deleted and another one was created, the Archived box was filled with invalid data. This issue has been corrected so that, when adding new visit history to a client or employee, the Archived box will now default to unchecked. Clients | Select | Addresses folder When the client’s current address was not the same as their permanent address, clicking the Find Directions link for the permanent address would look up the current address, and vice-versa. This update fixes this problem. Clients | Select | Episodes | Add When entering a new order or episode for a client, if a complete date using the year 2010 was typed directly into the Start Date field, an error message was displayed. This update resolves this problem. Clients | Select| Orders folder When the user was running Procura in a 64-bit environment, an error was generated when they added an order or episode. This update resolves the issue. Reports | Clients | Client Profile Report If the client had both a Home and Mobile phone number listed, both numbers would print on the Client Profile report if the Print Phone No. option was selected. However, if they only had a mobile number listed, it was being omitted from the report. This problem has been fixed. Clients | Intake | Find Clients | Intake When the user added a contact via the Client Intake form, an error was displayed when they clicked Add. We have fixed this problem. Clients | Select | Episodes folder | Recertify Procura was allowing a duplicate Medicare episode to be created when the Recertify button was clicked. So, if the user highlighted the wrong episode in the episode list, the Recertify button would create a new episode based on the dates in the episode they had highlighted. This update corrects the problem. When recertifying, the new episode dates will now be validated against the client’s existing episodes. 21621 22461 21849 21692 21560 22232 22400 21898 & 22370 121 of 155 59 Episode service plan duration exceeding episode end date 60 Client Intake - click OK after select dept causes freezing 61 Diagnosis Lookup causing database error on client intake 62 Physician/pharmacy cannot be removed 63 CRM from Customer form 64 CRM - Error received when viewing Organization contact Procura 7- User Release Notes Clients | Select | Orders/Episodes folder | Service Plans When the user entered a service plan for a Medicare patient in a client episode, Procura did not allow for a duration that terminated after the end date for that episode. An error was generated to force the user to enter a shorter duration for the service plan. This problem has been fixed. A warning message will now be displayed if the service plan exceeds the order/episode end date. The user will need to confirm that they want to save the service plan with the selected expiry date. Note that this update does not correct Auto Service Plans. Episode service plans that were generated from Auto Service Plans will have their expiry dates updated to equal the episode stop date if the expiry date is greater than the stop date. Clients | Intake | Intake | Intake This update fixes an issue where the Client Intake form froze when the user selected the client's department, and then clicked the OK button to automatically add them to that department. Note that, after clicking OK, the user will still be required to add an order/episode in order for some configurations to finalize the intake process. However, they will be prompted with a warning. Clients | Intake If the user clicked the Lookup icon on the Client Intake form in order to perform a search, the search options performed correctly. However, if they chose a diagnosis or procedure from the list, clicking OK would result in a database error. This issue has been corrected. The diagnosis table will now be opened correctly when the user uses the Lookup icon to select a diagnosis. Clients | Select | Medications/Drugs folder On the Medications/Drugs folder on the Client Information form, if the user edited the Physician and Pharmacy fields, they were then unable to remove them. Selecting the Delete option from the rightclick shortcut menu or pressing the Delete key on the keyboard did not remove the entry. This problem has been fixed. Management | CRM In the Customer Relationship Manager (CRM), if the user changed the selection filter or pressed F5 to refresh the list of contacts, those editing features that were supposed to be disabled would be reenabled. This permitted the user to use those editing features when they should not have been able to. This problem has been fixed. Editing will now be disabled whenever this situation occurs. When a contact is added from the Contacts folder in the Client Information form, an option to select that contact from the CRM is now presented to the user. This option opens the CRM in such a way that the user will only be allowed to select a contact. All editing will be disabled in order to prevent possible data corruption. Note that adding, editing or deleting of contacts in the CRM will still be allowed when it is opened from the Management menu. Management | CRM | Organization Information If the user added or edited an Organization or Organizational Contact in the Customer Relationship Manager (CRM), an error was generated. This issue has been corrected. 21570 21580 22557 22230 22110 21922 122 of 155 65 CRM - Filter for Tasks not working 66 Operational Dashboard - SQL Error on import Dashboard Hour Display 67 68 Employee Application folder Theme Issue 69 GP Export - System Reference for OT calc includes all records Cannot terminate employee without planner 70 71 72 After employee intake - Birth Month/Day fields are not populated ADP Payroll Export Interface 73 When using export in 6.2 - generates Access violation 74 Export does not detect first DVA claim 75 DVA Export Requirement 5.5 Item codes report staff service Procura 7- User Release Notes Management | CRM If the user attempted to filter the tasks within a specific date range in the Customer Relationship Manager (CRM), all contacts would be filtered out. This problem has been fixed. The filters for tasks will now filter all contacts to which workflow tasks are attached, but only if the notify dates fall within the specified date range. This update fixes SQL Server errors that were being caused by a compatibility issue between SQL2000 and SQL2005 during the import of data for the Operational Dashboard. Reports | Dashboards This update fixes a problem where hours were not being displayed on a Dashboard, neither in the bar graph nor when the user drilled down through the Dashboard. Employees | Select | Applications folder This update fixes a display issue where, when some Windows themes were active, the Reference Dates grid on the Applications folder in the Employee Information form displayed differently from other grids. Imports/Exports | Payroll | Great Plains Payroll Export This update fixes the overtime calculation rule, which was being mistakenly applied to all pay codes when only O/T, OT or D pay codes should have had the rule applied. Employees | Departments folder | Change Status We have corrected a problem that was forcing the user to select a planner if they terminated an employee when that employee did not have any visits that were affected by that status change. Employees | Intake This update fixes an issue where the Birth Month and Birth Day fields on the Employee Intake form were not being populated. Imports/Exports | Payroll | ADP Payroll Export We have fixed an issue with the ADP Payroll Export where the Export button became disabled after the user ran the Validation. Imports/Exports | Payroll | Ceridian Tri-Data Payroll Export When the Ceridian Tri-Data Payroll Export was started, it stopped with an Access Violation error and no records were exported. This issue has been corrected. Imports/Exports | Billing | DVA CNMDS Export When there was only one claim validated for the export and the Claim From date did not precede the range start date that was entered by the user, the claim was not being counted as a valid claim. So a message was being generated. This issue has been corrected. Imports/Exports | Billing | DVA CNMDS Export When the DVA CNMDS Export was run, several of the item codes were reporting staffing resources and ADL question values, even though these item codes do not require them to report this information. We have fixed this problem. The export will now only report staffing resources and ADL question values for non-event type item codes, (i.e., Travel, Wound Care, Assessment, Bereavement or Palliative will be excluded). 22418 21925 21965 21552 22248 22233 21587 21866 21750 22283 22223 123 of 155 76 DVA Export Short Admissions – Reporting Wrong Admission Date 77 DVA Export-Item codes paired with specific claim validation 78 Requirement /CR 168 Palliative Logic 79 DVA Bereavement Visits Error Logic (No Staff Service) 80 DVA Palliative visit Date Claim From Issue Imports/Exports | Billing | DVA CNMDS Export When running the DVA CNMDS export, if there was a client who had been admitted and discharged within a single period, the export would report the Discharge date as the Admission date. This problem has been corrected. The Admission date should only populate when the export detects that the client was never admitted before the export was run. Therefore, the Admission date will now only be reported on the first claim for the episode. Imports/Exports | Billing | DVA CNMDS Export In regards to the DVA CNMDS Export, it is mandatory that all claims have at least one valid staffing resource visit for the exported period, regardless of the item code. This problem has been fixed. If a client does not have valid staffing resources for period/claims, all item codes should report as having failed the staffing resource stipulation. Therefore, item codes NT51, NT55, NT56, NT57, NT58, NT59, NT60, NT61, NT62, NO63, NA01, NB01, NB10 are now validated accordingly. Imports/Exports | Billing | DVA CNMDS Export When the DVA CNMDS export was run for Palliative (NT51) claim fee visits, it was not recording the correct claim date. We have fixed this problem. It will now record the claim date for the previous regular claim fee visits. If the previous claim fee visit is not found, the Palliative (NT51) claim fee visit date will be used instead. Imports/Exports | Billing | DVA CNMDS Export If a solitary Palliative (NT51) claim fee visit is exported using the DVA CNMDS export, staffing resources are required to export this claim. But, previously, claims that did not have staffing resource were not being omitted from the export results when they should have been, and no error was displayed. This problem has been fixed. If no staffing resources are found, an error will now be reported in the validation report. If the Palliative (NT51) claim fee visit is exported with another claim fee visit that is not of the Bereavement type, the staffing resources will be applied to the other claim and the Palliative (NT51) claim will be exported with no staffing resources. Imports/Exports | Billing | DVA CNMDS Export When the DVA CNMDS Export was run, one-time Palliative Visits (NT51) were being reported in the next concurrent claim, apart from standard, deceased, discharge claims and bereavement visits. They were reported as not having any hours or visits (staffing service) and they were being omitted from the export. 22229 22401 21539 21541 21542 This problem has been fixed. The claim date of Palliative Visits (NT51) will now be derived from the claim date of the previous claim. If a previous claim is not found, the Palliative Visits (NT51) claim fee date will be used. Procura 7- User Release Notes 124 of 155 81 DVA Break in Care logic issue (Proaus6.1.1.8) 82 DVA--Requirement 9.4.2 Error No DVA CN Found 83 DVA-Bereavement claim validates next 28 period for staff resource 84 HACC 2.0 SLK Logic Error 85 VON SAP Payroll Attendance type name, pay description, not being exported Procura 7- User Release Notes Imports/Exports | Billing | DVA CNMDS Export The DVA CNMDS export was only including assessments that were dated on or before the Claim Fee From date. This excluded assessments that were marked as In-Progress and that were dated within the reporting period. This problem has been fixed. The export will now include all In-Progress assessments for a claim visit that occurs within the ‘Claims ending Date Range’. If the option ‘Include In-Progress Assessments’ is not checked, these assessments will now be reported in the validation report for the current claiming period. Note that Break in Care assessments will be reported in columns 15/O and 16/P on the CNMDS form. If it is established that Break in Care start and stop dates should not be reported, the Break in Care type (1, 2 or 3) will not be reported either. Furthermore, when a PASE assessment Discharge or Death is selected, a claim fee visit(s) will be generated on the date of death/discharge (DVA-R-006B). See also enhancement 21540. Imports/Exports | Billing | DVA CNMDS Export When the DVA CNMDS Export was run, clients who had billed staffing visits, but who did not have any claim fee visits for DVA funders, were not being validated and reported in the validation report. This problem has been fixed. The report will now contain an error, which will notify the user that they are attempting to export a client who has verified, DVA funded, staffing service visits, but who does not have an associated PASE assessment or claim fee markers. Imports/Exports | Billing | DVA CNMDS Export This update fixes a problem with the DVA CNMDS Export where, if bereavement claims occurred within one day of the next logical claim date, they were either skipped or they were reported in the wrong period. In addition, due to the staffing resource validation requirement, this NB01 claim was not being allowed through to the export. This problem has been fixed. Item codes of NB01 (bereavement claim) will no longer be validated for staff resources. Imports/Exports | Billing | HACC Export When the question of Carer Availability was answered with a 3, 98 or 99, the SLK field was not being preceded by a space. This problem has been fixed. Now, whenever that question is not answered with a 1 (Has a Carer) in the ONI assessment, the corresponding client data in the export file will contain the following: Column Q (item 24) will be filled with a value of 2 Column R will be blank Column L will have a value of 1 Imports/Exports | Payroll | SAP Payroll Export When the user selected ‘Attendance Types Only’ on the VON SAP Payroll Export form, the pay description was exported, instead of the attendance type (clients.lastname) or expense description. This problem has been fixed. If the user selects ‘Attendance Types Only’, clients.lastname will be transmitted by the export. If they select ‘Expense Record’, the expense description will be transmitted instead. 21543 & 21549 & 21565 & 22359 21544 22477 22731 22711 125 of 155 86 VON SAP Payroll Export path is not saved 87 VON SAP AR Export Remove Client ID from report Change request 88 Rejections on CAHPS manual upload for SHP 89 HH-CAHPS - SHP Export Format Corrections Imports/Exports | Payroll | SAP Payroll Export The VON SAP Payroll export path that was defined by the user was not being saved. The user was being forced to redefine the path each time they ran the export. This problem has been fixed. When the user selects a path to which to save the file, the next time they run the export, that path will now be stored and subsequently displayed in future runs of the export. Imports/Exports | Payroll | SAP Payroll Export There is no need for a Client Reference number to be specified on the VON SAP Payroll export form. Therefore, we have removed the Client Reference selection from the form. The client's order Accounts Receivable number will be displayed on the report. Imports/Exports | Exports | HH-CAHPS Export For the HH-CAHPS Export, the Date of Birth format has been updated to MM/DD/YYYY and the following four questions have been updated to report zero (0) for a no answer: DuallyEligibleForMedicareAndMedicaid CareRelatedToSurgicalDischarge EndStageRenalDisease HMOIndicator Imports/Exports | Exports | HH-CAHPS Export The following corrections have been made to the SHP file format in which the HH-CAHPS formats exported data: 22712 22716 22284 22478 90 91 92 HH-CAHPS - Export Filename Misspelled CAHPS export file name HH-CAHPS Export Label missing & OCS file naming CCN duplication Rename column 7 to 'LastName' Enclose Social Security Number and zip code values in quotation marks, and insert zeroes in front of the numbers Only export the first 5 digits of the zip code Default the TypeofSampling to 2 Imports/Exports | Exports | HH-CAHPS Export We have fixed a problem where the HH-CAHPS Export file name was misspelled. Imports/Exports | Exports | HHCAHPS Export This update resolves a problem where the name of the HHCAHPS export file was missing the letter ‘H’. Imports/Exports | Exports | HH-CAHPS Export The following issues have been resolved with the HH-CAHPS Export: Procura 7- User Release Notes 22468 22513 22231 Label for Lookback Period was missing ‘Months’ The CCN was being duplicated in the OCS output file The CCN that was exported to the OCS/DSS output file did not always match the CCN number in the file 126 of 155 93 RFA 3 and 5 not including 0023 line for first visit on RAP & ANSI 837 - exporting 3 LX 0023 lines 94 HL7 Outbound Client activities being sent with Visits 95 HL7 Outbound Wrong trusted partner options used for client care plan file 96 HL7 Outbound - only transmit current status is still sending old statuses GP Pay Export - not calculating OT correctly 97 98 SEHC ADP Attendance Types 99 SEHC ADP Payroll Export - Record Counter 100 Avanti Payroll Export - export Pay Code Reference Value incorrect 101 ACCPAC Payroll: Department Selection Grid 102 ANSI270 99+ patients ST & SE increment update see 21243 103 error Rapid Pay export I/O Procura 7- User Release Notes Imports/Exports | Billing | ANSI 837 Transmission We have updated the ANSI 837 Transmission so that OASIS RFA3 and RFA5 will now be included to generate Line 0023 in a claim. In addition, we have corrected an issue where multiple SV2*0023 segments were being exported when multiple OASIS records were entered for an Episode. The export will now only write one SV2*0023 segment based on the first OASIS that is either a Start of Care (01 RFA) or a Recertification/Follow Up (04 RFA). Imports/Exports | Exports | HL7 Transmission When there was a valid PASE document, the HL7 Transmission was exporting in visit files the care plan activities that were at the client level. We have fixed this problem. Care Plans at the client level are no longer being sent in visit transmission (SIU) messages for a CellTrak partner. Imports/Exports | Exports | HL7 Transmission This corrects an issue with the HL7 Transmission where the ORM/OBX segments that display care plan activities were being combined into one file for those clients who were registered in different departments. Imports/Exports | Exports | HL7 Transmission This resolves an issue with the HL7 Transmission where future-dated status changes were being exported instead of the current department status. Imports/Exports | Payroll | Great Plains Payroll Export This resolves an issue with the Great Plains Payroll Export where Overtime Expense records were not being matched to the visit correctly. Imports/Exports | Payroll | SEHC Payroll Export When an attendance type was not marked for Transfer to Payroll, it was being exported by the SEHC Payroll Export when it should not have been. This problem has been fixed. Attendance Types will now be exported only if they are marked for Transfer to Payroll. Imports/Exports | Payroll | SEHC Payroll Export This update fixes a problem with the number of marked records that were being displayed in the summary report when the SEHC Payroll Export was run. Imports/Exports | Payroll| Avanti Payroll Export The Avanti Payroll export was not writing the Reference Value of the Pay Code. It was writing the Pay Code Description value instead. This update corrects the value that is being exported. The export now writes Pay Code: Reference Value instead of Pay Code: Description. Imports/Exports | Payroll | ACCPAC Payroll This update fixes a problem where the Department Selection grid in the ACCPAC Payroll export was only 1 line, instead of 3 lines. Imports/Exports | Billing | ANSI 270 Transmission When ANSI 270 files were at their maximum of 99 patients, an additional file was being created by the ANSI 270 Transmission, which was not incrementing the ST and SE segments by 1. This problem has been fixed. When exporting multiple ANSI 270 files, the ST and SE Segments will now be incremented. Imports/Exports | Payroll | Rapid Pay Export This update resolves an I/O Error 32 error that was being produced when the user ran the Rapid Pay export. 22331 & 22286 21973 21896 21887 22397 21756 22020 22567 22520 22529 21581 127 of 155 104 CSTDA NMDS Export - negative values for blank answers 105 HL7 - outbound client directions appearing in ORM message 106 HL7 Care Plan Message sent with incorrect comments 107 HL7 transmitting archived task details 108 CMIPS II export change format of 2 hours fields 109 HOBIC - PID-4 missing some data 110 HOBIC - OBX-11 segment missing S 111 HOBIC - Only the primary informal contact should be printed 112 HOBIC - PID-15 missing value when primary language not selected. Procura 7- User Release Notes Imports/Exports | Billing | CSTDA NMDS Export This update resolves a problem with the CSTDA NMDS Export where, if a PASE question was not answered by the user, the export was transmitting negative values in the columns that correspond to it. Imports/Exports | Exports | HL7 Transmission This update resolves a problem with the HL7 Transmission where client directions were being displayed in an ORM message, (i.e. a message that contains care plan information). Imports/Exports | Exports | HL7 Transmission This update resolves a problem with the HL7 Transmission where a one-time visit was transmitted to the Celltrak Portal, but the Comments field of the message that was being generated contained information that was not associated with the care plan for the client. Imports/Exports | Exports | HL7 Transmission This fixes an issue with the HL7 Transmission where the detailed description of a care plan activity was being replaced with the contents of an activity that had been archived. It also adds the following new switches to the trusted partner: /ALLOW_CLIENT_CAREPLAN and /ALLOW_CAREPLAN_DESCRIPTION. These switches allow the transmission of non-archived care plan activities, without the requirement of a new PASE assessment. Imports/Exports | Billing | CMIPS Export This update fixes a problem with the CMIPS II Billing export where the value in the Recipient Authorized Hours and Recipient Billed Hours fields was being formatted as a decimal. The format of these fields has now been changed to HHHMM, (e.g., 30.5 hours is now represented as 03030). Imports/Exports | Exports | HOBIC Export When the HOBIC Export was run, the value that was being displayed in PID-4.1 was the Health Care Number (HCN) client reference number. If this client reference number is missing or is empty, the export should generate 10 zeroes plus ^UNK. Therefore, this value should have been appended with the province code that issued the number, (e.g., ^CA-ON). This problem has been fixed. Imports/Exports | Exports | HOBIC Export This update resolves an issue with the HOBIC Export where the OBX-11 segment was not displaying the value ‘S’ when it should have been. Imports/Exports | Exports | HOBIC Export This update resolves a problem with the HOBIC Export where, if the client had multiple informal contacts, a number of NK1 segments were being created. Only the primary informal contact should be printed. Imports/Exports | Exports | HOBIC Export This update resolves a problem with the HOBIC Export where PID-15 did not contain the primary language of the client in the ISO639-2 format. UNK was missing for clients who did not have a primary language or for whom no languages were selected. For clients who do not have a primary language, UNK will now be displayed. 22318 21712 21984 21934 22131 21911 21919 21920 21915 128 of 155 113 Running ANSI 837 Export produces error 114 Status Processing Generating Log File to Procura Temp Folder 115 Dated Notes - Body text not sent when using Plain Text 116 Check for updates not placing release notes in proper folder 117 Spelling error - User environment options 118 SP9 error with dated note creation on status change 119 Spelling mistake on CIS referral 120 Prompt user message not displaying correctly 121 General - clipping in department reference numbers 122 HL7 - Error checking on import 123 HL7 Passive Mode: PID-33 not being populated Procura 7- User Release Notes Imports/Exports | Billing | ANSI 837 Transmission This update fixes a problem with the ANSI 837 Transmission where, when the user checked the Show All box, and then they clicked Select All and checked the Specific Claims box, when they opened the Specific Claims form, an error was displayed. This was caused by over 20,000 billing periods that were being selected for display in the Billing Period grid. Now, only billing periods that contain ANSI 837 Invoices will be selected. This will greatly reduce the total number of billing periods to be processed. Maintenance | Processing | Statuses This update fixes a problem where Status Processing was generating a log file that should only be generated for test versions of Procura. The status processing log file will no longer be generated. User | Create Dated Note This update fixes a problem where, when a Dated Note was created in Plain Text mode, (i.e., Options, Send Email As, Plain Text), the body of the email was blank. Maintenance | Utilities | Update Procura Tables This update fixes a problem where, when the user selected Check for Updates, the release notices for service packs were being stored in the Updates folder instead of in the Applied folder. 21985 User | Environment Options | Spellchecker Options tab This update corrects the misspelling of the label ‘Grammar’ in the Environment Options window. The label is now correctly spelled. Clients | Select | Orders folder If the ‘Create Dated Note for Status Change’ option was enabled on the Status folder in the Departments Module and the start date of the order was then edited by the user, an error was being generated. This issue has been corrected. This update changes the misspelling of the word ‘Ignored’ on the CIS Referral form so that it is now correctly spelled. This update fixes a problem where the System, Group and User notification/message windows that can appear when a user logs in were not displaying the notification message correctly. Maintenance | General Setup | Departments | Edit | General folder | Default Reference Numbers | Edit This update fixes a problem where a screen label/field was being cut off or overwritten by another label/field when auto-generate was set for department reference numbers. 22273 Imports/Exports | Imports| HL7 Import If the user did not specify the option -stfid on the inbound trusted partner, the HL7 import process generated an error for every import. However, the process would complete properly using the Procura EMPID that was supplied in the import file. This problem has been fixed. Imports/Exports | Exports | HL7Transmission This update fixes a problem with the HL7 Passive Mode where the PID-33 element was not being populated with the client change date. 22479 21583 21572 21767 21936 22363 22281 22498 22582 129 of 155 124 HL7 Passive Mode PID-7 should not include time 125 HL7 - Line Breaks parsed from Hazard Comments 126 HL7 - Care Plan Activities - visit care plan activities can be out of order 127 HL7 /ALLOW_MULTI_CLTDEPT for Attendance Types 128 HL7 Inbound Restrict unscheduled attendance types (SEHC-64) 129 HL7 Inbound - only one dated note created per day 130 HL7 Outbound attendance type ADT message PID-2, PID-3 131 HL7 - Employee Transmit Button transmits Attendance Types 132 HL7 - Client or Employee Transmit buttons use session instead of DB time Procura 7- User Release Notes Imports/Exports | Exports | HL7 Transmission This update fixes a problem with the HL7 Passive Mode where the Date of Birth field was also displaying the time. The Date of Birth field is now formatted as YYYYMMDD. Imports/Exports | Exports | HL7 Transmission This update fixes a problem with the HL7 Transmission where line breaks in the Comments field of the Physical Environment folder in the Client Information form were being parsed into ADT messages. Line breaks will now be removed from the Comments area. Imports/Exports | Exports | HL7 Transmission The Care Plan activities that were being exported in the visits transmission (SIU) were being transmitted in whatever order the SQL Server determined would be most efficient. However, the activities should be written in a consistent order. Therefore, this problem has been fixed. We now ensure that there is consistent ordering of the OBX segments. 22583 HL7 Normally, Attendance Types are transmitted with only the Celltrak location in the PV1 segment. However, previously, if the switch /allow_multi_cltdept was used in the Attendance Type trusted partner, the PV1 segment was using DEPT_ID^DEPT_NAME. This problem has been fixed. Imports | Exports | Imports | HL7 Import This updates fixes a change request to restrict attendance types by pay level. 22236 Imports | Exports | Imports | HL7 Import This update fixes a problem with the HL7 import where a dated note was not being created if there was already a dated note in existence that contained the same subject line on that day. Now, when the switch /allow_detailed_visit_noteis enabled, a dated note can be created for every visit, even if there are multiple visits on the same day. Imports | Exports | Exports | HL7 Transmission We have updated the HL7 Transmission so that, when the user exports attendance types to Celltrak as clients with ADT messages using the /allow_only_att_types switch, the 5-digit department CVID is put into PID-2 and the client_id is put into PUD-3. Imports/Exports | Exports | HL7 Transmission When there were both Attendance Type and Employee transmissions enabled for a particular department, and the user clicked the Transmit button on the Employee Information form, the HL7 Transmission would transmit Attendance Types when it should not have. This problem has been fixed. Attendance types are no longer exported when the Transmit button is clicked. 22117 HL7 When using the Transmit button on either the Client or Employee Information forms, the system log entries would use the local PC time, instead of the server time. For example, if the user was connected to a database that was served in Eastern Standard Time (EST), any system log entries that were generated from that database would be logged using the time on the client’s PC, rather than the local server time. This problem has been fixed. 22107 22648 22659 22040 22118 22106 130 of 155 133 HL7 - outbound. /allow_only_att_types location output is incorrect 134 Cannot select existing order to update 135 HL7 - Unscheduled Attendance type visits created when they should not be. 136 HL7 - Passive Mode PID Identifier Other is not being parsed. 137 HL7 - Passive Mode if address options are not used don't print them. Imports/Exports | Exports | HL7 Transmission This update fixes a problem with the HL7 Transmission where an extra element was being inserted after element two in the PV1 segment. Clients | CIS Inbox When the user chose an existing order, the system would change back to ‘new order’. This issue has been corrected. HL7 This update fixes a problem with HL7. When the user used the HL7 Trusted Partner option ATTENDANCETYPE_PAYLEVEL, attendance type visits that did not match the trusted partner setup were still creating records in the table Edccalls. In addition, when processed using Callme! batch processing, attendance type visits were still being created in Timekeeping. Imports/Exports | Exports | HL7 Transmission This update fixes a problem with HL7 Passive Mode. When using the trusted partner option PID_Identifier_other the value of the client reference number that is used is found and is matched to the lookup table. However, the output was not being parsed; only the value of the Description field of the lookup was output. The output should be the value of the client reference number after the 2digit provincial identifier and followed by the parsed lookup table information, (e.g., 123456789^^^CANBC^JHN^). This problem has been fixed. Imports/Exports | Exports | HL7 Transmission With the trusted partner options /allow_current_address and /allow_permanent_address were being used, the following problems were encountered with the HL7 Passive Mode. These problems have been fixed: 22078 22463 22057 22494 22496 The current address option displayed the current address twice when it was used alone. 138 HL7 - Passive Mode cannot transmit without Allow_client_validation 139 HL7 - Passive Mode The merge message does not need a 1 Procura 7- User Release Notes When neither option was used, the current address was still being printed, even though address information should not be printed without the option being enabled. There was an additional caret (^) character inserted between the phone number and the area code in the Home and Work phone numbers fields. Imports/Exports | Exports | HL7 Transmission This update fixes problems with the HL7 Passive Mode. Although the trusted partner option /allow_client_validationis not required, clients who created an output file with an ADT^A08 message would stop doing so when this trusted partner option was removed. No file was created. In addition, if all PID identifier reference numbers contained empty values, a ADT^A08 file was still being created, even though the warning message ‘Cannot transmit Other Identifier for client’ was displayed. We will now ensure that transmitting HL7 information can still occur when this option is not used and that, when it is used, PID identifiers are checked for empty ‘strings’. Imports/Exports | Exports | HL7 Transmission This update fixes a problem with the HL7 Passive Mode where the ‘merge’ message had a 1 in the second sequence when it should have contained the patient identifier for the deleted client. The 1 is now removed and the data that follows it will be moved into that location. 22497 22499 131 of 155 140 HL7 Passive mode AO1 seen when AO8 is expected. 141 F1 creates an error 142 Department start date not populated by CIS Inbox 143 Procura invoice and ANSI Overwriting in invoice run 144 Combo Invoice Spelling Mistake 145 Delphi 2009 SetTabPrintTab - Invoices 146 Invoice Summary Report 147 HCFA 1500 Red Preprinted Form -Setup Not Working 148 Clients without Departments Utility 149 Database error when trying to delete default department Procura 7- User Release Notes Imports/Exports | Exports | HL7 Transmission This update fixes a problem with the HL7 Passive Mode where, when non-department client information was changed, a ADT^A01 was displayed in the MSH segment. What should have been displayed was AO8. This problem has been fixed. The AO1 value should only be output when the client department status has changed. Therefore, we will now ensure that the output HL7 file contains the appropriate value F1/Help | Help Topics The first time the user pressed F1, the Help menu would open, but the second time it was pressed, an error was produced. When using most 64-bit Windows 7 and Vista systems, as well as on a few 32-bit Windows XP systems, pressing the F1 key or selecting Help from the Main Menu resulted in an error message. This update resolves the problem. Clients | CIS Inbox When a new client referral was processed through the CIS inbox, the initial department start date was left blank. On the Department folder of the Client Information form, the start date displayed as ‘12/30/1899’. This issue has been corrected. When there is no start date specified for the client department, the client department start date will now default to today’s date. Billing | Invoices This update corrects an issue where, if a Procura invoice format and an ANSI invoice format were being used together in the same invoice period, the last Procura invoice and the first ANSI invoice would be printed on the same page. This update resolves an issue where the word ‘Business’ was misspelled on the Combo Statement Invoice. Billing | Invoices This update fixes an issue where lines and other information were not printing correctly in the Custom Professional Services invoice or in the Custom Professional Services Generic invoice. This update corrects an issue where the total in the Invoice Summary Report was being cut off depending on the length of the report. 22578 Billing | Invoices When the user performed ‘billing’ using HCFA 1500 red pre-printed forms, the funder displayed a ‘1’ in Place of Service (box 24b), instead of a '12' (Home Care). This update has fixed this issue. When invoices are printed using the red preformatted CMS 1500 form and the Funder Agency Reference Label (FARL) BillCodeOption contains a value of ‘1’, data for the Place of Service will now print correctly. Maintenance | Utilities | Clients without Departments Utility This update fixes a problem where the Clients without Departments form was missing some verbiage when it was printed. The size of this form has now been increased. Maintenance | System Options | Options tab When the user attempted to delete the initial default department from the System Options, and then saved the change, an error occurred. This problem has been rectified. A message will now inform the user that a default department is required and the title of the field will be in bold print to indicate that this is a requirement. 22226 21627 22399 22224 22255 21556 22016 22089 22365 132 of 155 150 Departments: New Department & Department Taxes 151 CR - CallMe: Attendance Types 152 Additional Information Module Subcategories Label Name - Add blank 153 Delete Employee utility not bringing back expected results 154 MDS - Section G1 Re-implement Contact Lookup 155 Help option in MDSHC points to wrong folder & Double-click question title returns error 156 Med DB - Sort Results Alphabetically 157 MOW Add/Del Meal Package in Client Delivery Schedule 158 MOW Stat Holiday conflict checking not working properly 159 MOW Meal Labels Report not printing correctly Procura 7- User Release Notes Maintenance | Billing Setup | Billing Rates Module | Billing Records If the user created a new department when using department-level taxes in Procura, they were unable to assign those taxes to Billing Rates for that new department. The department tax information was not being properly displayed on billing records that were attached to the new billing table. This issue has been corrected. Department tax information is now displayed correctly on new billing records. When the user added a department to an Attendance Type in a database that uses CallMe!, an error would be displayed if they did not specify a CVID when they added the department. This would only occur if Procura was set to transmit any Attendance Type updates to CallMe! automatically. This problem has been rectified. We will only perform this check if a CVID is entered. Maintenance | General Setup |Additional Information Module | Sub Categories Form When a new subcategory was added with a blank label name, a database error was being displayed. This problem has been fixed. The label name is now a required field in the Additional Information Sub-Category. Maintenance | Utilities | Delete Employees The Delete Employee(s) form was listing employees who had a status of Transferred, instead of those who had a status of Terminated. This problem has been fixed. Clients | Select | MDS-HC folder The Primary and Secondary Last Name fields in MDS section G1 should have a drop-down box on the Informal Contacts table, even when the Informal Helpers are not linked to the client. We have resolved this issue. See also enhancement #22167. Clients | Select | MDS-HC folder When using the MDS-HC form, selecting Help from a drop-down box or by double-clicking a question caused errors to occur. This problem has been fixed. The MDS-HC form was not looking in the correct folder for the MDS help file. Clients | Select | Medications folder We have resolved an issue where the medication database was not sorting medications alphabetically by name. Meal Delivery | Client Deliveries When the user clicked a meal, and then they clicked the Add/Del button, the Name box contained the text ‘LabelName’. We have resolved this issue so that, in the Meal Packages for Delivery window, the Name box will be populated correctly. Meal Delivery | Delivery Routes Schedule When the user scheduled meal deliveries on a statutory holiday, conflict-checking was not being performed correctly. We have fixed this issue. The prompt to check statutory holidays for one-time meal deliveries has been removed. Statutory holiday checking will be performed when the user adds routes to Route Schedules. So statutory holidays for client meal deliveries will be controlled by an available route. Reports | Meal Delivery | Meal Labels Report The Meal Labels report provides the user with an 'option' to select either a specific district and/or route. But, previously, when the user selected these options, the labels were inserting all meals into all districts. This problem has been fixed. 22390 22424 22592 21831 22572 22530 & 22558 21877 22070 22074 22080 133 of 155 160 OASIS - Show M0140-M0150 as needed 161 OASIS - M1016-NA set on RFA09 162 OASIS C Question M2100 in .rep file 163 OASIS - episode end date is not saved properly 164 OASIS - View and copy previous answer brings invalid answers fwd 165 OASIS-M1730 print blank form missing PHQ2 scale RFA 1 and 3 166 RFA 9 M1500 - 'Go to Question' does not work 167 Dependent questions printing to 485 when not answered. 168 Custom question "hooks" not functioning - RFA03 / 04 Procura 7- User Release Notes Clients | Select | Oasis | Add | Show all RFAs Questions M0140 and M0150 were being hidden from some OASIS assessments. This problem has been fixed as follows: 21553 M0140 will be visible for RFA01 and RFA03 M0150 will be visible for all RFAs M0140-UK will be visible only for OASIS-B M0150-UK will be visible only for RFA01 and RFA03 Clients | Select | Oasis For RFA09 on the OASIS form, if the user set the M0090 date to ‘2009’ (OASIS-B), and then they selected Yes for M0200 and changed the M0090 date to ‘2010’ (OASIS-C), M1016-NA contained a value of zero (0) when it should have been blank. This problem has been fixed. Clients | Select | Oasis folder We have a fixed a typographical error in the word ‘patient’s’, which existed in section G of question M2100 when the blank report ‘Resumption of Care’ RFA 03 of OASIS-C was printed. Clients | Select | Oasis folder When the user added an OASIS to an on-going episode, and then they entered an end date to the Certification period, clicking the Complete button caused the date to be discarded. We have fixed this problem. The date will now be saved when the data in the OASIS form is refreshed upon completion. Clients | Select | Oasis folder When the answers for the Clinical Record (M0010–M069) and Medication (M2000–M2030) questions were copied from previous OASIS assessments, the answers to questions M0032, M2020 and M2030 were sometimes copied inappropriately for the RFA. This problem has been fixed. Clients | Select | OASIS folder | Print Reports |Clients | OASIS Report If the M1730 radio button question is answered on the OASIS, it expands to show a PHQ2 Scale for the user to fill in. However, previously, the PHQ2 Scale did not display when printing blank forms that require the selection of unanswered questions for printing. This problem has been fixed. The PHQ2 scale in M1730 will now display for a blank RFA 1 or RFA 3 form. Clients | Select | Oasis folder When the user attempted to go to questions M1500 and M1510 (cardiac status) on RFA 9 of the OASIS, the question was not being located. This was also true when using the ‘Go to Question’ button on the OASIS validation errors form. This has been corrected. Clients | Select | Episodes | Phys. Orders folder | Print The answers to PASE questions of the Notice type were always printing, even if they were dependent on a specific answer for a previous question that was not selected by the user. This update will print questions only when the specific answers are selected. Clients |Select | OASIS folder| Print Reports | Clients | OASIS Report This release corrects a situation where, when the user printed an OASIS assessment to which custom questions had been added, those questions would not appear in the OASIS report if they followed questions POC18A or POC20. 21561 21600 22307 22285 21648 21738 21646 21713 134 of 155 169 RFA 4, Recertification date rules are incorrect 170 OASIS Validation Error - Diagnosis code not valid Showing wrong question 171 RFA 6 and 9 cannot enter correct M0906 date 172 M0175 showing active on RFA 4 and 5 v62 173 OASIS being sent with incorrect HIPPS code 174 OASIS Validation Error on M0104 175 OASIS M2110 answer 1 does not print Procura 7- User Release Notes Clients | Select | Oasis folder In regards to OASIS, a validation message for RFA 4 occurred when the M0090 date was not within five days prior to the episode start. The validation rule was applied to both Medicare and Medicaid funders when it should only apply to Medicare funders. This problem has been fixed. The validation will no longer occur for Medicaid funders. See also enhancement #21861 Clients | Select | Oasis folder When invalid diagnosis codes were used in questions M1010, M1016, M1020, M1022 or M1024 of the OASIS, the validation error referred to OASIS-B question numbers M0190, M0210, M0230, M0240, M0246, when they should have referred to OASIS-C question numbers. This problem has been fixed. The correct numbers will now be shown for both OASIS-B and OASIS-C. Clients | Select | Oasis folder In regards to OASIS, the M0906 field has a maximum date restriction, which prevents the entry of dates that follow either the M0090 date or the current system date, whichever is earlier. On RFA 6, RFA 7 and RFA 8, the maximum M0906 date was not being updated when the M0090 date changed. Therefore, valid M0906 dates sometimes could not be entered. This problem has been fixed. The M0906 maximum date can now be changed when the M0090 date changes. In addition, a similar relationship exists between M0906 and M0903: On RFA 6, RFA 7 and RFA 9, M0903 must be less than or equal to M0090 or M0906, whichever is less. Changing M0090 or M0906 did not refresh the maximum M0903 date. So this update allows the M0903 maximum date to be changed when the M0090 date or M0906 date is changed. Clients | Select | Oasis folder This update fixes an issue where question M0175 was appearing on OASIS-B assessments (M0090 less than 10/01/2010) of type RFA 04 and 05 when it should not have been. OASIS-C assessments (M0090 greater than 10/01/2010) are not affected. Clients | Select | Oasis folder OASIS assessments with a M0090 date that is greater than 10/01/2009 and less than 01/01/2010 were being exported with a HIPPS code version of V2308, when it should have been V2409. This caused a submission warning message to occur. This problem has been fixed. The update sets the HIPPS version to V2409 for assessments with M0090 dates prior to 01/01/2010 (OASIS-B) and to V3110 for assessments dated 01/01/2010 or later (OASIS-C). Clients | Select | Oasis folder A new version of the OASIS Validator has been released. The new Validator implements the changes in the latest CMS OASIS-C data record errata (correction) documents. This update allows the new verifier DLLs to be loaded automatically. Clients | Select OASIS folder | Print Reports |Clients | OASIS Report This update fixes a problem where question M2110 on the SOC OASIS was not printing if it was answered with a 1. 21997 22013 21655 21575 21599 21689 21669 135 of 155 176 OASIS M1016 and M1020 Tabbing out of order 177 OASIS Gen Quest: not printing question body to blank form 178 Validation error M1620 'go to error' - 'M1620 not found' 179 HIPPS/HHRG codes remove from OASIS when moved to other episode 180 Add OASIS RFA 6, 7, 8 or 9 - bringing in diagnosis Errors 181 Validation error M0102 'go to error' - 'M0102 not found' 182 OASIS Rept. not printing questions after 18A 183 OASIS C - M2100 section D if answer is 5 - does not save 184 OASIS +7 Fatal file Invalid Record Length 185 OASIS M0102 date removing when saved NA then checked Procura 7- User Release Notes Clients | Select | Oasis folder This update fixes an issue where the fields for questions M1016 and M1020/M1024/Additional Diagnosis/Surgical Procedures were not in the correct tab order. For M1016, the tab order will now be a, b, c, d, e, f. For the M1020 series, it will be M1020, M1024-3, M1024-4, Additional Diagnosis, Surgical Procedures. Note that this is the same tab order that was in effect in Procura 6.1.0.0. Clients | Select | OASIS folder | Print Reports | Clients | OASIS Report If a custom OASIS included a PASE question of the Vital Signs answer type, the OASIS report did not display the vital sign column headings if the question was not answered. This update fixes this issue. Vital signs will now print in a columnar format. Clients | Select | Oasis folder This update fixes an issue where, when the user used the Go to Question on the main OASIS form or Go to Error in the validation form, Question M1620 was not found in the OASIS. This problem has been fixed. Clients | Select | Oasis folder If an OASIS assessment was moved from one episode to another, the HIPPS/HHRG was missing because certain elements were not being saved properly, (e.g., M0030 SOC date). The issue is corrected in this update. Clients | Select | Oasis folder When adding an OASIS with RFA 6, 7, 8 or 9, the diagnoses codes were sometimes being copied from the previous assessment. This was causing validation errors. This update fixes this issue. Clients | Select | Oasis folder If the user answered question M0102 by checking the NA checkbox on the OASIS form, an error was being displayed when they clicked ‘Go to Error’ in the Validation form or ‘Go to Question’ in the OASIS form. This problem has been fixed. Clients | Select | OASIS folder | Print Reports |Clients | OASIS Report This update fixes an issue with the OASIS Report where a question that was selected to display after POC 18a did not print at all. Clients | Select | Oasis folder For question M2100, if the 5 box was checked in section D of the OASIS form, the value was saved in the answer in section B, instead of in the answer in section D. This meant that the answer in section B was incorrect and the answer in section D was not saved. This problem has been fixed. Clients | Select | Oasis folder Imports/Exports | OASIS Export OASIS Inactivation records (record type X1) were being exported as 1440 characters, instead of the required 1448 characters. This was causing all records to be rejected. This update corrects the record length. Clients | Select | Oasis folder We have fixed an issue where the date that was entered into M0102 on the OASIS was being discarded after the user saved the OASIS. 21733 22019 21897 22180 21568 21880 21647 21714 21625 21879 136 of 155 186 OASIS-submitted HIPPs cannot have blank HIPPS version 187 OASIS - display issue when opening sent OASIS 188 OASIS Report: Query Error 189 OASIS Report - Some Sections do not print custom questions 190 DSS format of HHCAHPS contain invalid columns 191 OCS CAHPS export is formatted incorrectly 192 OASIS access & Clinical Day View 193 Medications are not being linked with the database 194 Second OASIS export file overwriting initial one 195 Help, About - DLL version numbers not shown 196 Inserted Objects not saving in dated notes Procura 7- User Release Notes Clients | Select | Oasis folder Imports/Exports | OASIS Export When OASIS records contained M0090 dates that preceded 01/01/2010 but followed 10/01/2009, the exported HIPPS version field was blank. This update fixes this issue. When opening a sent OASIS, the formatting was being broken up by the words that were in bold print. This problem has been fixed. Reports | Clients | OASIS Report When running the Oasis report for a specific set of report options, a query error was being generated. This problem has been fixed. Reports | Clients | OASIS Report On the OASIS report, custom questions that were attached to sections POC 15, POC 16 and POC 18A were not printing. This problem has been fixed. Imports/Exports | Exports | HH-CAHPS Export The Feeding ADL has been removed from the export. ADL Non Independent count range was 0-6. We have changed this so it is now 0-5. The default for ADL columns is now "M". Imports/Exports | Exports | HH-CAHPS Export This update fixes a problem where the HH-CAHPS export was using an incorrect version of the OCS file layout. It now uses the 1.2 version of the OCS file layout. Clients | Clinical Day View This update fixes an issue where, even if the user did not have the access right to open OASIS, they could still open it from Clinical Day View. Clients | Select| Meds folder | Medication/Drug Information When changing the client medication class from Custom to Standard, the Custom Procura Medication was not being cleared. This was causing the medication to be treated as a Custom Procura Medication when it was re-edited or viewed in OASIS. This issue has been corrected. Using the option for the Medication database, the drop-down box will now display the Brand Name, Description and Code with the brand name that is saved in the Drug Name field. Imports/Exports | Exports | OASIS Export If the user created an OASIS file, and then they named it the same as a previous OASIS file, no prompt was being displayed to tell them that the export and log files would be overwritten. This update has corrected the issue. If an export file name is entered manually and that file already exists, the user will now receive a confirmation message when the Export button is clicked. They will then be able to halt the export and change the file name. Help | About On the Help, About form, the version numbers for DLLs were blank on the Libraries tab. This update allows the version numbers to be displayed for DLL libraries. Clients/Employees | Select | Dated Notes folder This update corrects an issue with objects that were added to a Dated Note. When the note was saved, the object could not be opened. Although the object was being saved as a link, the file could only be opened from the user’s computer, where the dated note was saved. 21626 22059 22422 21675 22490 22571 21765 22453 21899 21622 21634 & 21748 137 of 155 197 Coloring for Capacity Manager 0 value 198 Capacity Manager Calls Received slowness / incorrect 199 HL7 Inbound mileage rounding change 200 201 202 6.2 Help dated note 6.1 image showing on CRM print out with Schedule address field directions popup not working properly 203 CRW - Legacy Invoice GST amount incorrect 204 Create multiple visits: Pay Service not transferred to visits 205 Image Compare duplicate image records are being selected 206 PASE Export/Import Images saved in 6.1 are corrupted in 6.2 Procura 7- User Release Notes Scheduling | Employee Scheduling Groups | View | Capacity Manager This update fixes an issue where the Capacity Manager was not highlighting At Capacity values of zero (0) in yellow as it should have been. Scheduling | Employee Scheduling Groups | View | Capacity Manager The query responsible for retrieving the number of received calls for the Capacity Manager was running very slowly, (i.e., at an average of 45-75 seconds per run). In addition, the totals were being calculated incorrectly and calls were being received for dates in the future. This problem has been fixed. See also enhancement #21744 Imports/Exports | Imports | HL7 Import When HL7 messages with mileage expenses were being imported into Procura, the mileage value was being rounded inconsistently. This problem has been rectified with a system reference, called Callme_Mileage_Rounding, which changes the handling of incoming mileage to assume 2 decimal places. It will also change the processing of the 'call' such that the mileage expense record that is created will also use 2 assumed decimal places. Help | About This update fixes a problem where the Procura 6.2 image was being displayed on the Help, About form. Management | CRM In the Customer Relationship Manager (CRM), if the user attached a dated note and then printed, the details of the dated note would print in the wrong font (or as ‘boxes’ if the font was not installed). This problem has been fixed. Scheduling | Client/Employee Schedule When the user moved their mouse overtop of the address on the Schedule in an effort to see the directions to the client's home, the popup tip would cause a problem where only the first line of new entries would then be displayed. This problem has been fixed. We have fixed an issue with the Legacy Invoice CRW report where part of the value in the GST field was being lost, (i.e., it would display as $9.24 instead of $59.24). Scheduling | Client Schedules When the user created multiple visits on the Client Schedule form, if they then selected a specific pay service type and saved the multiple visits, Procura would not save the pay service type to those visits. This problem has been fixed. Clients | Select | PASE folder | Compare In the Image Compare form in PASE, images were either displaying more than once in the thumbnail list for the client and/or they were displaying for a different client altogether. This problem has been fixed. Clients | Select | PASE folder This fixes an issue with PASE assessments that contained image questions for which a default image was supplied. When the assessments were exported from Procura 6.1, and then imported into Procura 6.2, the default image was being corrupted. 21859 21913 21716 21564 21777 21794 21644 21788 21703 21706 138 of 155 207 PASE-Radio Buttons combined with text field writes values 208 V6200 PASE Radio button with text, text does not save 209 DVA EXPORT Variation w/Discharge does not stop visit & DVA Variation Defect Discharge 210 Defect/CR 22272 Break In care logic (Hosp/Holiday/Rehab) 211 NA01 (assessment) creates 2 regular visits 212 DVA-Break in Care 213 DVA-Calculate Item Number & Generate Claim Fee Visits 214 PASE: Date Question 215 ONI - Dependencies not populating when edited 216 PASE - lookup type answers do not clear from form Procura 7- User Release Notes Clients | Select | PASE folder We have fixed a problem where, under certain circumstances, a PASE question had the wrong value stored. These circumstances required that one PASE question exist with the radio button type and one exist with a user text field type. Clients | Select | PASE folder If a PASE question was created with answers that were formatted as radio buttons and one of the choices required that the user enter text, the text that was entered was not saved. This problem has been fixed. Clients | Select | PASE folder When the user filled out a DVA CN PASE form for a regular item code and, in the item code pattern, they introduced both a variation and a discharge, the claim fee visit creation utility failed to stop the regular item code pattern. This problem has been fixed. When a Palliative Care Variation onetime claim fee visit is generated on Discharge/Death, all claim fee visits on or after the discharge/death date will now be deleted. Clients | Select | PASE folder On completion of a Discharge DVA PASE, the claim fee visit date of occurrence was being updated to the discharge date. This issue has been corrected. The date of occurrence will retain the original 28day cycle when a Discharge DVA PASE is completed. Clients | Select | PASE folder When a DVA assessment contained changes effective March 1, 2010 and the assessment date preceded that date, NA01 was being generated for both onetime and regular claim fee visits. This problem has been fixed. Only NA01 onetime visits will now be generated. Note that it is recommended that a DVA assessment, which has been updated for 2010 changes, be used only when the assessment date is on or after March 1, 2010. Clients | Select | PASE folder We have fixed an issue where Non-Discharge/Death DVA PASE Assessments that have Break in Care dates will no longer affect Claim Fee generation. Clients | Select | PASE folder This update enhances DVA Calculate Item Number and Generate Claim Fee Visits to support the new March 2010 (DVA CN) classification system and schedule. Clients | Select | PASE folder When the capability of resizing was added to the Date question type in PASE, the user was allowed to resize the selection box so that it extended the full width of the screen. This problem has been fixed. Clients |Select | PASE folder PASE assessments with a specific type of dependency were sometimes failing to display the dependent questions. The dependent questions should have displayed if a specific radio button was not selected. This problem has been fixed. Clients | Select | PASE folder On PASE assessments, pressing the Delete key when a value was selected from a Lookup type question did not clear the lookup field. This problem has been fixed. 21829 22079 22254 & 22383 22330 22360 22444 21902 22579 22311 21736 139 of 155 217 PASE - Client Supervisor Requirement form missing 218 ONI-CIARR Report typo in Question 11.1 219 PASE-on edit, no prompt to discard changes (using x) 220 Client Assessment Report - Print version unlike screen version of assessment 221 Visit notes not synching to server. 222 ONI Printed Form 223 Blue Care Printed From - Facility Name not required 224 Carer Availability Prints as 4 on ONI 225 Master Pay Records attached to Employee File Clients |Select | PASE folder This update corrects an issue where PASE assessments with specific supervisor information were not triggering the Client Supervisor Requirement form when the assessment was completed. Clients |Select | PASE folder This update fixes a typographical error in the ONI-CIARR Report, which is printed from a PASE document. The error existed in the text for question 11.1 ‘Are there any factors about this home that could affect safety…’ Clients |Select | PASE folder This update fixes a problem where, when a PASE assessment was added to a client record, and the user exited the form, the prompt to save was not being displayed. Therefore, the information was not being saved. Reports | Clients | Client Assessment Report This update fixes an issue with the Client Assessment Report where, when the user clicked the Print button, the layout of the assessment was not the same as it was when they simply opened it. Clients/Employees | Care/Employee Connection | Synchronize When the Scheduling Start Date is updated on the server or local database, the new/edited client visits or visit notes that precede the Scheduling Start Date were not being synchronized to the server. This issue has been corrected. Any visit or visit note, which has been edited or inserted, will no longer be validated to the scheduling start date and will now be synchronized. Reports| Clients | ONI Report Clients | PASE – Print When an enhancement was made to the Carer location, the Informal Contact field was affected, which disabled the ability to print both of these values. This problem has been fixed. The Carer information can now be printed from the Informal Contacts folder in the Client Information form. Reports| Clients | ONI Report Clients | PASE – Print When a change was made to the Printed From field on the ONI Report, it included populating the facility name in the header. This caused highlighted text to display in the Printed From field when it should not have. This problem has been fixed. The company name now prints in the Printed From field as it should. Report s| Clients | ONI Report Clients | PASE – Print This update resolves an issue where the answer to the Carer Availability question was being inserted as ‘4-Has a Carer’ instead of as ‘1-Has a Carer’. Maintenance | Employee Setup| Pay Table Module | Pay Table Maintenance | Pay Records The user added all the pay records available to each employee on the Employee Pay Information tab, and then changed a master record in the pay table. But the change was not reflected on the Employee Pay Information tab. 22312 22685 22675 21754 22349 22732 22631 22749 22442 This problem has been fixed. If Pay Records are updated (or if Record Types are added, edited or deleted), all employees will also be updated if employee specific Pay Records are attached as Master Records to those pay records. Procura 7- User Release Notes 140 of 155 226 OASIS Final Claim Est. PPS - adds PPS amounts of multiple OASIS 227 Client Aged -Not detailing actual transactions as in pay proc 228 Planner Report Header Does not sort by Planner 229 Visits created on laptop synch back as "invisible visits" 230 POC Console not processing check-ins automatically 231 POC installer - SQL Express 205 SP3 on XP Pro SP2 = Blue screen of Death! 232 POC Installer Database not attached in 6200 233 POC Installer – SQL Express 2005 sp2 install fails when msxml6 sp2 is installed 234 Staff Productivity Report CRW/ Total issues Procura 7- User Release Notes Billing | Billing Batches | Calculate Payment Processing | Client Billing Information | Re-Calculate This update fixes a problem where the invoice amount in Payment Processing was the total of all OASIS PPS amounts, instead of the PPS amount of the first OASIS (RFA 01 or 04). If a Medicare funder has the Final Calculation type for Invoice Format set to ‘Est. PPS Amount’ defined, (i.e., under Maintenance, Funders, Department, Billing), the billing calculation will now output to the Final claim the sum of the PPS amounts for all OASIS that exist in the episode. Reports | Billing | Client Aged Report The Client Aged report was missing items from the detail that was included in Payment Processing. Running the report for one patient displayed the detail items in the Transaction Type area. However, they were not being included in the detail line items. This problem has been fixed. Scheduling | Planners When the user clicked the Print button on the Planner, and then they selected All Planners, the resulting Planner Report displayed All Planners for all pages when it should have sorted them by the planner and separated them with page breaks. In addition, the Planner Report header should have indicated under which planner the records were included. This problem has been fixed. The report will now sort by the planner when selected and print the grid as sorted/grouped. In addition, selected planners that are chosen from the Planner filter will display the planner names correctly, instead of as ‘elected Planners’. Clients | Care Connections Visits that were created on Point of Care (POC) devices and synchronized to the server displayed in the Invisible Visits utility with the ‘Visits with Invalid TK Period Ids’ item selected. However, these visits were not displayed in the Timekeeping module. The employees were displayed as having unprocessed visits in Build Timekeeping, but they did not include visits when built. This problem has been fixed. When new visits are synchronized into the server database, they will now be attached to the appropriate Timekeeping period if one exists. The POCCONSOLE.EXE utility was not processing check-ins automatically. The user had to click the Enable Queue box, and then select the Synch All option in order to allow the pending check-ins to be processed. This problem has been fixed. When the Point of Care (POC) Installer was being run on a system that used the OS XP Pro SP2, but which did not have SQL Express or SQL Server installed, running the SQL Express SP3 installer caused a system crash. This problem has been fixed. When running the Procura 6200 POC installation, the database was not being attached and an error was displayed. This problem has been fixed. When the client attempted to upgrade MSXML to V6 SP2 and then used the Point of Care installer, SQL Express failed to install. This problem has been fixed by updating to the latest release of SQL Server Express. SQL Server Express uses MSXML, and is included and installed with the Point of Care installer. We have fixed a problem with the Staff Productivity CRW Report. Visits, which were scheduled to the Administration Time attendance type and with hours set to Indirect, were being included in the Indirect% column of this report when they should not have been. 22300 22241 21746 21592 21559 22031 22050 22051 22651 141 of 155 235 California Reporting – Counts are off The following changes have been made to the California Reporting CRW Report: 21937 & 21940 & 21942 1) 2) 236 237 238 239 240 241 California Reporting Count of unduplicated clients and visits CRW: Staff Productivity Detail Report Admin Time percentage incorrect. Billable Services CRW/Ver. 3 BC-CR140 Date of death logic backwards FNIH Invoice - Saving to RTF JBC HACC Tax Invoice CRW - Taxes are not displayed in report Tax Invoice for EACH Version 9 242 JBC-04- GST Summary Report Invoice #1314 hardcoded to report interface 243 Compliance CRW report - Clients with correct postal codes still displayed. 244 HACC Tax Invoice CRW - Fees column contains rounding errors 245 CRW-Co-payment report crashes when TC value other than "1" Procura 7- User Release Notes We have updated the report to sort patients in alphabetic order. We have updated the patient count for new counting requirements so that, if a patient is admitted, and then discharged and re-admitted within the same year, they will be counted twice. Note that the patient must have received one visit and their client record must have been flagged as ‘billable’. 3) We have changed the grouping of the Diagnosis as follows: Line 3 Malignant Neoplasims: Lung has been changed to 209.21 Line 7 Non-Malignant Neoplasims: All Sites has been changed to 209.40-209.79 This update fixes an issue with the California Reporting CRW Report where the default for the date range was changing to ‘2009’. 21949 This release corrects an issue with the Staff Productivity Detail CRW Report where the administration time percentage was displaying an incorrect value if only Admin Time attendance type visits were displayed. 22575 This update fixes a problem with the Billable Services CRW Report where, if the user recorded the date of death for a client, the report would only print visits that occurred after that date. They should have also printed those visits that occurred on or before that date. This update fixes a problem with the FNIH Invoice CRW Report where some of the service requirements were not being saved in RTF format correctly. This update fixes a problem with the JBC HACC Tax Invoice CRW Report where taxes were not being displayed in the client co-payment section of the report. 21589 This update fixes a problem with the Tax Invoice for Each CRW Report where, when the user selected a different department/funder combination, the tax invoice did not print the information that it should have. So the Bill To field was incorrect, the Employee field was missing from the report and the Client Visits were displaying bill amounts. This problem has been fixed. This update fixes a problem with the GST Summary CRW Report where, in versions 3 and 4 of the report, there was an invoice number (#1314) that was hard-coded to the report form and the invoice option did not automatically include all of the results as the default. This update corrects an issue with the Compliance CRW Report where clients from a specific department were being reported as not being in compliance. 21436 This update corrects an issue with the JBC HACC Tax Invoice CRW Report where the values in the Fees column were not rounding correctly. This was affecting the sum of the values displayed, as well as the sub-total. This update fixes an issue that occurred when the Copayment CRW report was run to extract visit data. If the report included visits in which a value other than Null or ‘1’ existed in the TC (Time Card) Column, the report would crash. 21782 21895 21774 21957 21930 22508 142 of 155 246 CRW: Callme! Exceptions by Client - calls within variance showing No Call 247 OASIS Report Not Printing Image Questions Correctly 248 Expense & Mileage Report Error 249 Client Service Summary Report Visit Total Options 250 Revenue Analysis report columns overlap 251 TK Detail Summary report not adding columns correctly 252 Funder coordinators from expired orders printing 253 Employee Schedule Report 254 255 Report MDS-HC Profile Labour Rule Exception Report not always displaying category Procura 7- User Release Notes This update fixes an issue where matched calls within variance were being displayed on the Client Exception CRW Report as ‘No Call’ when they should not have been. 22203 Reports | Clients | OASIS Report | Print This update corrects an issue in which the resulting report did not print embedded images when image-type OASIS questions were printed. Management | Fiscal Management | Timekeeping Expense & Mileage Report This update corrects an issue with the Expense & Mileage Report where data was overlapping on the report. Reports | Clients | Client Service Summary Report The following problems with the Client Service Summary Report have been fixed: 21571 21865 When billing tables were linked to departments, the Visit Total Options drop-down box was empty, (i.e., Service Types, Bill Types, Discipline Types, etc.), even though items of the type that was selected did exist, (i.e., Total By). The Grouping section for the Visit Total Options did not populate with a list, regardless of which options the user selected. When the user selected one or more departments on which to filter, there was nothing available to select from in the Visit Total Options. Therefore, the report did not display any totals. Fiscal Management | Revenue Analysis Report This update fixes an issue with the Revenue Analysis Report where funder codes that took up the full amount of space would overlap the name of the funder. Reports | Timekeeping | Timekeeping Detail/Summary Report If the user added the numbers in the Pay Duration and Bill Duration columns, neither column would produce the correct total when the Timekeeping Detail/Summary Report was run. This problem has been fixed. Reports | Clients | Client Profile Report This update resolves an issue with the Client Profile Report where Funder Coordinators who were associated with expired client orders were printing when they should not have been. Reports | Scheduling | Employee Schedule Report This update fixes an issue with the Employee Schedule Report where the visit comments were not being displayed if they were split between pages. Reports | Clients | MDS-HC Profile Report This update fixes an issue with the MDS-HC Profile report where, when printing a blank standard form, section J2 would not print unless the ‘Print Generic Questions’ box was checked off. Reports | Scheduling | Labor Rules Exception Report In the Labour Rules Exception Report, the categories under which certain employees belonged were not printing under Maximum Consecutive Days (MXDYWRK). This problem has been fixed. When the Labor Rules Exception report is printed, categories will now be printed for all employees. 21883& 22026 & 22058 22027 22028 21751 21731 22501 21718 143 of 155 256 CRW: Staff Productivity Detail Report - Case Conference type 257 CMS Cost Report Not printing NRS totals 258 CMS Cost Report Miss-type for Home Health Aide 259 CMS Cost Report Not printing Patient counts for service disciplines Title XVIII 260 CMS Cost Report Not printing counts for Other Part I Statistical Data 261 Status Drop-Down List not populated for report 262 263 TK Detail by Employee: Department Name Wrapping Service Reports: Report of 264 Employee Roster Report: Attend Types & Employee without Visits 265 Employee RosterField Masking & Justification Issues 266 Employee Roster Report: Summary Actual Supply Issue & Employee Not Avail showing Supply Total Procura 7- User Release Notes This release corrects an issue with the Staff Productivity Detail CRW report where visits, which were scheduled to the Case Conference attendance type and that contained hours that were set to Direct, were included in the report when they should not have been. Management | Client/Service Profiling | CMS Cost Report This update has fixed an issue with the CMS Cost Report where NRS totals were not printed in the correct column. Management | Client/Service Profiling | CMS Cost Report This update fixes an issue with the CMS Cost report where a typographical error occurred in the phrase ‘Home Health Aide’ under the Description. Management | Client/Service Profiling | CMS Cost Report This update fixes an issue with the CMS Cost where the patient count for each discipline was not being printed in Part I – Statistical Data. Management | Client/Service Profiling | CMS Cost Report This update fixes an issue with the CMS Cost report where visits of ‘Other Type’ did not include all payer sources. Visits of ‘Other Type’ will now include all payer sources, including Medicare. Reports | Statistical | Employee Reference Number Statistical Report This update fixes an issue with the Employee Reference Number Statistical Report where the Status drop-down box was empty when the report was run. Reports | Timekeeping | Timekeeping Detail by Employee Report This update fixes an issue with the Timekeeping Detail by Employee report where, if a department name was typed in capital letters, it overlapped the Date column when it printed in the Department Name column. Reports | Scheduling | Report of Service Report This update fixes an issue with the Report of Service report where the heading ‘Nurse Name,’ which is printed at the top of the report, was displaying the name of the first client on the page, instead of the name of the employee in question. Reports | Scheduling | Employee Roster Report In regards to the Employee Roster Report, if the ‘Include Attendance Type’ filter was used in conjunction with the ‘Include Employees Without Visits’ filter, only those employees with visits were included. This problem has been fixed. These two filters will not be exclusive; both will be allowed to function at the same time if they are both selected by the user. Reports | Scheduling | Employee Roster Report In the Employee Details bands of the Employee Roster Report, the Actual Supply, Total Demand, Availability Period and Daily totals were only printing to one decimal. This problem has been fixed. They will now display to two decimals. Reports | Scheduling | Employee Roster Report This update fixes problems with the Employee Roster Report where the labour rules were not being applied to both the Summary band/row and the Detail band/row. In addition, the Summary band/row was not being updated correctly. 22552 21912 21906 21908 21909 22526 22598 22565 22237 21649 21650 & 21651 144 of 155 267 Employee Roster Report using default availability. 268 Employee Roster Report - Hanging and Index out of bounds errors 269 Employee Roster Report Defect 270 Availability, Booked Visits, & Actual Supply & Print Max per Day Capacity/Supply Calc Error 271 Employee Roster Report - Print Employee Category 272 Client Service Summary -discipline order not printing same as chosen 273 Defect Revenue Analysis Report 274 Physicians Order Rep: effective date not filtering properly 275 Employee Calendar Schedule Report rows and columns out 276 Timekeeping detail by employee report template Procura 7- User Release Notes Reports | Scheduling | Employee Roster Report This update addresses an issue with the Employee Roster Report where a user was registered in multiple departments and was then terminated from one of them. Their availability displayed as 24 hrin the report when the Combine Dept. Output print option was checked. The availability for each department should have been calculated correctly. Reports | Scheduling | Employee Roster Report In regards to the Employee Roster Report, when the Combine Dept. Output print option was checked for more than two employees and for more than two departments with different sets of references, the application would stop responding when the Print button was clicked. In addition, an error occurred if the user changed the text in the Adj.Prev.Date Range box. These problems have been fixed. Reports | Scheduling | Employee Roster Report When running the Employee Roster Report with the option ‘Display in hrs and Mins’ selected, the report was printing incorrectly, (e.g., -1.-15 should display as -1:15.) This problem has been fixed. Reports| Scheduling | Employee Roster Report In regards to the Employee Roster Report, if an employee was marked as Unavailable on a given day and they had a visit booked on that same day, a positive value was produced for Actual Supply when it should have produced a negative value. In addition, the Supply band (aka Capacity) for an employee was not reporting the correct value. These problems have been fixed. Reports | Scheduling | Employee Roster Report This update fixes an issue with the Employee Roster Report where the Print Employee Category option on the form was not saving to the registry. Reports | Clients | Client Service Summary Report This update fixes an issue with the Client Service Summary Report where, when the user chose the service type/aux code in the order in which they wanted it to show on the report, the Client Service Summary discipline order was not printing in that order. Management | Fiscal Management | Revenue Analysis Report This update fixes an issue with the Revenue Analysis Report where back-billed Timekeeping records were displaying with no funder when using Pay Rate Record (after Timekeeping) for the Cost column. This problem has been fixed. Some records were not being matched to a funder when they should have been. Reports | Clients | Physicians Order Report This update fixes an issue with the Physicians Order Report where the effective date was not filtering properly. Reports | Scheduling | Employee Calendar Schedule Report This update fixes an issue with the Employee Calendar Schedule Report where the rows and columns were misaligned when any employee schedule was printed. Reports | Timekeeping | Timekeeping Detail by Employee Report This update fixes an issue with the Timekeeping Detail by Employee Report where the selected attendance type that was saved in the template was not being retained and displayed when the report was re-opened. 21702 21642 21824 21822 & 21823 21980 21728 22455 21605 21555 21727 145 of 155 277 Employee Calendar Schedule Report producing black line 278 Access Violation in RTL120.bpl 279 PPS Report - 'Print Episode Type' not printing any data 280 Employee Schedule report is double spaced 281 Contact Profile Report - printing 282 Labor Rules Exception report 283 Client Service Summary Report - column headings overlap 284 Client Mailing Labels Access Violation rtl140.bpl 285 MDS-HC - CAPS section - right click help error 286 User defined settings cause DB error 287 Remove broken button from MDS-HC form 288 OASIS Report PASE Dependency Procura 7- User Release Notes Reports | Scheduling | Employee Calendar Schedule Report This update fixes an issue with the Employee Calendar Schedule Report where a black line was printing at the bottom of the report. Reports | Employees | Employee Additional Information Report When the Employee Additional Information report was run with a Specific Department and Department Category selected, and with either Schedulable or Unschedulable chosen for the Status filter, an access violation error occurred. This problem has been fixed. Reports | Billing | PPS Report This update fixes an issue where the PPS Report failed to display any episode types when the Print Episode Type option was selected. Reports | Scheduling | Employee Schedule Report This update fixes an issue where the Employee Schedule Report printed in double-spacing and should not have. Management | CRM | Select | Print This update fixes a problem with the Contact Profile Report where, when it was printed, there was code that was being displayed when it should not have been. In addition, some of the data elements overlapped. Reports | Scheduling | Labor Rules Exception Report This update fixes a problem with the Labor Rules Exception Report where the user had 2 visits on their schedule; one at 40 hours in one department, and one at 1 hour in another department. The Labor Rule Exception report was including a total of 41 hours for each department in which they were registered. However, the total at the bottom indicated that they had exceeded the Max 40 Hours labor rule by 6 hours, when they had only exceed edit by 1 hour. Reports | Client | Client Service Summary Report This update fixes a problem with the Client Service Summary Report in which column headings were overlapping. Reports | Client | Client Mailing Labels Report This update fixes an error that was occurring when the user tried to print preview the Client Mailing Labels report. Clients | Select | MDS-HC This update fixes an error that occurred when the user right-clicked the CAPS section in the MDS-HC assessment, and then selected 'Help' from the shortcut menu. Clients | Select | MDS-HC This update fixes a problem with the MDS-HC assessment where a database error was being displayed when it was printed. Clients | Select | MDS-HC This update fixes a problem where the Edit Year function in the date-time picker in the MDS-HC form did not operate in Windows XP. It is now hidden on all Procura date-time fields. Note that this will only affect Procura running on Windows XP systems. Reports | Clients | OASIS Report When the user printed a blank OASIS that had a PASE assessment attached, custom questions that were based on dependencies were not printed on the OASIS Report. The issue is fixed in this update. 21815 22538 21932 22206 21852 22023 22025 22867 22683 22743 22620 22813 146 of 155 289 290 Access Right Attendance Types... invoice HST not displaying on 291 Error Posting Message HPG Service: Incoming document not XML 292 Archived MDS-HC assessments can still be added in MDS tab 293 TK - Define Periods Date change 294 'Copy Invoice To' prints arbitrary visit start/stop times on invoice copy 295 Workflow: Error when deleting tasks 296 HL7: Attendance Types transmitted with blank CVID 297 User dept access prevents message matching but still display Procura 7- User Release Notes Maintenance | General Setup | Departments | Validation Tab This update fixes a problem with the Edit and Add buttons for Valid Attendance Types in the Department Module. These buttons will now be disabled if the user does not have the access right called ‘Attendance Types’ enabled. This access right will also control access to Maintenance | Departments | Edit | Validation | Valid Attendance Types. Billing | Invoices This update fixes a problem with invoices where the HST was not displaying properly. The HST is setup to charge at the funder level. The billing details displayed the HST, but the invoice did not. Clients | CIS Inbox | Offers The update fixes an error that was displayed when the CIS Inbox processed an offer without creating a dated note. Now, when an offer is accepted through the CIS inbox, if no dated note is created, a message will be displayed. Clients | Select | MDS-HC This update fixes a problem where custom MDS-HC assessments were available on the Add list, even after they had been archived. Archived assessments are no longer visible when the user adds an MDS-HC assessment to the client. Timekeeping | Periods This update fixes an intermittent error that stated that the Scheduling Start Date was not being updated when the user edited the end date for a Timekeeping Period. Clients | Select | Episode This update fixes a problem that occurred when the ‘Copy Invoice(s) To’ box was used in the episode. The copy of the invoice did not accurately portray the visit start/stop times. Scheduling | Tasks This update fixes an error that displayed when the user attempted to delete a task from a Workflow. Imports/Exports | Exports | HL7 Transmission This update fixes an issue where Attendance Types were being transmitted if the CV_ID field was blank but not NULL. Clients | CIS Inbox | Referrals If a user did not have access to a department that was set up to be ‘seen’ by the CIS inbox, the referrals and offers were showing up in the Inbox for this user, but were unmatched to any department. The CIS Inbox displayed all clients, even though the user had access to the ‘Scan Department for Client’ access right. This problem has been fixed. These messages will no longer be displayed. 22788 22629 23134 22973 22757 23033 22549 22626 22925 147 of 155 298 299 CIS Inbox not matching department/funder w multiple partners CIS Inbox - Allow fields to be double-clicked on - to open a display window 300 CIS Inbox - Print capabilities 301 302 303 304 305 306 307 Employee Schedule Report – Address Field overwriting Callme! Comparison screen creates error Invalid Tag Allowance Claims Employee Schedule Report - Client Name / Phone Number CRW - Client Consistency Report - Missing attendance types CRW - Client Consistency rpt - Rebooked employee counts incorrect CRW - Client Consistency rpt - SQL Error found CR - PASE Supervisor Requirements include archived in list Procura 7- User Release Notes Clients | CIS Inbox | Referrals This update fixes an issue with the CIS Inbox where complex department and funder mappings were preventing messages from being attached to any departments and/or funders. See also defect #22925.However, the CIS inbox was not matching Departments correctly when more than one CHRIS Partner existed. This problem has been fixed. We now ensure that the Partner ID is not linked to multiple departments. In addition, messages that are obtained through each CHRIS Partner will match when they are used independently. However, this precludes the user from being able to have department or CCAC specific settings in the partner. Clients | CIS Inbox The ‘Hint’ box, which appears when the user ‘hovers’ their mouse over certain fields in the CIS Inbox messages, was being cut off, (e.g., in Dated Notes). The values that they were ‘hovering’ over contained more characters than which is allowed. Therefore, the end of the message was not being displayed. This problem has been fixed. We now allow the user to double-click a field, which will open a window in which the contents of that field are displayed in full. Clients | CIS Inbox This update provides for the ability to print from the CIS Inbox (Print Referrals Listing). Reports | Scheduling | Employee Scheduling Report This update fixes a problem with the Employee Scheduling Report where the Address field was overwriting the Visit start date and/or Area fields. Timekeeping | Adjust | CallMe! This update corrects an issue where the CallMe! Visit Comparison window was displaying an error. 22947 22903 22907 22892 22814 Reports | Scheduling | Employee Schedule Report This update fixes a problem with the Employee Schedule Report where the Client's name was overwriting the Client's phone number. Client Consistency CRW Report This update fixes a problem with the Client Consistency CRW Report where six attendance type visits were missing from the list of excluded attendance types. Client Consistency CRW Report This update fixes a problem where the count of employees in the Client Consistency CRW Report was not being adjusted to reflect those attendance type visits that were excluded. Client Consistency CRW Report This release adds to the number of ‘excluded’ attendance type visits that were missing from the Client Consistency CRW Report and which was causing the employee count to be higher than it should be. Clients | Select | Assessments When users selected ‘Supervisor’ for ‘Assessor/Surveyor Type’ in the PASE form, archived Supervisor Requirements were being included in the drop-down box when they should not have been. This problem has been fixed. Archived requirements will now be hidden. 23087 23064 23057 22987 22839 148 of 155 308 309 310 311 312 313 314 315 316 317 Client Profile report Reports | Client | Client Profile Report This update fixes a problem with the Client Profile Report where, if a Care Plan comment fell at the bottom of the page, the detailed description was overwriting the footer when the report was printed. CMS 1500 1000 Billing | Invoices Claims Rejected Box 24E This update fixes a problem with the CMS 1500 Invoice. Box 24 column E now displays a count of the Diagnosis Pointer diagnoses that is printed to Box 21 when the Funder Agency Reference Label, called ‘Diagnosis’, exists and its value equals ‘Option3’. V7 - (New) Billing Reports | AR/GL | Billing Details Report Details Report Template not This update fixes a problem with the Billing Details Report where, when the user created a template holding Funder for a report for a specific funder, and then they created a template for a report for a different specific funder, the report retained the funder value from the first template when they tried to run it from the template. V7 - Released Code Imports/Exports | AR/GL | QuickBooks AR Export for QB Invoice incorrect value in This update fixes an issue with the QuickBooks AR Export where the Funder Agency Reference Label, one field called ‘QB Invoice 2’, was reporting negative values in column M (PRICE). The rate is now retained as a positive value when this FARL is in effect, in the same way it is when only the QB Invoice FARL is in effect. Calculation in QB Imports/Exports | AR/GL | QuickBooks AR Export export enhancement not This update contains the following fixes to the Quick Books AR Export: rounding The PRICE column is now restricted to two decimal places The QNTY column will now report Expense/Mileage bill units, instead of the visit’s billing duration. Medication Monographs Clients | Select | Medications/Drugs folder This update fixes an issue where, if the user had not subscribed to the Medication database, the Print buttons that enable them to print monographs were visible when they should not have been. HL7 outbound - clients listed in Imports/Exports | Exports | HL7 Transmission error log for employees When the standalone PROHL7X.EXE file is used to run the HL7 export, the error CLIENT: [client name] MISSING STAFF ID was being generated in the system log. The client name will no longer be referenced in the employee file. (Alex) V7 - Scheduling Group Scheduling | Employee Scheduling Groups Confirmation Popup This update fixes an issue where the confirmation message, which indicates that there is a conflict between the client and employee Service Requirements, extended beyond the screen. V7 - HCFA 1500 - Cell 30 not being Billing used If the HCFA 1500 invoice was exactly one page in length, (i.e., page 1 is the final page), the Balance Due box (box 30) was empty. This problem has been fixed. The total invoice amount will always be displayed on the final page of the invoice and, when the invoice is only one page in length, page 1 will be considered the final page. V7 - Status change in workflow Workflow module Where the user changed the ‘Held’ status to the ‘Hospitalized’ status for some departments, and then, when two or more of those departments were selected for the Procura 7- User Release Notes 22652 23006 22939 23072 23107 21828 21871 22033 22262 22263 149 of 155 alert, they did not save. This problem has been fixed. For Client/Employee Status events, the conditions Client Status Change From/To and Client Status Change have been updated to only display a department status for departments that have been validated for the Alert. Therefore, if no departments are validated for the alert, then no department statuses will be displayed in the condition. The Alert must be validated for departments prior to setting up status conditions. 318 on Merge V7 - Employee Merge Utility - Error 319 V7 - Employee Schedule Grid: Show Labor Rule Totals 320 V7 - Linked PASE document will not upload unless reference is set 321 V7 - NW-21 - Custom Mileage Rules - Change to Cancelled Visits 322 V7 - General - change local filtering date format logic 323 Access Violation rtl120.bpl error when Closing TK Periods 324 V7 -Visit History Generation System Log Entry shows 0 records created 325 HL7 Client export - should explicitly exclude attendance types 326 HL7 - Attendance Type Message Construction incorrect (6.0) Procura 7- User Release Notes Maintenance | Utilities | Employee Merge Utility This update fixes an issue where, when the user ran the Employee Merge Utility to merge two employees, an error was being generated if the source employee had Availability. Scheduling | Employee Schedules If an employee had no labor rules for a selected department, their entire visit calendar grid in the Scheduling module was shaded in the color white. This was overriding the Availability display if ‘Off Days’ were set to display in a different colour. This problem has been fixed. If a labor rule does not exist for the employee/department, it will not display shading. Clients | Select | Clinical Day View The user attached a PASE document to a client in Clinical Day View on their local database, and then linked it to a visit. When they uploaded the client to the server, and then downloaded that client back to their local drive, the PASE document was no longer attached or linked. This problem has been fixed. Timekeeping Cancelled visits are now being excluded from this enhancement. 22358 This update fixes a problem with the local date filtering, which has been changed from the Short Date Format to D-MMM-YYYY. Timekeeping | Periods | Close Period | Check for Unverified Visits When the user closed a Timekeeping period with the Check for Unverified Visits box checked, an error was generated. This problem has been fixed. The Timekeeping Detail Summary report will run as it should and no error will be generated. See also defect 22538. Maintenance | Processing | Visit History When the user ran the Visit History calculation, a report was produced of a number of records that were created. But the System Log file indicated that zero (0) records were created when it should have displayed the actual number. This problem has been fixed. Imports/Exports | Exports | HL7 Transmission This release fixes an issue where, if there was bad data in the client database, attendance types were included in the HL7 export when they should not have been. Imports/Exports | Exports | HL7 Transmission This update fixes a problem with the HL7 export. The value that was being exported in position 4 of the PV1 segment will now be exported in position 3 of the PV1 segment. 22634 22385 22416 22627 22692 22709 22726 22736 150 of 155 327 V7 - Wildcard reporting allow freeform typing in area field 328 Upload License Data - Invalid Pointer Operation 329 Dated Notes – being saved/sent to recipient if deleted 330 Availability/Employee Roster Report - Midnight Start 331 V7 - Task Event Client status activation not working Procura 7- User Release Notes Reports This update fixes an issue where the user was unable to type a wildcard in the Area drop-down box on many of the report forms. Wildcard functionality has now been restored to the Area drop-down boxes that appear on the following report forms: 22740 Client Status Changes Order/Episode Maximum Exception Availability Employee Schedule Employee Timesheet Labor Rules Exception Weekly Caseload Billing Period Summary Profitability ADT by Age ADT by Funder ADT by Gender ADT by Referral Client Status Changes Visit Counts by Billing Code and Start Time or Shift code Visit Counts by Funder and Billing code Visit Counts by Start Time or shift code Workload Analysis by Area HR Statistics by Language HR Statistics by Status Reason Visit counts by employee Category Maintenance | Licensing This update fixes a problem where, when the user was attempting to upload their license data to Procura, an error occurred. Clients | Select | Dated Notes folder If the user entered a recipient into the To: field in a Dated Note, and then removed that recipient and clicked Save/Send, the note was emailed to that recipient, even though it had been removed. This problem has been fixed. Dated Notes that do not contain a recipient name will ever only be saved. Report s | Scheduling | Employee Roster Report An availability with a Midnight start time (00:00) was being treated as a null value (12/31/1899 00:00:00). This caused the field to appear blank in the Availability module and these entries did not show up on reports, such as the Employee Roster Report. This problem has been fixed. Workflow Workflow Alerts were not working correctly for client status activation. After creating an alert, and then changing a client’s status from Discharged to Active, no alert was being 22744 22753 22809 22827 151 of 155 generated. This problem has been fixed. 332 V7 - Schedule Generation - File & System Log 333 V7 - Weekly Planning Rpt converting repeating durations incorrect 334 V7 - Celltrak - HL7 - Inbound Unscheduled client visit 335 V7 - URN number on Client Co Payment Report only displays 9 digit 336 Defect/CR: HH-CAHPS Min CMS Export CSV 337 V7 - Client Service Summary Report - Wrong Table Queried 338 BC SPEC 50 Waitlist Status not option for Scheduling Group 339 SEHC-ADP Payroll Export Procura 7- User Release Notes Maintenance | Scheduling Setup | Schedule Generation If the user who was running Schedule Generation did not have access to the destination folder for the log file, no System Log entry was being generated, even though an entry should be generated regardless of their inaccessibility. This problem has been fixed. Reports | Scheduling | Weekly Planning Report When a One-Time visit was scheduled with a duration of 50m in the ‘Hrs and Min’ format, it was automatically converted to 0.8333 in the employee’s visit. This has been fixed. The visit durations that were entered in 'Hrs and Min' format were being converted to a repeating number, which was being rounded down by the Weekly Planning Report. Imports/Exports | Imports | HL7 Import This update fixes an issue with the HL7 import where, if an unscheduled client visit was imported, but the client's telephone number was not unique, Procura would not automatically populate the client record when a visit was created in the CallMe! window in Timekeeping. Reports | Billing | Client Co Payment Report If a client was included in the Client Co Payment Report and their URN number exceeded 9 digits, the report would cut off after this limit. This problem has been fixed. This field limit has now been increased to accommodate for as many digits as possible. Imports | Exports | HH-CAHPS Export This update corrects the following issues with the HH-CAHPS Minimum CMS Export when run in CSV format: Column 60 (ADL Feed) is no longer required per CMS and has been removed. Column 54 (ADL Deficits) was not correctly totaling the answers from Columns 55-59. Reports | Client | Client Service Summary Report In the Client Service Summary Report, the ‘Visit Total Options’ selection is populated by relating the billing records to the various attributes of the billing tables. However, for new billing tables that were created, it would not return any results from which to pick. This problem has been fixed. Scheduling | Client Scheduling | Groups When a client was added to, or unarchived from, a scheduling group, the Status dropdown box in the Group Status window only had four options - Assessment, Active, Held and Deceased Support. There was no option to select the Wait Listed status. This problem has been fixed. All client department statues will now be available when adding a client to a scheduling group. Imports/Exports | Exports | SEHC-ADP Payroll Export This update fixes a problem with the SEHC-ADP Payroll Export where, when it was run, an error was being generated, and then it would crash. 22829 22830 22857 22875 22909 22926 22928 22945 152 of 155 340 Medication Profile Report columns overwriting 341 Client Ref no Stat Rep points to wrong table 342 HL7 - Duplicate visit / travel time entries 343 V7 - Client schedule: employee search filter inaccuracies 344 V7 - 'Copy Invoice To' prints arbitrary visit start/stop times on invoice copy 345 V7 - Refresh issues in payment processing Filters and visits 346 V7 - Batch payments - edit reversal from unposted batch - error 347 V7 - Premium Pay Utility Rounding error with start/stop time? 348 V7 - status generation is stopping the schedule records from generating forward 349 V7 - Callme - visits showing zero's in mileage column Procura 7- User Release Notes Clients | Select |Medications/Drugs folder The data in the columns on the Medication Profile Report was overlapping when it was printed from the Medications/Drugs folder in the Client Information form. This problem has been fixed. The report was not allowing enough space in the Strength column in order to allow for longer entries. Reports | Statistical | Client Reference Number Statistical Report This update fixes a problem with the Client Reference Number Statistical Report where the query that populates the Status drop-down box was using the wrong table. The query now uses the correct table. Imports/Exports | Imports | HL7 Import This update fixes a problem with the HL7 Import where duplicate entries in EDCCALLS / EDCVISITS were being generated if the import needed to stop and restart. Scheduling | Client Scheduling This update fixes a problem with visits that were being added to the client schedule using the employee search filters. If the visit had a duration and both the 'Check Service Reqs' and 'Check Availability' filters were checked, and then the ‘Check Service Reqs' was unchecked and rechecked, the results returned the second time were different. Clients | Select | Episodes folder When the ‘Copy Invoice(s) To’ box was used in an episode to copy an attached invoice, the copy of the invoice did not accurately portray the visit start/stop times. The original printed invoice did, but the copy displayed arbitrary start/stop times of 07:00pm12:00am for all visits, regardless of the actual visit times. This problem has been fixed. Billing | Payments | Processing This update fixes a problem where, when the user edited the time or bill duration of a visit, the associated billing record was being updated, but the billing grid was not being refreshed. Billing | Batch Payments This update fixes a problem where an error occurred when a batch payment was edited, which instructed the user to re-select invoices. Imports/Exports | Payroll | Custom Pay Premium Calculation Utility This update fixes a problem with the Custom Pay Premium Calculation Utility where a rounding error was occurring when the visit duration was calculated using the start/stop times. Scheduling After a patient was put on a Held status, and then taken off, visits that were previously part of a pattern became One-Time visits and would not generate forward. This problem has been fixed. The status generation was stopping the schedule records from generating. Timekeeping | Adjust | CallMe! This update fixes a problem with in CallMe! where, when no expense records existed, mileage was still displayed in the Mileage column with a value of zero (0). 22982 22984 23000 23008 23033 23041 23053 23062 23078 23097 153 of 155 350 V7 - Close TK Period - Check for unverified visits 351 V7 - TK - Previous period visits showing in current 352 Client Care Connection spelling error in filter options 353 ONI--Prox.bpl 6.1.1.8--Equipment comments exceed deselect 354 Work Order JBC-20 incorrectly totaling hours 355 Reports: Collection Letter Report/Client Aged 356 HL7 - Transmission - Performance Improvements 357 Availability/Employee Roster Report - Midnight Start Procura 7- User Release Notes Timekeeping This update fixes a problem where an error would occur when closing a Timekeeping period and checking for unverified visits. Timekeeping The previous Timekeeping periods were being displayed in the current period because a comparison of the visit date and time with the closed period date and time was not including seconds. This problem has been fixed. Clients | Care Connection | Display This update fixes a problem where there was a typographical error in the term ‘Client Service Plan’ that exists in the filter options on the Care Connection form. Imports/Exports | Imports | ONI When a lengthy description was given for the ‘Aids and Equipment Used’ question/answer, the ONI import did not import the value for that question. This problem has been fixed. The contents of this field will now be truncated if it exceeds 80 characters and the value that is entered will be allowed. Billing | Invoices This update fixes a problem where the visit duration was not being represented correctly on the Professional Services Logo invoice because it used the Billing Duration field from the Billing table to determine the visit duration. The visit duration from the Visits table will now be used. Reports | Billing | Client Aged Report This update fixes the following problems with the Client Aged Report: When an image that is 443 x 403 pixels was inserted, it was being autoresized incorrectly, which was causing it to overlap the date. Incorrect values for the number of Days Overdue were being generated when the Collection Letters were run. The value for the number of Days Overdue column on the Collection Letter Report was overlapping the value in the Amount Due column. Imports/Exports | Exports | HL7 Transmission This update improves the performance of the HL7 Transmission by decreasing the processing time that is required to find care plan activities for each visit. Note that version 6.2.0.5 of the PROHL7X.EXE file is required if you use the Standalone HL7 Export. Reports | Scheduling | Employee Roster Report This update fixes a problem where employee availability that has a midnight start time (00:00) was being treated as a value, (e.g., 12/31/1899 00:00:00), which caused the field to appear blank in the Availability module and the entries did not display on reports, such as the Employee Roster Report. Employee availability that starts at midnight will now be reported correctly in the Employee Roster Report. 23124 23165 23210 22228 22710 22719 22745 22809 154 of 155 358 QB AR Export - FARLs from wrong funder being applied 359 Client Aged Report - Templates and Specific Transactions 360 V7 - Show Labor Rules in Scheduling - Colors disappear 361 OASIS Calculate PPS on the fly Access Rights 362 Duplicate CVID - Same Employee Same Day possible Procura 7- User Release Notes Imports/Exports | AR/GL Exports | QuickBooks AR Export This update fixes a problem where, when the QuickBooks AR Export was run with the 'QB Invoice' and 'QB Invoice 2' Funder Agency Reference Labels, the billing charge that was being exported was being formatted incorrectly if the source funder was not defined for that export. Reports | Billing | Client Aged Report This update fixes a problem where, when the user saved specific transaction types within a template on the Client Aged Report, they would remain selected when the user switched templates. Scheduling | Client Schedules | Select | Options | Environment Options When the Show Labor Rule Totals checkbox is checked in the Environment Options window in the Scheduling module, the cells that contained values that exceeded the labor rule, would be colored red. But, if the user used the scroll bar or clicked another cell, the color would disappear from the cell. This problem has been fixed. Clients | Select | OASIS There are two Access Rights that control the display of HIPPS/HHRG and PPS Amounts within the status bar at the bottom of the OASIS form. The Access Rights were originally designed to control whether the HIPPS/HHRG values would be updated ‘on the fly’ as users changed the OASIS ‘money’ questions that are colored in red. The intent was to allow customers to make a business decision as to whether nurses should be allowed to see the financial impact of their OASIS entries while they perform the assessment. The access permissions were not originally intended to extend to the PPS Information form or to the OASIS Header display. However, because ‘on the fly’ is a subjective phrase, it is reasonable for a customer to interpret these access rights as being a method by which the values would be excluded from the PPS Information and OASIS Header form. Therefore, when a user does not have the Access Rights for ‘OASIS Calculate HHRG/HIPPS on the fly’ and ‘OASIS Calculate PPS Amount on the fly,’ the display of these values on the PPS Information form and on the OASIS document's header form are now hidden from the OASIS form and will not display/print on the OASIS Report. CallMe! Procura prevents the creation of duplicate CVIDs for the same client on the same day. However, duplicate CVIDs could still be created for the same employee on the same day, which caused issues for CallMe! This problem has been fixed. 23177 23212 23216 23217 23218 155 of 155