-------------------------------------------------------- Release Notes for MRO Management v 5.3.41014 14 October, 2004 -------------------------------------------------------- 1. Introduction -------------------------------------------------------- This text is stored in a file called UPDATE.TXT. It will be installed into the program directory, so you can read or print it at your convenience. These release notes are provided to help you learn about changes to the software that have occurred too late to include in the on-line manual and help systems. Review the Contents section (next) to see if any of the Release Notes may be of interest to you. 2. Contents -------------------------------------------------------- 1. Introduction (prior section) 2. Contents (this section) 3. Enhancements 4. Fixes 5. Known Issues 6. Post-CD Fixes & Enhancements -------------------------------------------------------- 3. Enhancements -------------------------------------------------------- HOLD RESULTS FOR TERMINATED PARTICIPANTS The Validation routine will optionally generate an exception if the participant for a given result is marked as terminated in DrugPak. See Global Settings | There is an additional option to ignore the TERMINATED status for results with an "auto-add" test type. This means that if a Test Type is listed as one which should trigger the addition of new participant, then the Validation routine will export the result even if that participant is TERMINATED. NEW VALIDATION OPTIONS: RECORD AN EXCEPTION IF A DOT RESULT HAS A NON-DOT PANEL If this option is turned on, then each DOT Drug result panel must contain all the following (and no other) substances codes: AMP COC MAR PCP OP SEARCH INTERNAL COMMENTS FOR "DILUTE/SUBSTITUTED" TRIGGER TEXT If this option is turned ON, then the Validation routine will check the INTERNAL comments field for the words DILUTE or SUBSTITUTED. If either of these words appear, then the Validation routine will turn ON the corresponding DILUTE or SUBSTITUTED checkbox for the result. If this option is turned OFF, then MRO Management will NOT check the INTERNAL comments field to trigger the DILUTE/SUBSTITUTED fields. SEARCH RESULT LETTER COMMENTS FOR "DILUTE/SUBSTITUTED" TRIGGER TEXT This feature works the same as the prior feature, except the validation routine will be examining the "Result Letter Comments" RECORD EXCEPTION WHEN PARTICIPANT IS TERMINATED Options include: - Never record exception - Always record exception - Record exception only if not pre-employment test. (This last option is useful when you have chosen to automatically terminate participants when auto-added through MRO Management). RECORD AN EXCEPTION IF ALCOHOL RESULT IS POSITIVE WITHOUT >.02 OR >.04 SPECIFIED Turn this option OFF if you want to permit a "P" positive result for Alcohol. Turn this option OFF if you want to require entry of Stage 1 (>.02) or Stage 2 (>.04) for positive results. NEW "NEW PARTICIPANT" OPTIONS: "Include in Randoms Status" New checkbox: Never include in randoms if result is non- negative. This will override the participant template, as well as the following option: When adding participants: - Obey the participant template's "Include in Randoms" - Never Mark "Include in Randoms" - Always Mark "Include in Randoms" New "Active/Terminated Status" Options New checkbox: Never mark active if result is non-negative. This will override the following option: When adding participants: - Never Mark "Active" - Always Mark "Active" DUPLICATE SPECIMEN OPTIONS The following checkboxes control under what condition the user will be notified when the specimen ID already exists in DrugPak or MRO Management: - Warn on ANY duplicate drug specimen - Warn on ANY duplicate alcohol specimen - Warn on any duplicate specimen for same SSN (in any company) - Warn on any duplicate specimen in the same company (for any participant) - Warn on any duplicate specimen in the same company and participant (this is the old, default behavior) Duplicate Specimen Prompts: - Prompt only when verifying a single record (otherwise record an exception). - Prompt always - Prompt never (always generate an exception) When prompted, the user will have the opportunity to replace the existing result record, generate a separate result record, or generate an exception. MISCELLANEOUS Changed layout installation so that only lab layouts appear (billing layouts can no longer be installed from MRO Management). -------------------------------------------------------- 4. Fixes -------------------------------------------------------- Fixed bug in which the MRO Names screen could not be accessed using the ">" button. Fixed bug in which a positive alcohol test was causing the corresponding drug test to be marked positive as well when exported to DrugPak. Marking a record SUBSTITUED also made it DILUTE. The correct behavior is that SUBSTITUTED and DILUTE are mutually exclusive. This has been fixed. -------------------------------------------------------- 5. Known Issues -------------------------------------------------------- You can keep up-to-date with the latest version of DrugPak by visiting our Update page on the web: http://drugpak.com/update -------------------------------------------------------- 6. Post-CD Fixes & Enhancements -------------------------------------------------------- 1/29/2004 Added security for MRO program access Fixed bug: Missing name not always caught when required Fixed bug: Participant sometimes not matched if DOT or administration information is missing Fixed Bug: Exception button sometimes positioned incorrectly. Fixed bug: Participant sometimes not added if DOT or administration information is missing. Fixed bug: Non-DOT tests for DOT participants were being changed to DOT tests. Fixed bug: MRO name was being populated incorrectly. 2/11/2004 Refined the way in which DOT and Administration flags are set when a new participant is added via MRO Management. 2/18/2004 Added global option to prohibit/allow collection and verification dates after the system date. 2/25/2004 Modified MRO Worksheet report so that comments will print across page breaks. 3/18/2004 Fixed a problem in which the MRO name was not updated properly when changing the MRO for a result. The MRO name appears correctly on the screen, but is incorrect on reports. 3/30/2004 Added a new dialog to the import. If an MRO name is not found, you have the choice to match it with an existing MRO, use the default MRO, or add a new MRO with the name being imported. Once this choice is made, the import will remember that decision when it encounters the name again. 04/09/2004 Update for new version of Document Manager 04/26/2004 -- Added a new option: "Global Settings | MRO Management Module | Required Fields: Require Home Base". An exception will be raised if the home base is blank, but only if the Company has Home Bases on file. -- Fixed a bug in the validation routine which allowed DOT results to be exported without an occupation or DOT administration under some circumstances. Specifically: a) The test is an "auto-add participant Test type" b) The participant template for that company includes the occupation c) The participant already exists d) The existent participant does not have an occupation (or DOT Administration) specified. -- Updated the "Browse Work File" window - Now it will save window dimensions and position - Now it will save the last used index - Now it will save the field sequence and widths - Now it uses the "Quick Find" window for searching - Now it has a Filter panel. 5/26/2004 -- Linked Document Manager documents were not being found when a test record is posted. 6/3/2004 -- The MRO Worksheet was printing the DOT status of the participant instead of the DOT status of the test record being printed. Now, the DOT and administration is coming from the result record in MRO Management. 6/03/2004 Fixed a "list index out of bounds [1]" error that occurred when attempting to link a Document Manager document. 6/11/2004 Fixed an access violation that occurred when linking document manager documents during the import process. 6/24/2003 Updates data for compatibility with new Document Manager feature, allowing links to multiple tables. 8/10/2004 Fixed an access violation that occurred when matching codes for the Clinical Reference Lab layout. Fixed a problem in the MRO Results List, in which the company filter was not being obeyed. The record count for the work area was being calculated every time the user moved to a new record, and was being calculated multiple times when the Find window was used. Now the record count can be run on demand, by double- clicking the appropriate status bar panel (the panel reads, "Double-click for record count"). 8/20/2004 Fixed an error when selecting Match Codes for the Clinical Reference Labs layout. Fixed an error ("Value must be between 1 and 2147483647") that occurred when user pressed the Match Codes button in the Translation Engine Control Panel. 10/13/2004 Added process to insert the Record Added Date (R_ADDED) after a result data for an random (RND) test is entered.