CyberLAB Version 7.3.0 New Features Guide · aimed at helping providers, payers, vendors, and non-covered entities with the transition to ICD-10. CyberLAB’s support of ICD-10 codes

CyberLAB® Version 7.3.0New Features Guide

Includes

Includes:• Feature Enhancements• Improvements and Corrections

Copyright Notice

LAB_NFG_V7.3.0_1 iii

Copyright Notice© Copyright 1996 - 2013 ASPYRA, LLC.

All rights reserved. Information in this document is subject to change without notice. Documentation updates will be provided in accordance with contractual agreements. The information in this guide, including procedures, methods, and concepts herein, is the proprietary property of ASPYRA, LLC, its wholly owned subsidiaries, and its licensers and may not be reproduced, or transmitted in any form, for any purpose, without the express written permission of ASPYRA, LLC.

The software described in this document is furnished under the software licensing agreement discussed in contractual documentation and may be used or copied in agreement with the terms of this license.

WARNING

The CyberLAB® system is intended for use only by qualified medical or systems administration personnel. Users must be thoroughly trained and knowledgeable in the use of the software and equipment. Use by unauthorized personnel can result in a breach of security and could compromise patient care.

TRADEMARKS

CyberLAB®, CyberPATH®, CyberMATE®, ImageACCESS®, MedCAP®, MedCHAT®, ImageWEB®, and MedVIEW® are registered trademarks of ASPYRA, LLC in the United States and/or in other countries.

Windows® and Windows NT® are registered trademarks of Microsoft® Corporation.

Crystal Reports® is a registered trademark of Business Objects, Inc.

Eltron® and Zebra® are trademarks of Zebra Technologies Corporation.

RightFax® software is a registered trademark of Captaris, Inc.

Unix® is a registered trademark of The Open Group.

JSCharts® is a registered trademark of SmartketerLLC.

iv CyberLAB New Features Guide

Revision HistoryThis section contains a history of the changes made to this guide at each revision. It is important that you use the guides intended for the software version you are using. For more information about the current online documentation, contact ASPYRA.

• LAB_NFG_V7.2.8_1

This is the original release of the CyberLAB New Features Guide for version 7.2.8.

• LAB_NFG_V7.2.8_2

This is a revised release of the CyberLAB New Features Guide for version 7.2.8.

• LAB_NFG_V7.2.9_2

This is the current release of the CyberLAB New Features Guide for version 7.2.9.

• LAB_NFG_V7.2.10_1


• LAB_NFG_V7.2.11_1


• LAB_NFG_V7.3.0_1


ASPYRA, LLC

800-437-9000Corporate Headquarters

ASPYRA, LLC4360 Park Terrace DriveWestlake Village, CA 91361

Fax: (1)818 880 4398

[email protected]

East Coast Offices

ASPYRA, LLC9432 Baymeadows RoadJacksonville, Florida 32256

Fax. (1)904 448 3042

[email protected]

European Headquarters

Aspyra Technologies, Ltd.

Cardinal PointPark RoadRickmansworth, WD3 1RE England

+44 (0)1923 432610

Fax: +44 (0)1923 432810

[email protected]

mailto:[email protected]



LAB_NFG_V7.3.0_1 v

Chapter 1: CyberLAB Version 7.3.0 Enhancements and Improvements .....................1-1

CyberLAB Enhancements ....................................................................................................................1-2 New ICD-10 Code Sets .................................................................................................................1-3

Patient Entry ............................................................................................................................1-3Collection Verification ..............................................................................................................1-4Medical Necessity Rules .........................................................................................................1-5Standing Order Entry ...............................................................................................................1-6Standing Order List .................................................................................................................1-7Inbound/Outbound Interface ....................................................................................................1-8

Enhanced Patient Reporting ..........................................................................................................1-9Previous Results ...................................................................................................................1-10

Urinalysis Alpha Results Enhancement .......................................................................................1-24FAX / Email Restricted Tests Enhancement ................................................................................1-26Extended Range Configuration ....................................................................................................1-27Worksheet Cleanup and Performance Enhancement ..................................................................1-29Collection Verification Streamlined ..............................................................................................1-30Updated CyberLAB User Interface ..............................................................................................1-31

Improvements and Corrections ..........................................................................................................1-35

Chapter 2: CyberLAB Version 7.2.11 Enhancements and Improvements ...................2-1

CyberLAB Enhancements ....................................................................................................................2-2Email Notifications Based on Interim Report Rules .......................................................................2-3

Email Configuration and Customization ..................................................................................2-8Email Authorization Request Forms ............................................................................................2-10Email Options Tied to User Class ................................................................................................ 2-11Patient Orders Entered Using New Rapid and Batch Options .....................................................2-13

Designating Patient Entry Type .............................................................................................2-14Collection Verification Now Includes Notifications of Required Account Information Changes ...2-19Encrypted User Password Field ...................................................................................................2-22Patient Report Faxing Configurations ..........................................................................................2-22Viewable Sample and Collection Comments Fields in Microbiology Results ...............................2-23Single Result Entry Displays Sixteen Samples Per Page ............................................................2-25Enhanced Automatic Tech IDs .....................................................................................................2-26Organism Workup Comments Deletable from Held State ............................................................2-27Interim Reports Can Display Client Route ...................................................................................2-27

Table of Contents

Table of Contents

vi CyberLAB New Features Guide

New Patient Held Report Required Fields and Sort Options .......................................................2-28Web Gateway Security Enhancements .......................................................................................2-28MNV Waiver for Printing Medicare Bill Types ..............................................................................2-29CyberLAB Supports Label Printing by DYMO Label Writers ........................................................2-30Web Gateway Order Entry Prints Requisition Forms ...................................................................2-30CyberLAB Library of Custom Reports using Microsoft SQL Services .........................................2-30


Chapter 3: CyberLAB Version 7.2.10 Enhancements and Improvements ...................3-1

CyberLAB Enhancements ....................................................................................................................3-2Client Master Maintenance Enhancements ...................................................................................3-2

Increased Field Size ................................................................................................................3-2Client-Defined Requisition Options .........................................................................................3-3

Test Dictionary Maintenance Enhancements .................................................................................3-4Duplication of Test Name ........................................................................................................3-4Printing of Custom Panel Test Labels .....................................................................................3-5

Medical Necessity Rules and Setup Enhancements .....................................................................3-7Addition of All Bill Types ..........................................................................................................3-7Addition of Payer (Insurance) Codes for All Bill Types ............................................................3-8Additional Age and Gender Fields within Medical Necessity Validation Rule Setup ..............3-9

Order Entry Decision Support Enhancements .............................................................................3-13Additional Payer Code Fields ................................................................................................3-13Additional Payer Maintenance Rule Types ............................................................................3-15Venipuncture Rules ...............................................................................................................3-20

Patient Inquiry Enhancements .....................................................................................................3-21Reposition of Send-out Code on Result Line ........................................................................3-21Abnormal Send-Out Result Color-Keyed ..............................................................................3-22

Patient Entry Enhancements .......................................................................................................3-22Additional Insurance Fields in Patient Demography ..............................................................3-22



CyberLAB Enhancements ....................................................................................................................4-2QC Graphs Now Display in Graphical Form ..................................................................................4-2Species Code Selection List at Order Entry ...................................................................................4-2User Class Control Over Schedule Download Menu Content .......................................................4-2

Improvements and Corrections ............................................................................................................4-2


CyberLAB Enhancements ....................................................................................................................5-2Access Unix-Archived Reports from Windows ...............................................................................5-2Quick Launch Icon Bridge to Another Website ..............................................................................5-2Generate Interim Report Print Activity ...........................................................................................5-3Five Color Choices for Delta Flag ..................................................................................................5-3

Table of Contents

LAB_NFG_V7.3.0_1 vii

Work in Progress Report Offers New Filter ....................................................................................5-3Test Dictionary List Includes Handling Procedures ........................................................................5-3Autotransmit Batch to International Destination .............................................................................5-4

Improvements and Corrections ............................................................................................................5-4

Table of Contents

viii CyberLAB New Features Guide

c h a p t e rCyberLAB Version 7.3.0 Enhancements and Improvements

This chapter in the New Features Guide highlights the product enhancements available in CyberLAB version 7.3.0.

If you need additional information about the CyberLAB system, you can access the Online Help system while in the CyberLAB application by pressing the Quick Launch button that has an image of a book.

Contact your ASPYRA support representative for more information.

In This Chapter...

CyberLAB Enhancements .................. 1-2

Improvements and Corrections ........ 1-35

CyberLAB Version 7.3.0 Enhancements and Improvements

1-2 CyberLAB New Features Guide

CyberLAB EnhancementsIn this section, you can learn about the enhancements made to the CyberLAB system in version 7.3.0. The feature enhancements are organized by either module or sub-module and include the following changes:

New ICD-10 Code Sets ................................................................................................................... 1-3

Enhanced Patient Reporting ........................................................................................................... 1-9

Urinalysis Alpha Results Enhancement....................................................................................... 1-24

FAX / Email Restricted Tests Enhancement............................................................................. 1-26

Extended Range Configuration .................................................................................................... 1-27

Worksheet Cleanup and Performance Enhancement ............................................................... 1-29

Collection Verification Streamlined ............................................................................................. 1-30

Updated CyberLAB User Interface.............................................................................................. 1-31

CyberLAB Enhancements

LAB_NFG_V7.3.0_1 1-3

New ICD-10 Code Sets CyberLAB now supports the use of ICD-10 Diagnosis codes while continuing to support existing ICD-9 codes. ICD-10 is the latest revision of the ICD codes developed by the World Health Organization and is due to come into effect in the United States on October 1, 2014. All entities covered by HIPAA must begin using ICD-10 codes on this date - this is not optional.

CyberLAB has been enhanced to equip our customers with the capabilities to fully support the ICD-10 transition. These features can be used to load and test the new ICD-10 codes once each customer has decided how to apply and implement ICD-10 in a specific environment.

The Centers for Medicare and Medicaid Services (CMS) is a government organization that bears the bulk of the responsibility for promoting the adoption and use of health information technology in the nation’s health care system. The CMS Web-site has an ICD-10 Resource Center (www.cmb.gov/ICD10), which covers all of the important issues with specific section aimed at helping providers, payers, vendors, and non-covered entities with the transition to ICD-10.

CyberLAB’s support of ICD-10 codes involves multiple areas of the application, though primarily centered on the structure of data files that maintain the Diagnostic codes, as these are used by many core programs.

The following information regarding CyberLAB’s support of ICD-10 diagnosis codes pertains solely to those activities generally undertaken by system users within your facility. Necessary program changes, such as loading the ICD-10 table and setting the flags that are used to control versioning, are managed exclusively by ASPYRA support and are, therefore, not addressed here.

Patient EntryThe change in ICD code support is evidenced in Patient Entry during the entry/update of specific tests. Depending on the value of the global ICD Version flag (‘09’ or ‘10’), all displays of the ICD code will be in the format associated with that version. The selection screen provided in this area is also determined by the setting of this flag.

For samples entered in any version prior to 7.3 the displays will be in the ICD-9 format and the selection window will display the contents of the ICD-9 table. The ICD code (09 or 10) can be added in all three entry areas: Patient Entry, Batch Entry, and Rapid Entry with the code selection process for each entry type being the same and appearing similar to the following:



Figure 1-1: Example of ICD-10 Codes Accessed from Sample Entry Screen

Collection VerificationYou will encounter the ICD codes in Collection Verification during the entry/update of specific tests. Depending on the value of the global ICD Version flag (‘09’ or ‘10’), all displays of the ICD code will be in the format associated with that version. The selection window provided in this area is also determined by the setting of this flag, and appears similar to the following:

Figure 1-2: Sample Entry Screen


LAB_NFG_V7.3.0_1 1-5

Collection records should not be carried over from an ICD-9 entered mode, so there is no need to view Collection records in the ICD-9 format once the global ICD Version flag has been set to ‘10’.

Medical Necessity Rules The diagnosis code definitions for ICD-10 values are stored in a new table, separate from the ICD-9 codes. The maintenance program has been modified to utilize the appropriate table based on the global ICD Version flag first, but it also allows for an override so that new ICD-10 rules may be entered prior to the official cutover to ICD-10.

Support can enable an option called “Dual Entry” that will allow the system to use and bill for ICD-9 while allowing the facility to set up ICD-10 in advance. This switch will be enabled by default in your test environment and disabled by default in your live environment. Please contact Client Support if you desire this behavior to be changed.

Figure 1-3: ICD Code Version Selection Example

Figure 1-4: Example of Entering/Maintaining MNV Diagnosis Records



Both Rule Maintenance and Print MNV Rules List will be based on the ICD Version for this session as entered.

Before ICD-10 can be tested, MNV rules for ICD-10 must be set up. These rules are not related to ICD-9 rules and cannot be converted to ICD-10. They will need to be configured manually by a user skilled in defining ICD-10 rules in accordance with the CMS requirements.

Standing Order EntryThe diagnosis code definitions for ICD-10 values are stored in a new table, separate from the ICD-9 codes. The program has been modified to utilize the appropriate table based on the global ICD Version flag first, but it also allows for an override so that Standing Orders with ICD-10 codes may be entered prior to the official cutover to ICD-10.

Figure 1-5: Example of ICD Code Selection

Figure 1-6: Example of Entering/Maintaining Standing Order Diagnosis Records


LAB_NFG_V7.3.0_1 1-7

Standing Orders using ICD-9 codes will not be converted automatically to use ICD-10 codes. All Standing Orders in the system must be re-assigned the appropriate ICD-10 codes manually. Using the “Dual Entry” feature, simultaneous access can be maintained between both sets of Standing Orders ICD codes until all orders have been converted to ICD-10 by a user skilled in selecting the correct ICD-10 codes for the orders.

Standing Order ListThe Standing Order List has been modified to use the appropriate table based on the global ICD Version flag first, but it also allows for an override so that the Standing Order List will reflect the entries from the appropriate tables.

Figure 1-7: Standing Order List Version Selection Screen

Figure 1-8: Standing Order List Sample



Inbound/Outbound InterfaceCyberLAB updates also address the issue of successfully transmitting both ICD-9 and ICD-10 codes via HL7 mapping, helping you maintain an uninterrupted and accurate flow of information between interfaces and facilities.

HUB Interface Processor ModulesSince these interface modules, which are dealing with HL7 standards, don’t access any database tables and are also not product dependent, the format of the ICD version is controlled strictly inside the HUB parameter file associated with each interface.

The following new parameter line entries have been added to handle both the current and the new ICD features.

SEND-DIAG-FORMAT=YES

The ICD code version for each diagnosis code will be sent in DG1-03.3 and/or in FT1-19.3 HL7 fields for outbound interfaces.

DEFAULT-DIAG- FORMAT=ICD9

DEFAULT-DIAG- FORMAT=ICD10

The default ICD code version can be defined if all of the diagnosis codes in the incoming and/or the outgoing HL7 messages are of the same format.

SEND-DIAG-ICD9-FORMAT=VALUE I9

SEND-DIAG-ICD10-FORMAT=VALUE I10

SEND-DIAG-ICD9-FORMAT=VALUE ICD9

SEND-DIAG-ICD10-FORMAT=VALUE ICD10

SEND-DIAG-ICD9-FORMAT=VALUE 9

SEND-DIAG-ICD10-FORMAT=VALUE 0

The user specific literal identifying the diagnosis code for both ICD-9 and ICD-10 versions can be defined to be sent in the DG1-03.3 and/or in the FT1-19.3 HL7 fields for each diagnosis code for outbound interfaces.

When dealing with HUB inbound interfaces, if the DEFAULT-DIAG- FORMAT entry is not defined and the inbound HL7 message doesn’t identify the ICD format in DG1-03.3, then the interface update modules will process the diagnosis code associated with the received inbound order in accordance with the setting of the global ICD version flag.


LAB_NFG_V7.3.0_1 1-9

LAB Interface Update Processor ModulesThe LAB Interface Update Processor modules use the ICD version defined in the format field of the incoming order record to determine the format of the incoming diagnosis code prior to its processing and storage in the sample record. If the value defined in this format field is blank, then these modules will use the global ICD version flag to process the incoming diagnosis code.

LAB Interface Outbound Preparation Processor ModulesThe LAB Interface Outbound Preparation Processor modules pass the ICD-9 value in the format field in the outbound record associated with any sample that is generated prior to the official cutover to ICD-10, otherwise these modules pass the ICD-10 value in the format field in the outbound record, for the HUB outbound module to process the record to send the appropriate value in the DG1-03.3 and/or FT1-19.3 HL7 field.

It is important to remember that the only way to accurately test the ICD-10 implementation is to enable ICD-10 support in your test environment prior to the official government deadline. Note that once this switch is set it cannot be reversed. Your environment will permanently be set to ICD-10, however, you will still be able to access the previous ICD-9 rules, standing orders, dictionaries, collection records, and sample records as long as “Dual Entry” is enabled.

It is possible for a facility to still prepare in advance for the ICD-10 conversion without impacting workflow in the live environment with the “Dual Entry” selections as long as CyberLAB 7.3 is installed in the test environment. The facility can set up all ICD-10 related MNV rules and Standing Orders in the test environment and Aspyra support can move those databases into the live environment prior to the deadline. In other words, ICD-10 preparations can take place in either live or test environments depending on your requirements.

Enhanced Patient ReportingThe process within CyberLAB used to print, fax and email Patient Reports has been enhanced with options that allow you to design and build reports that contain specialized content and new formatting displays. Included among the new options are: Previous Results, Abnormal Summary, Alternate Abnormal Flagging, enhanced Microbiology Columnar format with Antibiotic Sorting and Sensitivity Translations, Column Sub Heading Placement after Ordered Tests, Heading and Footing Bookmarking and Line Type formatting with column positioning using tab stops, and Macro controlled formatting.

The configuration for the additional content portion of these reports is set up in the Report Parameters section of CyberLAB accessed through File Maintenance > Report Maintenance.

Configuration for the additional content portion of these reports is set up in the Report Parameters section of CyberLAB. Access to this section is through the CyberLAB menu as illustrated below:



Figure 1-9: CyberLAB Main Screen

Previous ResultsUp to three columns of previous single test results can appear on a report with column headings that can be configured to contain the Collection Date, Collection Time and Sample number. The subheading for the column containing the current results can also be configured to contain the sample number and collection date. The configuration for Previous Results is set up in Report Parameters.

How do I configure Previous Results?

1. Navigate to the Report Parameters Options screen; indicate the report type you wish to edit; select any associated options that will pertain to these edits, and click OK. A configuration screen for the selected report displays.

2. Select Miscellaneous Parameters from the available drop-down list and click OK.


LAB_NFG_V7.3.0_1 1-11

3. Use the Next button to advance to the eighth page of Miscellaneous Parameters where the Previous Results option displays at the top of the list.

4. Set the Include Previous Results drop-down to “Yes.”

5. Select the format for how the Collection Date and Time will appear below the test results subheading.



6. Indicate how many blank lines to print between the subheading and the Date and Times.

7. Indicate the starting column character for the Collected Date and Time location in the subheading for each Previous Results column you will have on the report, and, if you want it in the subheading, the starting column for the Current Date and Time.


LAB_NFG_V7.3.0_1 1-13

8. If you wish the actual Sample Number to print above the configured Date and Times in the first heading line, you must return to the first page of the Miscellaneous Parameter options and embed tags for the sample numbers (@@SAMPLE0, @@SAMPLE01, @@SAMPLE2, @@SAMPLE3) in the heading line.

The position of the columns holding the previous results is set up in the Body Field parameters and should line up with the appropriate subheadings. The absence of a position number will exclude the previous result set.

9. Once you have completed all the edits to the Miscellaneous Parameters screens, click the Accept button to record and implement the changes.

Abnormal Summary This is a section at the end of the report that includes only tests that were flagged as abnormal with the regular body of the report. This feature can be turned on or off by a “Yes” or “No” selection.

Figure 1-10: Abnormal Summary Flag Setting Option

The Abnormal Summary can also be configured with a subheading line in addition to the regular Test subheading with the option for the summary to appear on a separate page or separated by 1, 2, or 3 lines after the main body of the report.



Figure 1-11: Abnormal Summary Line Position Option

Alternate Abnormal FlaggingThis feature, turned on or off by a selection of “Yes” or “No”, allows for alternate flag values to print on the report and provides a way of grading the degree of the High and Low ranges by indicating on which side of the mid-point of the range the result falls. For example, if the High range for a test is 10-20 mg, the mid-point of this range is 15 mg. Using the configuration pictured below, if the result is in the range of 16-20, it would be flagged with “++”, whereas a result in the range of 10-15 would be flagged with “+”.

Figure 1-12: Alternate Abnormal Flagging Configuration

Enhanced Microbiology Columnar FormatIf the global configuration for Microbiology Results are to be reported in a columnar format, then the following enhancements will apply. When printing in a columnar format, Sensitivities will be reported in a table format with the Antibiotics down the left hand side and the Organisms identified horizontally across the top. The Order that the Antibiotics appear are determined by the selection of the “Antibiotic Sort Type”.

Figure 1-13: Antibiotic Sort Type Options

• Default (Alphabetic) - the Antibiotics will be sorted by their three character code in alphabetic ascending order.


LAB_NFG_V7.3.0_1 1-15

• Sort Value - the Antibiotics will be sorted by a three-digit sort number assigned to each Antibiotic in ascending order. The sort number is set up in the Antibiotic Code Maintenance program in the Instrument Options field.

Figure 1-14: Microbiology Antibiotic Code Maintenance Screen

• Sort Value + Sensitivity - the Antibiotics will be sorted, in ascending order, by a three digit sort number that is the sum of the sort number and a numerical representation of the sensitivity result (R=1, I=3, S=4 and blank =12). The sort number is set up in the Antibiotic Code Maintenance program.

• Preferred + Sensitivity - the Antibiotics will be sorted, in ascending order, by a three digit sort number that is the sum of an Organism/Antibiotic specific sort number (a default sort number will be used if the summed Organism/Antibiotic specific number does not exist) and a numerical representation of the sensitivity result (R=1, I=3, S=4 and blank =12).

The sort number is set up in the Antibiotic Code Maintenance program as follows: (Default Code (3 characters) “-“ Organism Code (3 characters “:” Preferred Sort Number (3 digits)). The Organism sequence can occur up to five times. The below example shows AMP (AMPICILLIN) with a default sort number or 010 and a preferred sort number of 005 for EC (ESCHERICHIA COLI) and 001 for PSA (PSEUDOMONAS AERUGINOSA).

Figure 1-15: Sample of Antibiotic Preferred + Sensitivity Code Setup

Additionally, a Sensitivities Code (up to four characters) can be translated into a 12 character word. Organism Identification result lines can have up to 15 characters appended to them and the Source and Site descriptions can be configured with a Label. These configurations can be found on the last page of Miscellaneous Parameters within Report Parameter Maintenance.



Figure 1-16: Parameter Set [Default] Interim Report Screen

See Figure 1-17 below for an example of the enhanced reporting features.

Figure 1-17: Microbiology Results on Patient Report Sample


LAB_NFG_V7.3.0_1 1-17

Column Subheading Placement after Ordered TestsThe Column Subheading Placement after Ordered Tests feature is another option that can be turned on or off with a “Yes” or “No” selection. Found on the fifth page of configuration options in the Miscellaneous Parameters section of Report Parameter Maintenance, this new feature, when turned on, causes the test results subheading to print after each Ordered Panel Test on the Report.

Figure 1-18: Column Heading after Ordered Panel Test Selection Field

Figure 1-19: Sample Report with New Column Subheading Placement Displayed

Heading and Footing BookmarkingYou may now pass heading and footing information to the DDS for insertion into predefined template bookmarks, allowing for any combination of font characteristics for each bookmarked field. This gives the Lab maximum flexibility in designing their Patient Reports. This option is turned on when “Yes” is selected for the “Pass Bookmarks to DDS” prompt found on the eighth page of Miscellaneous Parameters within Report Parameter Maintenance.

Figure 1-20: Pass Bookmarks to DDS Selection Field

The bookmark data that is passed to the DDS is determined by the entries in the “Report Header Fields” and “Report Footer Fields” sections in Report Parameter Maintenance. The row and column entries for this type of report do not need to be accurate, but are required for the field to be passed to the DDS.

This type of report does not work for local printing through Patient Inquiry. A separate Report Parameter setup is required with the above option turned off, and the code assigned to this format must be set up in “General System Parameters” under the “Features Tab” in the “Report Parameter Set ID to Print Report via Web Gateway” field.



Below is a table of the possible bookmarks that can be used in the Heading section or the Footing section of the Microsoft Word Document Template. Bookmark names will be preceded by an “H” for Heading or “F” for Footing.


LAB_NFG_V7.3.0_1 1-19




LAB_NFG_V7.3.0_1 1-21

Line Type FormattingThe Line Type Formatting option is turned on when “Yes” is selected for the “Pass Bookmarks to DDS” prompt and works in conjunction with the Heading and Footing Bookmarking option described above. This feature will pass line type numbers to the DDS for every line within the body of the report, which allows for specific formatting of that line type by the DDS. The Line types are listed below:



The formatting of the Line Types occurs within the DDS and is set up in the DDS Templates section. The important thing to remember is that the DDS will take sections of the line that the CyberLAB printing process creates and locate and format accordingly, based on the Line Type Number. String changes are set up as usual using the Fonts tab. The setup and configuration of the DDS is an advanced option and should be conducted by ASPYRA Support. Below is an example of a Patient Report Template configured to show bookmarks.


LAB_NFG_V7.3.0_1 1-23

Figure 1-21: Patient Report Template Configured to Show Bookmarks

Figure 1-22 provides an example of the finished completed Patient Report as it would appear when actually printed, faxed or emailed.



Figure 1-22: Finalized Patient Report Ready for Distribution

There are other, optional features available to the printed report that can be configured by ASPYRA. Please contact the ASPYRA Sales Department for further information.

Urinalysis Alpha Results EnhancementUrinalysis Alpha Results now use the alpha results cross-reference table that is already available for Single Test Alpha Results, which is built and maintained in the Report Parameters Maintenance program.

When setting up possible results for components of a Urinalysis Console Test, you are limited to five characters for an alpha result, as illustrated below:


LAB_NFG_V7.3.0_1 1-25

Figure 1-23: Physical and Micro Parameters Screen

When entering results for a Urinalysis Console Test, a drop-down list presents the possible results that can be entered for a component of any test. If the result is set up in the Alpha Conversion Table in Report Parameter Maintenance, it will be translated on the Patient Report and in Patient Inquiry, as illustrated below:

Figure 1-24: Report Parameters Set Up



Figure 1-25: Successful Cross Reference Set Up Displayed in Patient Inquiry

FAX / Email Restricted Tests EnhancementPatient Inquiry has been enhanced to allow the Fax or Email of samples with restricted tests based on a User Class Function Specific Access configuration. If your user class permits Fax or Email options and the “Allow Fax/Email Restricted Tests” feature is turned on, you will be able to force Fax or Email a patient report with restricted tests.

This Function Specific Access configuration can be found in User Class Maintenance for Patient Inquiry.


LAB_NFG_V7.3.0_1 1-27

Figure 1-26: User Class Function Specific Access Options for Patient Inquiry

With this feature engaged, you will not be able to see a restricted test in Patient Inquiry as usual, but you will see the Fax or Email options on the print tab.

Extended Range ConfigurationYou may now configure Instrument Result Editing to use Device and Address specific Extended Ranges, thus giving you more latitude and when resulting tests.

To set up an Extended Range for a device/address, a range ID must first be created for the specific instrument. This is accomplished in Range ID Maintenance, which is an option with Test Dictionary Maintenance (File Maintenance>Database Maintenance>Test Panel Main- tenance>Test Dictionary Maintenance).

Figure 1-27: Range ID Maintenance Screen Sample



To then define an Extended Range for any test that will be run on the device, the individual test itself must first be configured to use extended ranges. This process too is performed in Test Dictionary Maintenance under the Test Maintenance option.

Figure 1-28: Test Maintenance Option with Designated Test Code Example

Following the designation of a specific test, the Test maintenance screen displays, enabling you to set the range type to “Extended”.

Figure 1-29: Test Maintenance Screen with Extended Range Type and Subsequent Extended Ranges Tab

The instant you select “Extended”, the Extended Ranges tab (see Figure 1-29 above) displays. Select this tab to access the screen that enables you to enter Test Results by Range ID.


LAB_NFG_V7.3.0_1 1-29

Figure 1-30: Test Result Ranges by Range ID Edit Screen

When editing results for Tests that were run on an Instrument defined to have extended ranges, the result will be flagged using the extended ranges and the range is carried along with the result.

Figure 1-31: Edit Live Results Screen

Worksheet Cleanup and Performance EnhancementCyberLAB 7.3 now allows you to clean up old records based on a new all-sites prompt.



Figure 1-32: Options Screen with Sites Drop-down List

The programs for Worksheets and Pending Work Reports have been modified to enhance their performance by streamlining the internal sorting and selection criteria.

Figure 1-33: CyberLAB Main Screen Selection Menus

Collection Verification StreamlinedCyberLAB has eliminated the extra patient demography verification step, when not required. No longer will the patient demography screen display by default during Collection Verification, but only when the order has been received through an interface and the demography modified by that interface.


LAB_NFG_V7.3.0_1 1-31

Figure 1-34: Collection Verification Screen

When the demography screen does display, it appears similar to the following:

Figure 1-35: Demography Verification Screen

Updated CyberLAB User InterfaceEnhanced CyberLAB Login Screen and Main Menu FunctionalityThe appearance of the Login window and Program Selection divisions have been updated to achieve compatibility with Internet Explorer 10.



Figure 1-36: Login Window and Main Menu Screen

When using Internet Explorer (IE) 10 it is required that it be in Compatibility View, which can be set up in the Tools menu by selecting Compatibility View. You can contact ASPYRA Support for instructions on how to configure this setting and other recommended IE settings. CyberLAB 7.3 is backwards compatible with other IE versions, enabling users of older IE applications to access, use, and enjoy CyberLAB’s new features and refreshed appearance.

Modified Interface CyberLAB has undergone a visual refresh that includes:

• Updated page color

Enhanced with a white background and foreground colors of black, blue, green, and grey, the CyberLAB interface incorporates a modern look with a restful viewing experience.

• A new interface font

An updated font provides a cleaner interface and improved legibility.

• Crisp, smooth button faces

Building upon the change in font, CyberLAB’s buttons now display more clearly.


LAB_NFG_V7.3.0_1 1-33

Figure 1-37: Sample of CyberLAB Interface Updates

Search Icons Replace Double-Click Text Box FunctionSelection boxes used to quickly populate text boxes throughout CyberLAB are now accessed using the magnifying glass search icons located at the right of designated fields. This action replaces the previous practice of double-clicking within the associated field to invoke a separate window that displays the selections, as the list is now an actual part of the page from which it was requested. Additionally, the selection boxes visually reflect the updated GUI themes and, when accessed, are now positioned off of the input field from which they are invoked rather than displaying arbitrarily across the screen.

To further simplify the use of the selection boxes, each is now equipped with a scroll bar and the number of displayed entries can be controlled through a global configuration. (For more information about this configuration option, contact your CyberLAB Service Representative.)



Figure 1-38: Sample of New Selection Box

Interactive Calendar Updated and more easily navigated calendar pop-ups, now contain a new “Today” date selection feature. The calendar renders much more quickly as it is no longer a new window that displays over the application, but is in fact, a static expansion of the open interface. While the invoked calendar cannot be moved about the screen, it is more responsive than previous versions.

Figure 1-39: Sample of New Calendar Icon and Popup

Improvements and Corrections

LAB_NFG_V7.3.0_1 1-35

Improvements and CorrectionsThis section details corrections and improvements made to the CyberLAB system version 7.3.0:

• A correction was made to the Call History Log Reporting module to prevent an error from appearing which was preventing the Log Report from processing when filtering by Ordering Doctor. The program was issuing an alert stating “ordering doctor cannot be blank” even though the order doctor field is not shown on the screen. This occurs on the open screen when selecting the report criteria. Included in this defect was the correction to always show the result and flag information on the comment line on the Log Report. This was not occurring for certain log record types.

• The Patient Order Processing module was corrected to prevent the issue of a SQL error being generated and terminating the process when deactivating samples with certain ordered test combinations including Microbiology type tests.

• Corrected the behavior of the Patient Entry Program when auto assignment of “GA” modifiers is configured. This configuration applies only to patients with a Bill type of Medicare, the modifier was being replaced with the Diagnosis Code when patients were not Medicare.

• Corrected the Client Master Entry program so not to allow the creation of blank client database records.

• Corrected default options in General System Parameters entry screen to default to “No” instead of “Yes” for the following configuration fields: Use all Bill types for MNV Rules; Payers for all Bill Types for MNV Rules; MNV Rule Failures in Held Status; Fax MNV Waiver; Fax Authorization Request; Print Medicare MNV Waivers Only.

• Corrected the Result Response Rule Maintenance Program so when a rule is deleted it will be automatically deleted from any Rule Panel that it was part of. This prevents Result Response processing from trying to run a blank rule.

• Corrected the process used in all Microbiology Results Entry Programs to generate Billing Only Tests Codes, for Samples with a Culture Test type ordered, based on Organism Identification, Biochemical Testing, Workup Setup Codes and Sensitivity Panels for multiple isolates. The issue was that randomly not all the Billing Only Tests were being generated for Samples with multiple isolates when the billing method was not configured to use the Accumulation method. Now when using the Decision Support Billing method, all Billing Only Tests Codes are applied to the Sample based on the configuration and the number of isolates.

• Corrected the Matrix Results Entry Program so it will advance past the first worksheet when there are unresulted tests remaining on it. It was only advancing when all tests for the worksheet were resulted.

• Corrected the loss of decimal precision when reporting results. This was a very low frequency, random occurrence at only one Lab with a very specific Result Out interface configuration.



• Corrected the Medical Necessity Rules maintenance program to display the field label correctly for insurance type when copying the rules from one insurance type/insurance code to another.

• Corrected the issue where the Edit Instruments Results Module was hanging when an abnormal result was submitted when Call features were disabled.

• Corrected Collection Verification check for the existence of the Patient Auxiliary Demography record before deleting when changing Patient ID to prevent abnormal program termination.





In This Chapter...






Email Notifications Based on Interim Report Rules................................................................... 2-3

Email Authorization Request Forms ........................................................................................... 2-10

Email Options Tied to User Class ............................................................................................... 2-11

Patient Orders Entered Using New Rapid and Batch Options............................................... 2-13

Collection Verification Now Includes Notifications of Required Account Information Changes ............................................................................................................................................ 2-19

Encrypted User Password Field ................................................................................................... 2-22

Patient Report Faxing Configurations ......................................................................................... 2-22

Viewable Sample and Collection Comments Fields in Microbiology Results....................... 2-23

Single Result Entry Displays Sixteen Samples Per Page ........................................................... 2-25

Enhanced Automatic Tech IDs .................................................................................................... 2-26

Organism Workup Comments Deletable from Held State ...................................................... 2-27

Interim Reports Can Display Client Route ................................................................................. 2-27

New Patient Held Report Required Fields and Sort Options.................................................. 2-28

Web Gateway Security Enhancements ........................................................................................ 2-28

MNV Waiver for Printing Medicare Bill Types .......................................................................... 2-29

CyberLAB Supports Label Printing by DYMO Label Writers................................................ 2-30

Web Gateway Order Entry Prints Requisition Forms .............................................................. 2-30

CyberLAB Library of Custom Reports using Microsoft SQL Services ................................. 2-30


LAB_NFG_V7.3.0_1 2-3

Email Notifications Based on Interim Report RulesCyberLAB now supports the automatic generation of email notifications for distribution of Patient Reports by Client. Based on Interim Report Rules, this enhancement enables you to configure a single email time slot for use in generating and sending email notifications for a range of distribution types.

Among the email distribution types is “Report as an Attachment.” This is the only option in which an actual PDF formatted patient report is clipped to the email message, and the only one for which protection of HIPAA sensitive information is a concern. When a patient report is attached to an email, security and encryption of HIPAA and any other confidential data is the responsibility of the Email Server.

Email Distribution Type Result

Report as Attachment Produces and transmits an email notification with a PDF formatted version of the Patient Report affixed as an attachment.

Notification Only Produces and transmits an email notification informing addressees that a Patient Report has been printed, faxed, or is available for viewing/printing through the Web Gateway.

Notification with Interface Simultaneously generates a general notification email and a PDF formatted Patient Report. The email is transmitted to the designated addressees, informing them of the PDF’s existence, while the PDF is copied to a predetermined Report Depository where it is available for secure, electronic distribution.

Table 2-1: Email Distribution Types



Configuration for this option is conducted in the Client Master Maintenance Program under the Autotransmit tab.Using the available email tools, you can add a new email time slot or change/edit an existing time slot.

CyberLAB only supports the creation of a single email time slot per client, but this slot enables you to designate a specific recipient and up to nine addition “cc” addressees for the selected email distribution type.

How do I add an email time slot?

1. Navigate to the Client Master Maintenance - Options screen (File Maintenance > Database Maintenance > Client Master Maintenance), designate the Client ID and/or Client Name and click OK.

No Notification with Interface Generates a PDF formatted Patient Report and copies it to a predetermined Report Depository where it is available for secure, electronic distribution. When using this distribution type, no email notification is produced.

Notification Criticals Only This distribution type is specific to Patient Report results and automatically notifies the addressees when test results fall within the critical range. The report is not attached to the notification but rather created and copied to a predetermined Report Depository.

Email Distribution Type Result

Table 2-1: Email Distribution Types


LAB_NFG_V7.3.0_1 2-5

2. When the General information screen for the selected client displays, select the Autotransmit tab.

A screen similar to the one displayed above appears.

3. Set the Autotransmit drop-down (shown highlighted) to Yes.

4. Click the Add E-Mail Slot button (shown highlighted) to invoke the Edit Time Slot screen to configure the address(es) and email distribution type.

If an email time slot has already been created, selecting the Add Email Slot button generates a warning informing you that an active email slot currently exists and that the system can only support one per client.



5. The Add Email Slot screen contains a series of editable fields that enable you to designate the actual time during which emails can be sent; the phone number of the sending party; the inclusion of Confidential Reports; the Email Distribution Type; the reports location folder; the email address of the main recipient; and up to nine email address slots for “cc” recipients. Edit the necessary fields and click OK.

The Phone Number field is mandatory and should be unique to the client. Should you overlook this field in editing, any attempts to save the screen contents will result in a warning message reminding you that a phone number is required.

How do I change an existing email time slot?

1. Navigate to the Client Master Maintenance - Options screen (File Maintenance > Database Maintenance > Client Master Maintenance), designate the Client ID and/or Client Name, and click OK.


LAB_NFG_V7.3.0_1 2-7

2. When the General information screen for the selected client displays, select the Autotransmit tab. The Client Master Maintenance - Options screen appears, displaying the currently configured Email and FAX time slots.



3. Double-click the email time slot entry to access the associated Edit screen.

4. Using the available data fields, make the necessary changes and/or additions to the selected email slot.

5. When you have completed your edits, click OK to record the changes and close the edit screen.

Email Configuration and CustomizationWhether the email is automatically generated via Interim Report Rules or forced through Patient Inquiry, the body of the email and the affixed signature can be customized through Email Distribution Type and Sample Status. The configurations for these customizations are conducted in the Client Master Maintenance Program under the Email Body Setup option.


LAB_NFG_V7.3.0_1 2-9

Figure 2-1: Client Master Maintenance Screen - Email Body Setup Option

Accessing the Email Body Setup option provides access to a host of configuration preferences that include Signature and Notification text.

Figure 2-2: Email Signature Text Screen



Figure 2-3: Email Notification Text Screen

Bookmarks can be added to the Notification Text enabling specific sample and patient information to be added to the body of the Email. Options for each Email Distribution type are further subdivided by sample status: Preliminary or Final and Corrected.

Email Authorization Request FormsAlso included in the CyberLAB email notification enhancements is the ability to email authorization request forms to insurance payers using the Order Entry Decision Support Rules. While this automated notification process was once limited to only FAX and Print requests, you now have the option of designating an email authorization request which is automatically generated.

Simply navigate to the Payer Maintenance screen (File Maintenance > Database Maintenance > Order Entry Decision Support), access the drop-down list adjacent to the Template field, select Email Authorization request, and click OK.


LAB_NFG_V7.3.0_1 2-11

Figure 2-4: Payer Maintenance Screen

Email Options Tied to User ClassThe CyberLAB email enhancement additionally contains the option for configuring Patient Inquiry based on User Class security settings, and enables the authorized user to force a Patient Report via an email as an attachment.

When the Function-Specific Access screen for a selected user is invoked and the Patient Inquiry function is selected, the two email options for User Class are available for selection:

• Disable Email Option - this will prevent the Email option from appearing in the Patient Inquiry. This cannot be selected if the user class is intended to have the email option from Patient Inquiry.

• Disable Email Address Entry - this will only allow the email to be sent to the address configured within the Client Master for the client associated (ordering doctor) with the sample. If this is not selected, then the user class can enter the address. The address set up for the client is displayed as the default.



Figure 2-5: User / Class Maintenance - Function-Specific Access Screen

If email is allowed, the option to use it is found on the Print tab within Patient Inquiry when viewing a specific sample.

Figure 2-6: Patient Inquiry - Print Tab Screen (Distribution Method Drop-Down)

Select Email from the Distribution Method drop-down list. This selection causes the email address currently associated with this patient record to display.


LAB_NFG_V7.3.0_1 2-13

Figure 2-7: Patient Inquiry - Print Tab Screen (Email Field)

You may use the default address or enter a new one and then force the message by clicking Print.

Patient Orders Entered Using New Rapid and Batch OptionsCyberLAB Patient Entry now provides two new Patient Orders entry methods: Rapid Entry and Batch Entry.

Rapid Entry allows the user to enter batches of samples with minimal Patient Information and is best suited for the laboratory that needs to enter large quantities of samples slated for the same battery of tests and possessing only one or two sample identifiers plus the ordering Client. Rapid Entry can be configured to repeat tests ordered and Ordering Client for each new sample entered.

Batch Entry provides the same options as Rapid Entry but also gives the user the option of entering all sample and demographic information for the order at the time of entry. It can also be used to update sample and demographic information for orders originally entered using Rapid Entry because it provides access by batch number as well as the sample number for existing orders. Batch Entry can additionally be configured so that Patient Demography information is not required at entry except for the minimal amount necessary to create a new record for patients not already in the data base.

Both Rapid and Batch Entry allow for the assignment of a tracking number and client number for the batch. Also included in this enhancement and applicable to both new entry options are background queuing mechanisms that allow for the creation and distribution of batch reports by client based Interim Report Rules. A SQL Report template is also included with this feature, enabling a matric-type report with multiple rows of samples and multiple columns of tests for each Client batch.



Figure 2-8: Sample Batch Report

Designating Patient Entry Type Navigate to the Patient Entry - Default Options screen (Patient Entry/Inquiry > Patient Entry/Maintenance) and select the desired Patient Entry method from the Patient Entry Type drop-down list pictured in Figure 2-9 on page 2-15.

If either Rapid Entry or Batch Entry is selected, the adjacent Batch ID field appears displaying the number of the last batch created for the current date. The eleven digit batch number is generated using the date the batch was created and a sequence number (yyyymmdd001).


LAB_NFG_V7.3.0_1 2-15

Figure 2-9: Patient Entry - Default Options Screen

Double-click the number displayed in the Batch ID field to invoke the Patient/Sample Batch Entry screen shown in Figure 2-10 on page 2-15.

While the system defaults to the last batch number generated, it is easily changed. Simply click inside the Batch ID field and type the number of the batch that contains the samples you wish to review.

Figure 2-10: Patient/Sample Batch Entry Screen

This screen displays the listing of existing batches beginning with the one designated in the Start at field at the top. The Start at batch number corresponds to the Batch ID designated on the Patient Entry - Default Options screen and can be changed at either location to reorder the displayed batches.



How do I Enter Patient Orders Using Rapid Entry?

1. Navigate to the Patient Entry - Default Options screen (see “Designating Patient Entry Type” on page 2-14 of this guide) to select Rapid Entry as the Patient Entry type.

2. Once you have selected Rapid Entry from the available drop-down (see Figure 2-9 on page 2-15), click the OK button at the screen’s lower left to invoke the Rapid Batch Entry screen:

The screen is divided into three frames: the Main Entry, where patient and ordered test data is recorded; the Test Selection List, where tests ordered for the patient are displayed; and the Batch Contents List, which displays every order contained within the batch.

When selecting the Rapid Batch Entry option, you may create a new batch for the orders you are creating by using the Batch ID number that automatically displays, or you may add the orders to an existing batch by physically changing the default number.


LAB_NFG_V7.3.0_1 2-17

3. Use the data fields located at the screen’s upper left to quickly enter the necessary patient order information. As tests are added to the order, they display in the Test Selection List frame at the upper right of the screen.

Double-click entries displayed in this list to return them to the main entry area from where they can be individually updated or deleted from the order.



4. Once all required tests for the patient are entered, thus completing the order, click the OK button in the Main Entry frame.

The order is added to the Batch and listed in the Batch Contents List frame at the bottom of the screen, while the Main Entry area is cleared of patient specific data, repopulated with the Batch ID; next available Sample ID; the last entered Tracking Number; Collection Date, Time, and Tech; and Lab Received Date, Time, and Tech.

If the Repeat Client option is turned on, the Client ID and Name will be repopulated with the last one entered. If the Repeat Tests option is turned on, the Test Selection List will be repopulated with the last entered list as well as sample comments and collection comments. The Diagnosis fields will not be repopulated.

MNV rules or Decision Support rules do not apply to Rapid Batch Entry. The behavior of Patient ID and Name in Rapid Entry is governed by the existing configurations set for regular Patient Entry.

How do I enter Patient Orders Using Batch Entry?

Batch Entry looks and performs much like regular Patient Entry but is enhanced with configuration options that allow it to mimic the behavior of Rapid Batch Entry. This added flexibility enables you to quickly create a new record without requiring the immediate recording of detailed patient demography.

1. Navigate to the Patient Entry - Default Options screen (see “Designating Patient Entry Type” on page 2-14 of this guide) to select Batch Entry as the Patient Entry type.


LAB_NFG_V7.3.0_1 2-19

2. Once you have selected Batch Entry from the available drop-down (see Figure 2-9 on page 2-15), click the OK button at the screen’s lower left to invoke the Batch Entry screen:

The identification information required to complete new patient entry depends upon the Function-Specific Access for your assigned User Class. If it is set to “Skip Demog Entry in Batch Entry,” then the program will not navigate to the Demography Entry screen, but will create a patient record using only the information entered at the upper portion of the Batch Entry screen. If the User Class is not configured this way, the system will advance you to the Demography Entry Screen to record more complete patient information.

3. Once the demographic data is recorded, enter the rest of the order information, and then select Done to complete the order. This will return you to the demography area where you will be able to quickly create another batch order of the same tests for a different patient.

Collection Verification Now Includes Notifications of Required Account Information Changes

Collection Verification now includes warnings that inform users when Custom Questions, Demography and Billing updates, Patient ID, and Visit ID changes or merges are required for orders originating from HIS or EMR interfaces.

As a result of this enhancement, samples assigned a priority sample type code will appear on the Sample Verification list with their priority code description (such as STAT) colored red. Also displayed in red are notices for samples requiring review of Custom Questions or



Demographics (see Figure 2-11 on page 2-20). This highlighting serves to remind the user that certain entries lack necessary information, which must be included before samples can be collected.

Figure 2-11: Sample Verification List Screen

The Custom Question test feature has been added to Collection Verification to permit review of questions and answers received from an inbound orders interface. The screens and functionality are the same as those found in Patent Entry/Maintenance.

Any unanswered questions that are defined as having a required answered must be answered before the sample can be collected.

When a test having Custom Questions is manually ordered on the sample in Collection Verification, the Question/Answer screen is presented for completion.


LAB_NFG_V7.3.0_1 2-21

Figure 2-12: Custom Questions Screen

When the “Review: Demography” literal is shown for a sample, it is a warning for the user to review the patient’s demographic data. It may also mean the sample’s Patient ID should be evaluated and changed if necessary. In some instances, an orders interface may send the patient demographic data under a temporary Patient ID which must be changed when the sample is collected.

If the Patient ID is subject to change, a button labeled Change Patient ID appears at the bottom of the View Demography tab screen (see Figure 2-13 on page 2-22).



Figure 2-13: Collection Verification - View Demography Tab Screen

Encrypted User Password FieldCyberLAB has enhanced its security features by encrypting the User Password field in the user profile record. This renders the password field invisible when viewed through User Class Maintenance, SQL Studio Manager, or KEYIDX, thereby further securing user passwords and subsequently protecting the system.

Patient Report Faxing ConfigurationsNew Report Faxing configurations enable you to designate the application of cover sheets and connection for batched reports. Applied in the Client Master Data Base, these faxing options allow you to designate a single cover sheet and connection for the entire report batch or generate a individual cover sheet and connection for each included report.

How do I Configure Report Faxing Options?

1. Navigate to the Client Master Maintenance - Options screen (File Maintenance > Database Maintenance > Client Master Maintenance).

2. Enter the ID number or Name of the client for whom you are configuring the report faxing options and click the OK button.

3. At the resulting client screen, select the Autotransmit tab.


LAB_NFG_V7.3.0_1 2-23

4. Use the FAX Options drop-down to select the desired option: Normal FAX Operation, Cover page per report, or One report per connection.

5. Click the OK button at the bottom of the screen to save your selection.

Viewable Sample and Collection Comments Fields in Microbiology Results

Sample and Collection comments entered or updated at Order Entry time using Patient Entry or Collection Verification are now displayed in viewable fields within the Microbiology Results Entry and Microbiology Specimen programs. This innovation provides the microbiologist responsible for processing the specimens with greater information and detail about the samples. Each program now displays a new “Sample Text” tab that contains the new, read-only comments field.



Figure 2-14: Sample Text displayed in Microbiology Results Entry Program


LAB_NFG_V7.3.0_1 2-25

Figure 2-15: Sample Text displayed in Microbiology Specimen Login Program

Remember that these new sample text fields are read only and cannot be edited from either Microbiology program.

Single Result Entry Displays Sixteen Samples Per PageThe number of samples visible per page in Single Result Entry has been increased from seven to sixteen, thus providing a more comprehensive and comparative catalog of reviewable sample entries.



Figure 2-16: Single Result Entry Screen with Increased Sample Display

Enhanced Automatic Tech IDsCyberLAB has increased the number of automatically assigned Tech IDs from 2704 to 4900, thus providing you with a virtually inexhaustible complement of system generated and tracked identifiers.

While this enhancement improves the issuance and tracking of Tech IDs in association with User Profiles, its usage is not mandatory, as you may still choose to assign custom Tech IDs and maintain separate assignment logs.

Simply navigate to the User/Class Maintenance screen (File Maintenance > System Parameters > Tech ID/Security Maintenance > User/Class Maintenance), enter the User ID of the individual to whom you are assigning a Tech ID, and click the OK button. The User/Class Maintenance screen for the designated user displays along with a Tech ID assignment dialog (see Figure 2-17 on page 2-27).


LAB_NFG_V7.3.0_1 2-27

Figure 2-17: User/Class Maintenance Screen

The dialog provides you with three choices:

• A - when selected, the next available system generated Tech ID code is assigned and the user profile is saved.

• E - when chosen, the dialog closes and the navigation returns to the user profile screen enabling you to enter a custom Tech ID code.

• X - this option closes the dialog and profile screen, discarding any profile modifications made to the profile.

Organism Workup Comments Deletable from Held StateCyberLAB enhancements now enable you to delete Organism Workup comment text when the specimen is still in a Held state and have that deletion reflected in the Live state once the specimen is released. Previously, text added in the Live state could only be changed or removed in the same state using the Edit Live option.This new capability eliminates the redundancy of removing text from both the Held and Live state sample.

Interim Reports Can Display Client RouteClient Route is now available for inclusion on printed Interim Reports. This new feature is a useful tracking tool when the distribution routes assigned to Patient Reports are based on predetermined codes set up in CyberLAB’s Client Master Maintenance, as it provides instant identification of the route to which the printed report is assigned.



New Patient Held Report Required Fields and Sort Options To better track and audit Samples and Individual Tests that are in a held status pending the receipt of authorizations or ABN Waivers, CyberLAB has added new Report Required fields that allow the recording of additional data while providing new report filtering options.

New required fields include Date of Service, Client ID, Client Name, Client Phone, Payer Code, Payer Description, Test Code, Test Name, and Reason for Hold, each of which can in turn be used as a sorting criterion when generating the Patient Held report.

Figure 2-18: Example of New Patient Held Report Required Fields and Sort Options

Figure 2-19: Held Sample/Test Report

Web Gateway Security EnhancementsCyberLAB’s increased Web Gateway security enables client selection and input to be restricted by User Class Group Codes in Patient Entry. This enhancement incorporates into Patient Entry/Maintenance the client filtering functionality currently present in Patient Inquiry and provides administrators with more control in maintaining a smooth, non-redundant workflow.


LAB_NFG_V7.3.0_1 2-29

Client filtering is automatically enabled when a user’s profile is defined with an Inquiry Client ID or Inquiry Group, an example of which can be seen in Figure 2-20 on page 2-29. The User Maintenance screen depicted shows a user with a client restricted account, which limits the user to viewing patients and samples and entering new orders only for Client ID 5.

Figure 2-20: User/Class Maintenance Screen

While this feature applies to both Full Access Users and Web Gateway Users, it is primarily implemented for Web Gateway users.

MNV Waiver for Printing Medicare Bill TypesCyberLAB can now be configured to print MNV Waivers for only Medicare bill types and still allow for MNV rule evaluation to occur for other bill types that may be set up in the MNV rules, without printing the Waivers.



CyberLAB Supports Label Printing by DYMO Label WritersCyberLAB now supports DYMO Label Writers, which print barcode labels directly from a connected workstation. The flexibility of the DYMO Label Writers in using conveniently placed and available equipment makes them an idea solution for Web Gateway users.

Web Gateway Order Entry Prints Requisition FormsCyberLAB’s Web Gateway Order Entry module now allows you to print order requisition forms on a selected, workstation-attached, printer. This feature provides greater convenience and records organization by enabling the use of multiple printers rather than requiring the designation of a single printer that may be located far from your workstation.

CyberLAB Library of Custom Reports using Microsoft SQL Services

CyberLAB clients have worked with ASPYRA to create custom reports using the Microsoft SQL Reporting Services module. Based on the CyberLAB SQL database, these reports encompass a variety of subjects that include multiple variations of Ordered Tests, Test Samples, Billing, and even Courier Schedules. In CyberLAB 7.2.11, ASPYRA is in the position to offer custom management reports that fit a laboratory’s requirements, utilizing the current library and the designs submitted by our Clients. To review samples of the current report portfolio, refer to “Exhibits” on page A-1 of this guide.


• Modified the Patient Inquiry module so that it will disallow the forced printing of incomplete Cytology results for samples linked to a CyberPATH case number.

• Corrected minor screen format issue within alpha test entry in QC Dictionary.

• Corrected the issue of result values not appearing on the Call List when the results are coming from an instrument.

• Corrected the issue of no data printing on the work list if a parameter is entered below line 14 in the GOE Form Parameters.

• Corrected the behavior of the Patient Inquiry Program which goes into an endless loop under certain conditions.

• Corrected the issue of the Barcode printing program stopping the printing labels and gets hung up. Program will not respond to stop (BAKCAN) command.

• Corrected the behavior within the Patient Entry Module when adding tests to live Sample with tests held gives the error, “Sample ID used” and requires a new Sample ID to be assigned.


LAB_NFG_V7.3.0_1 2-31

• Added subhead date/time received field labels to Cumulative Report parameters section of Report Parameter Maintenance Module. Cumulative Report currently uses this field but there is no way to configure.

• Corrected the issue of Compressed Patient Reports not completing and printing when collection comments exist for a sample.

• Corrected the issue of Client restricted users being able to view minimal restricted demography information in Patient Inquiry.

• Corrected the issue of Interim Reports printing incorrect client addresses.

• Corrected the issue of Employer Information being left off the Patient Entry Screen file and out of the field arguments.

• Corrected the issue of Patient Entry Processing of Samples in Live and Held with unresolved MNV Violations.

• Modified Archive Module to correct date evaluation for unconditional archive utility.

• Corrected issue of MNV Waiver print program not printing to standard printers.

• Corrected the issue within Micro Entry of comments being lost if overflow entry with more than 12 lines of text occurs.

• Corrected the problem of bypassing records when locked for the Collection List report and the Standing Orders generate program.

• Corrected Cytology Reports from CyberPATH from printing through CyberLAB’s IRR - creating duplicate cytology reports.

• Corrected Remote printing of Bar Code Labels using the DYMO printers to support Split Sample Label creation.

• Corrected the issue of Test Interpretations being truncated when displayed in Patient Inquiry.

• Corrected the issue of CyberLAB Cytology Results not always being queued up for results out interfacing within the Cytology Results Entry Module.

• Corrected the issue where the Client Phone Number is included in the Patient Name on the ABN Waiver, if the Patient Name is less than 14 characters.







In This Chapter...






Client Master Maintenance Enhancements .................................................................................. 3-2

Test Dictionary Maintenance Enhancements............................................................................... 3-4

Medical Necessity Rules and Setup Enhancements..................................................................... 3-7

Order Entry Decision Support Enhancements ......................................................................... 3-13

Patient Inquiry Enhancements ..................................................................................................... 3-21

Patient Entry Enhancements ........................................................................................................ 3-22

Client Master Maintenance EnhancementsFeature enhancements made to the Client Master module include the following:

• Increased Field Size

• Client-Defined Requisitions Options

Increased Field SizeIn Client Master Maintenance, on the General tab, the following fields have been increased in size:

• Care Of

• Address 1

• Address 2

Beginning in version 7.2.10, you can enter up to 45 characters in these fields, which allows you to enter the full facility name, complete address, and the appropriate contact name of the facility as seen in Figure 3-1 on page 3-3. In previous CyberLAB releases, you could only enter up to 25 characters in these fields.


LAB_NFG_V7.3.0_1 3-3

Figure 3-1: Increased Field Size on Client Master Maintenance – Options Screen

Client-Defined Requisition OptionsBeginning in version 7.2.10, in the Client Master maintenance, on the General Options tab, up to five separate client-defined Requisition Forms can be configured, each with their own set of special tests and their own format. As seen in Figure 3-2 on page 3-4 click any of the following tabs to create and configure the separate client-defined Requisition Forms:

• Reg Form1

• Reg Form2

• Reg Form3

• Reg Form4

• Reg Form5

Each of these requisition forms can be unique. Please contact ASPYRA support to design and enable the forms.

Increased Field Size



Figure 3-2: 23 Requisition Forms Available

Twenty-three different requisition form formats are available for your use when designing these individual Client Requisition Forms. As seen in Figure 3-2 on page 3-4, when you click the Requisition Form drop-down list, the selection values for the form format appear, either as Undefined and beginning with “Form A” and ending in Form W. This gives you the flexibility to configure your Client Requisition forms to print any type of format to suit your Clients’ requirements and the laboratory needs.

Test Dictionary Maintenance EnhancementsThe following enhancements have been added to Test Dictionary Maintenance:

• Duplication of Test Name

• Printing of Custom Panel Test Labels

Duplication of Test Name Beginning in version 7.2.10, you can use the same test name more than once in the Test Dictionary. For example, you can use the test name, “Glucose”, as many times as needed for that same test. You may need to use the same test name multiple times if the test is performed in house and also at off-site laboratories.

Increased Number of Requisition Forms


LAB_NFG_V7.3.0_1 3-5

As seen in Figure 3-3 on page 3-5, the “Glucose” test name has been added in CyberLAB for three different test codes and appears on the Test Dictionary Selection List screen. You initially enter new test codes on the Select Options and also the Test Maintenance Panel Test screens.

Also pictured in Figure 3-3, the test name is differentiated by the abbreviation of your choice, for example:

• The letter “Q” has been added to the abbreviation to indicate that the Glucose test needs to get routed to “Quest” for testing.

• The letter “L” has been added to the abbreviation to indicate that the Glucose test needs to get routed to “LabCorp” for testing.

Figure 3-3: Duplication of the Test Name “Glucose” on the Test Selection Screen

Printing of Custom Panel Test LabelsIn previous versions of CyberLAB, when you printed labels for panel tests, the labels only had the panel test name printed on each label. If a panel test includes several components but only prints the name of the test panel, then confusion may arise for the laboratory technician who must perform a specific test for each component.

Beginning in version 7.2.10, you can now specify custom labels for panel tests. For example, the panel test that requires test labels will include several different components to test as seen in Figure 3-4 on page 3-6. In our example, the panel test for Basic Metabolic contains 11 different components that are specified and selected on the Components tab.

Test Name “Glucose” Added Three Different Times



Figure 3-4: Components Specified for Panel Test BMP

As seen in Figure 3-5 on page 3-7, on the Custom tab, when you enter a value of “CUSTOM” in the Requirements field, CyberLAB prints the abbreviation of the actual test component on the test label. Custom test labels for panel tests benefit the lab technician because the exact component is identified, which lets the technician know the specific test to perform for each test tube.

For setting up labels to print in the CyberLAB application, please contact your ASPYRA Support representative.


LAB_NFG_V7.3.0_1 3-7

Figure 3-5: Setting up Custom Panel Test Labels to Print for Panel Test BMP

Medical Necessity Rules and Setup EnhancementsThe following feature enhancements have been added to the Medical Necessity Rules module:

• Addition of Bill Types

• Addition of Payer (Insurance) Codes for All Bill (Insurance) Types

It is important to understand that the terms Insurance Code and Payer Code are used interchangeably throughout CyberLAB, as both refer to the same information. This condition also exists between the terms Insurance Type and Bill Type; both titles are used to specify identical data.

• Additional Age and Gender Rules

• Ability to Hold Samples requiring Waivers based on Medical Necessity Rule Failure

• Ability to Fax Waivers to Admitting or Attending Physicians

Addition of All Bill TypesUnder the Features tab of General System Parameters, you can now configure CyberLAB to use all Bill Types for Medical Necessity rules. You can either answer “Yes” or “No” to the prompt “Use all Bill Types for MNV Rules” as seen in Figure 3-6 on page 3-8.

“CUSTOM” value indicates printing of test component



Figure 3-6: Use All Bill Types for MNV Rules Setup

When CyberLAB is configured to use all Bill Types, then Medical Necessity Rules can be defined for every billing type listed below:

• Medicare

• Medicaid

• Other Insurance

• Patient

• Medi-Medi

• Doctor

• Doctor, No Charge

• Patient, No Charge

• Prepaid No Bill

• Prepaid with Bill

Addition of Payer (Insurance) Codes for All Bill TypesUnder the Features Tab of General System Parameters, you can now enable Medical Necessity Rules to be defined for specific Payer (Insurance) Codes in conjunction with selected Bill Types. For example, selecting “Yes” from the “Payers for all Bill Types for MNV Rules” drop-down, as shown on Figure 3-6 on page 3-8, allows you to set up Medical Necessity Rules by Payer Codes for all available Bill Types. Conversely, selecting “No” from the drop-down limits the Bill Type you may use for Payer Codes when defining Medical Necessity rules to “Other Insurance” only.

All Bill Types for MNV Rules Selection

Payers for all Bill Types for MNV Rules Selection


LAB_NFG_V7.3.0_1 3-9

For example, the Insurance (Payer) Code field is displayed on the Medical Necessity Rules “Rule Maintenance” screen for the Medicare Insurance (Bill Type) Type (as shown in Figure 3-7 on page 3-9), thus enabling you to associate a rule for this Insurance Type (Bill Type) with a specific Insurance Code.

Figure 3-7: Insurance Code Field with Medical Necessity Rules

If you do not enter a value in the Insurance Code field, then the CyberLAB system applies the rules to the billing type currently selected. New configuration options within General System Parameters allow you to define rules for all Bill Types and to allow for the association of Insurance Codes with all Bill Types.

Additional Age and Gender Fields within Medical Necessity Validation Rule SetupThe following fields have been added to the Medical Necessity Rules screen used for entering waiver information, as shown in Figure 3-8:

• Age Range text 1

• Age Range text 2

• Gender Checking text 1

• Gender Checking text line 2

The text entered into these fields assists in defining the reasons that an ordered test meets or fails the Medical Necessity Rules established for both the patient’s Bill Type and Insurance Code and can be configured to appear on the waiver.



Figure 3-8: Additional Fields for Medical Necessity Bill Type Initial Setup of Waiver

Once the waiver information is recorded, the next screen displayed within Medical Necessity Rules now contains the following new fields, as seen in Figure 3-9 on page 3-11:

• Allowable Age Range

• Gender Requirement

Allowable Age RangeAge is only considered in the validation process of the selected test when values are entered into the Allowable Age Range fields.

Gender RequirementThe following three values exist for the Gender Requirement drop-down list:

• No Gender Checking

Directs CyberLAB to disregard the patient’s gender during the Medical Necessity Rule validation process. The “No Gender Checking” selection is the system default for the Gender Requirements drop-down list.

• Female Only

Directs CyberLAB to consider only female patients during the Medical Necessity Rule validation process.

• Male Only

Directs CyberLAB to consider only male patients during the Medical Necessity Rule validation process.

Age and Gender Fields


LAB_NFG_V7.3.0_1 3-11

Figure 3-9: Age and Gender Fields Added to Medical Necessity Rules

Ability to Hold Samples Requiring Waivers Based on Medical Necessity Rule FailuresUnder the Features Tab of General System Parameters, you may now configure CyberLAB to automatically hold tests that fail Medical Necessity Rules. Using the “MNV Rule Failures in Held Status” drop-down (as shown in Figure 3-10 on page 3-11), select “Yes” to implement an automatic hold for any test that fails a Medical Necessity Rule or “No” to maintain the test in the original Order status.

Figure 3-10: MNV Rule Failures and FAX Waiver/Authorization Options

Age and Gender Fields

MNV Rules in Held Status Option

FAX MNV Waiver Solutions

FAX Authorization Request Selections



Tests can also be placed in “Held” status based on ABN Waiver designation. Figure 3-11 on page 3-12 shows the Test Code CBC-A failing a Medical Necessity Rule during Patient Order Entry. If CyberLAB is configured to Hold Medical Necessity Rule failures and the “ABN Waiver Signed” prompt is selected for either “No” or “Unknown”, then this test will be placed in a “Held” status.

Figure 3-11: Medical Necessity Rule Failure to be Held

Samples comprised of multiple tests may be ordered in two ways: As Collected and To Be Collected, each of which affects the “Held” Status procedures differently.

• If the Sample is ordered “As Collected” and contains some tests that have failed and some tests that have passed the Medical Necessity Rules, then only the failing tests will be placed in a “Held” Status. Should all the tests within an “As Collected” sample fail, then the entire sample will be placed in a “Held” status.

• Samples ordered as Not Yet Collected are automatically placed in a “To Be Collected” status regardless of the number of included tests that have rule failures.

Ability to Fax Waiver to the Ordering or Attending PhysicianUnder the Features Tab of General System Parameters, you may now configure CyberLAB to Fax an additional copy of a Printed Waiver to either the Ordering or Attending Physician. The following options are available for the “Fax MNV Waiver” configuration as shown in Figure 3-10 on page 3-11.

• Fax to Ordering Doctor

Whenever a Waiver is printed by CyberLAB, an additional copy will be faxed to the Ordering Doctor if a fax number has been set up for this doctor in the Client Master Data Base.

ABN Waiver Signed Prompt selected for Unknown


LAB_NFG_V7.3.0_1 3-13

• Fax to Attending Doctor

Whenever a Waiver is printed by CyberLAB, an additional copy will be faxed to the Attending Doctor if a fax number has been set up for this doctor in the Client Master Data Base.

• Do Not Fax to Client

No additional waiver copy will be faxed.

Order Entry Decision Support EnhancementsThe following feature enhancements have been added to the Order Entry Decision Support module:

• Additional Payer Code Fields

• Additional Payer Maintenance Rule Types

• Venipuncture Rules

Additional Payer Code FieldsThe Payer Maintenance screen, accessed from the Order Entry Decision Support module, now contains additional insurance code fields, thus enabling you to record supplemental address and contact information as seen in Figure 3-12 on page 3-14. The new fields include:

• Address

• Address2

• City/State/Zip

• Phone

• Fax Number

• Email Address

The Email Address field is not functional for CyberLAB version 7.2.10. You will be able to use this field in a future release of CyberLAB.



Figure 3-12: Additional Payer Code Fields Added to the Payer Maintenance Screen

Pre-Authorization Template SetupThe Payer Maintenance screen, as seen in Figure 3-13 on page 3-15, has been further enhanced by the inclusion of a Pre-Authorization Template field. This new field allows you to enter your laboratory’s version of a pre-authorization request form template and designate the distribution method by which the form will be sent to the payer.

In the Template field, enter the file name of the Word document your facility uses as a template. This entry activates the adjacent drop-down field from where you indicate the form’s disposition: automatic FAX directly to the payer or hard copy printing for alternate distribution.

Additional Payer Code Fields


LAB_NFG_V7.3.0_1 3-15

Figure 3-13: Setting Up the Pre-Authorization Template for either Fax or Print

Once you send ASPYRA your laboratory’s version of a pre-authorization template, ASPYRA sets up your template to ensure that CyberLAB automatically populates it with the correct contact information for transmittal to the insurance company.

Additional Payer Maintenance Rule TypesThe CyberLAB Order Entry Process has long supported the Substitution rule type, which allows you to substitute one test code for another as dictated by the Patient’s bill type and insurance coverage (Payer). Beginning in version 7.2.10, new rule types: Add, Exclude, and Pre-Authorize have been added to the Payer Maintenance screen, which automate the following procedures:

• Adding an additional test code to the original order

• Excluding a test code from an order

• Defining a test code that requires Pre-Authorization and allows the Pre-Authorization form to be faxed to the insurance company

Working with Payer Maintenance Rule TypesAs seen in Figure 3-14 on page 3-16, all rule types appear on the Payer Maintenance screen where you select the billing method designated to pay for the test. Click the Rule Type drop-down list to display the additional rule types, which now include:

• Add

• Exclude



• Pre-Auth

Figure 3-14: Additional Rule Types Added to the Payer Maintenance Screen

Adding a Test CodeIn some cases, you may need to add additional test codes to an order when a specific test is ordered for a patient using a specific Billing Type and Payer. This may be related to handling procedures that one Payer will incur while others will not or to accommodate additional testing required by one Payer but not by others. When configuring a test code to be added to an order, we assume that you have selected a Payer code and have entered a test code. In the example shown in Figure 3-15 on page 3-16, we have selected a Payer Code of “ASP” and a Test Code of “437” for Glucose.

Figure 3-15: Payer Code and Test Code Selection

When you click the Submit button, a screen (see Figure 3-16 on page 3-17) displays that enables you to select the appropriate Rule Type and applicable billing option for the designated test.

To configure the rule to add another test code to the original test order of “Glucose”, make sure that both the rule type and the billing type are set to “Add”.

New Rule Types


LAB_NFG_V7.3.0_1 3-17

Figure 3-16: Adding a Test Code to the Decision Support Rule

The test code added to the Decision Support Rule is another Glucose test, which has a test code of 237. A confirmation message appears at the bottom of the screen to indicate the successful addition of a new test code.

Excluding a Test CodeYou may need to warn the Order Entry Personnel that certain Test Codes should not be ordered because they are on the patient’s Payers Exclusion list. To configure a Test Code for exclusion from an order, you can use the “Exclude” rule type. As seen in Figure 3-17 on page 3-18, Test Code 229, Glucose Fasting, should not be ordered for a patient with the Payer ASP for all Bill Types.

Rule Type and Billing Type Set to Add

Confirmation Message that Test Code has been Added to Original Test



Figure 3-17: Excluding Glucose Fasting Test Code Setup

From this point forward, any Order Entry that includes Test Code 229 (Glucose Fasting) for a patient with an Insurance (Payer) code of ASP causes the warning dialog shown in Figure 3-18 on page 3-18 to display.

Figure 3-18: Order Entry Decision Support for Exclusion Rule

Defining a Test Code that Requires AuthorizationAt your laboratory, you may want certain tests to require that a pre-authorization be obtained before the test is performed. To set up a Test Code to require pre-authorization, both the Rule Type and the Billing Type must be set to the “Pre-Auth” value as seen in Figure 3-19 on page 3-19 for Test Code 7602, for Payer Code ASP and all Bill Types.


LAB_NFG_V7.3.0_1 3-19

Figure 3-19: Setting Up a Test Code to Require Pre-Authorization

Figure 3-20 on page 3-19, shows the dialog window that an Order Entry Tech would receive when ordering Test Code 7602, Bun/Creation Ratio for a patient with an Insurance Code (Payer Code) of ASP.

Figure 3-20: Message that Offers the Option of Placing the Test On Hold



If a Test is Held for Pre-Authorization and the Payer’s Template and Distribution method is set up, the Authorization Request Form will be populated with the patient and test information and either faxed to the Payer’s fax number or printed.

Additional options for faxing copies of the Authorization Request form are set up under the Features Tab of General System Parameters, as shown in Figure 3-10 on page 3-11. Fax Authorization Request options are identical to those automatically generated for Waivers, which are defined in “Ability to Fax Waiver to the Ordering or Attending Physician” on page 3-12 of this guide.

Venipuncture RulesCyberLAB now enables you to set up Venipuncture Rules, thus speeding the billing process and simplifying the completion of ordered tests.

The set up option for Venipuncture Rules is contained within the Order Entry Decision Support Module. This option allows you to configure by “Payer”, “Bill Type”, and “Collect Tech.” the Billing Only Test Codes that will be added to a Sample Order based on Tube Type.

As seen below in Figure 3-21 on page 3-20, you can define your Rules based on any combination of the following Fields.

• Payer Code

This must be a valid code that has been set up in the Payer Maintenance section. It can also be blank as long as there is a Bill Type.

• Bill Type

This is selected from a drop down list of valid Bill Types. You can also select a value of “none” as long as there is a valid Payer Code.

• Collect Tech

This is a free-form, four-character field if the Collection Tech field in Patient Entry is configured this way, or it is a two-character, validated Tech ID if the Collection Tech field in Patient Entry is configured as such. The Collect Tech field can also be left blank as long as a valid Payer Code or Bill Type is entered.

Figure 3-21: Venipuncture Rule Setup


LAB_NFG_V7.3.0_1 3-21

The Venipuncture Rule Setup screen, as shown in Figure 3-21 on page 3-20, enables you to “Add” new rules or “Change” existing rules. Once you have selected the primary rule indicator fields, you can define up to fifty Tube Type/Bill Only Test Code combinations.

Figure 3-22: Setup of Venipuncture Rule Tube Type/Bill Only Test Code Combinations

As depicted in the Venipuncture Rule example shown in Figure 3-22 on page 3-21, if an Order is placed for tests that require either a Lavender Top (L-Top) or a Red Top (R-Top) tube type for a Patient with a Bill Type of “Other Insurance”, a Payer Code of “ASP”, and a Collect Tech of “CCA1”, a Billing Only Test of 520 (Venipuncture Charge) would be applied to the order.

Patient Inquiry EnhancementsThe following enhancements have been added to Patient Inquiry:

• Reposition of Send-Out Code on result line

• Abnormal Send-Out Result text colored as abnormal

Reposition of Send-out Code on Result LineWhen results are imported into CyberLAB through a Results-In Interface, they are tagged with a Send-Out Code that represents the laboratory at which the test was performed.

This Send-Out Code now appears at the end of the corresponding result line in Patient Inquiry bracketed within parenthesis, as shown in Figure 3-23 on page 3-22.



Figure 3-23: Patient Inquiry Send-Out Results

Abnormal Send-Out Result Color-KeyedAbnormal Send-Out test results now appear on the Patient Inquiry Send-Out Results screen (see Figure 3-23 on page 3-22) in red, matching the Abnormal Flag and Result Marker. This color-coding informs you at a glance that the contained test information requires immediate attention.

Patient Entry EnhancementsIn the Patient Entry module, additional insurance fields have been added according to the client’s billing type. The additional insurance fields are an optional feature enhancement offered with the CyberLAB version 7.2.10 application.

Additional Insurance Fields in Patient DemographyThe additional insurance fields appear on the Demography screen as seen in Figure 3-24 on page 3-23 and are organized on the screen by the following tabs:

• Primary Ins

• Secondary Ins

• Additional Ins

On any of these tabs, you can designate for each selected billing type, which fields are required, which fields are optional, and which fields will not be used at all.

As seen in Figure 3-24 on page 3-23, the fields on the Primary Ins tab allow you to enter insurance information based on the patient’s primary insurance carrier. In this example, the selected Insurance Type is “Patient”, which when selected, disables all insurance related data fields (Group No., Medicare No., Medicaid No., Insurance No., and Insurance Co.).


LAB_NFG_V7.3.0_1 3-23

Figure 3-24: Additional Insurance Fields on the Demography Screen for Primary Insurance

As seen in Figure 3-25 on page 3-23, the fields on the Secondary Ins tab allow you to enter insurance information based on the patient’s secondary insurance carrier. In this example, we selected “Medicare” as our insurance type, which automatically makes the Insurance Co. and Medicare No. fields open and available for you to enter the appropriate value. The majority of the other insurance fields on this tab are closed and do not allow you to enter information.

Figure 3-25: Additional Insurance Fields on the Demography Screen for Secondary Insurance

As seen in Figure 3-26 on page 3-24, the fields on the Additional Ins tab allow you to enter insurance information based on any additional insurance that the patient currently has. In this example, we have selected “Other Insurance” as the patient’s additional insurance, which automatically makes all fields except Medicare No. and Medicaid No. available for editing.



Figure 3-26: Additional Insurance Fields on the Demography Screen for Additional Insurance

Improvements and CorrectionsThis section lists the corrections and improvements made to the CyberLAB system version 7.2.10:

• Modified Panel Results Editing module to prevent QC text from carrying over from one Test to another on different Known Controls. (SLX 001-00-002956)

• Corrected the issue of a call comment not appearing in Patient Inquiry when releasing a held result. (SLX 001-00-002963)

• Modified the Send-Out Code Maintenance module to correctly remove a Send-Out code when the delete option is selected. (SLX 001-00-002972)

• Modified the Call List / Abnormal Reports module to prevent the program from hanging when printing a report when sorting by “Only Panic / Critical Values. (SLX 001-00-002997)

• Modified the Load List Profile Maintenance section of the Interface Characteristics module to correct the issue of the inability to enter a Barcode Specimen Type when configuring Split Sample processing. (SLX 001-00-002998)

• Modified the Urinalysis Parameter Maintenance module to correct the issue of the Urinalysis ranges not saving the first time entered. (SLX 001-00-003012)

• Modified the QC Manual Results Entry module to correctly allow for the entry of Alpha type QC results. (SLX 001-00-003031)

• Corrected the issue of Selection Lists having more than 20 options defined in the Field Master File from being truncated to 20 when the html is generator. (SLX 001-00-003033)

• Modified the Microbiology Parameter Maintenance module to correct the issue of the Default Micro Parameter field (Sensitivities Comment Code) not holding when entered and Biochemical result as a comment code not validating. (SLX 001-00-003036)

• Corrected the issue with the Field Master Update program to read a Windows formatted text file as input. (SLX 001-00-003064)

• Updated Patient Inquiry to correct passing of the Sample ID to the external URL of a website when using the Quick Launch Icon action “Website,” and “?Sample=<SID>” prefix. (SLX 001-00-003160)


LAB_NFG_V7.3.0_1 3-25

• Corrected the mismatched data type issue that developed between the application and SQL Data Base when entering the Barcode Specimen Type during configuration of Split Sample Processing. (SLX 001-00-2998)





If you need additional information about the CyberLAB system, you can access the online help by pressing the Quick Launch Icon with an image of a book while in the CyberLAB system.


In This Chapter...


Improvements and Corrections .......... 4-2



CyberLAB EnhancementsIn this section, you can learn about the following enhancements made to the CyberLAB system in version 7.2.9:

QC Graphs Now Display in Graphical Form.............................................................................. 4-2

Species Code Selection List at Order Entry ................................................................................. 4-2

User Class Control Over Schedule Download Menu Content .................................................. 4-2

QC Graphs Now Display in Graphical FormThe QC graphs in CyberLAB used to display on the screen in a character-based style. Starting with the CyberLAB 7.2.9 release, the QC graphics display in graphical form on the following screens:

• Single Result Entry

• Panel Results Entry

• Matrix Results Entry

• Point-of-Care Entry

• QC Manual Results Entry

• QC Statistical Report Options

In addition, two plotted graph lines are supported, for either the case of two Knowns for one Test Code or two Test codes for one Known.

The new graphical style is supported on both Unix and Windows platforms.

The third-party software that supports the new style of QC graphs is automatically installed as part of the 7.2.9 update. There are no support requirements for this software.

Species Code Selection List at Order EntryVeterinary laboratories are now able to use a Species Code selection list at Sample ID Order Entry. This feature is automatically available when the Species Code field is active.

User Class Control Over Schedule Download Menu ContentThe User Class Maintenance module was modified to allow selective access to the Schedule Download options, when more than one option is available in that menu selection.



LAB_NFG_V7.3.0_1 4-3

• Modified the Urinalysis Results Entry submodule that when you delete a Urinalysis Result record, the Cyberprint definition files and the Result Response activity logs are no longer deleted.

• Modified the Panel Results Entry submodule to suppress the telephone icon when the Call feature is not active.

• Modified the Specimen Workup/Edit submodule in the Microbiology module to prevent entry of duplicate organism codes when in Held Results mode.

• Modified the results posting modules for SQL systems so that interpretations are retained for tests that exceed the 78th test slot on the sample.

• Modified all results presentation modules so Alpha Result Conversion supports up to 204 entries instead of 102.

• Modified the Collection Verification submodule in the Patient Entry/Inquiry module to use the system flag that requires entry of the Micro Source Code.

• Modified the Batch Specimens In-Transit submodule in the Work Scheduling module to show Sample IDs in transit from the main site to a remote site.

• Modified the Single Result Entry submodule in the Results Entry module. When the default abnormal flag is a critical flag and the result of a Sample ID is changed to normal, the result posted is a pure abnormal flag.

• Modified the Edit Instrument Results submodule in the Results Entry module to suppress the telephone icon when the Call feature is not active.

• Modified the Collection Verification submodule in the Patient Entry/Inquiry module to support Medical Necessity Validation on host ordered Sample IDs.

• Modified the Interim Report submodule in the Clinical Reports module to ensure against double-spacing on the copy-to version of the lab report.

• Modified the Interim Report submodule in the Clinical Reports module to properly use the report parameter flag that controls inclusion of the Primary Care doctor in the Copy-to Doctor list.

• Modified the Test Maintenance submodule in the Test Dictionary Maintenance module to properly write a new handling text when the Extended Range tab was also selected.

• Modified the Autorelease rules processor in the Instrument Interface Maintenance submodule of the File Maintenance module. The modification prevents abnormal termination when the Instrument Interface Maintenance submodule only sends results for tests with zero Test Code.

• Modified the background Microbiology results processing module to check for a nonnumeric Sample ID before writing to the pending Microbiology results file. This modification prevents an intermittent SQL error.

• Modified the Cumulative Report submodule in the Clinical Reports module to properly print the page number when the number of samples across setting is less than five.

• Modified the Instrument Interface results processing module to prevent intermittent skipping of results when received from an interface.



• Modified the SQL database properties of the Cytology Workload hours field to allow for two decimal places, which matches the field definition within the Cytology Workload Entry module.

• Modified the Results Processing module to update the sample record to include the send-out code of the panel header. This modification prevents reprints of the send-out manifest from returning a message, which indicates that no send-out tests qualify for reprinting.

This modification does not affect the send-out interface.



If you need additional information about the CyberLAB system, you can access the online help by pressing the Quick Launch Icon with an image of a book while in the CyberLAB system.


In This Chapter...


Improvements and Corrections .......... 5-4



CyberLAB EnhancementsIn this section, you can learn about the following enhancements made to the CyberLAB system in version 7.2.8:

Access Unix-Archived Reports from Windows................................................................1-2

Quick Launch Icon Bridge to Another Website..................................................................1-2

Generate Interim Report Print Activity..............................................................................1-3

Five Color Choices for Delta Flag......................................................................................1-3

Work in Progress Report Offers New Filter.......................................................................1-3

Test Dictionary List Includes Handling Procedures............................................................1-3

Autotransmit Batch to International Destination................................................................1-4

Access Unix-Archived Reports from WindowsCyberLAB clients who upgraded from the Unix to Windows platform and archived reports in the Unix system, can now access Unix-archived reports from Windows.

Archived patient data is stored in archive volumes. Each volume has a name. The Unix archive process moves live patient data to an archive volume that is named by the user.

After you access the archived report in the volume, you can view the report on the screen, print it, or select File to send the report to a file in your directory.

The Patient Inquiry and Ad Hoc Report Generator submodules are affected by this capability to access Unix-archived files from Windows.

Quick Launch Icon Bridge to Another WebsitePlace a Quick Launch Icon in the Patient Inquiry submodule to associate the CyberLAB system’s patient results database with another system’s results database.

When a sample ID containing a patient’s test results is posted in Patient Inquiry, the user can press the Quick Launch Icon, usually placed at the top of the screen, in Patient Inquiry.

This action makes the CyberLAB system’s sample ID available in the other system’s result database. So, a user in the other results database can then access the test results of that patient.


LAB_NFG_V7.3.0_1 5-3

Generate Interim Report Print ActivityThis action is located in the Results Response Maintenance submodule in the File Maintenance module.

By default, when all results being posted come purely from RRG (Results Response Generator) actions, which is most common when a sample test is first ordered, the action flag (yes/no) is ignored, and a report is generated. A new RRG flag makes certain that the selected action (yes/no) is honored.

Five Color Choices for Delta FlagThe Delta Flag appears on the Results screen in the Patient Inquiry submodule only when the result failed Delta checking. It appears as a “D” to the right of the Normal Range flag of the result.

In the 7.2.8 CyberLAB system, the color of the Delta Flag, which had been changed to yellow to distinguish it from red, is now returned to red. However, the red color is misleading because in the CyberLAB system, red results are considered abnormal. The red color had been changed to yellow to differentiate it from the red color, but the yellow color was difficult to view.

Therefore, at a client’s request, your ASPYRA implementation specialist or Client Support representative can override the default color of red and offer five other distinct color choices.

Work in Progress Report Offers New FilterThe Work in Progress Report generates a list of patients for which tests are ordered but results are pending.

The filter default for the date is that of the order. An alternative to the order date that was added several years ago is the Lab Received date. In the 7.2.8 CyberLAB system, another alterative that has been added is the Collection date.

The change from order to the Lab Received date or Collection date can be made by your ASPYRA implementation specialist or Client Support representative.

Test Dictionary List Includes Handling ProceduresThe Test Dictionary List contains all the tests within the Test Dictionary of the CyberLAB system. The list is located in the Test Dictionary submodule in the File Maintenance module. The list of tests can be viewed on the screen or printed in a detailed report.

If the user selects the Yes option to print a detailed list of tests in the Test Dictionary, the list will contain the handling procedures for the tests. There is also a separate list of handling procedures for tests that can be viewed on the screen or printed.



Autotransmit Batch to International DestinationTo autotransmit a batch of clinical reports outside the United States, a phone number with more numbers is required.

Therefore, when the CyberLAB server dials the phone number to the destination, the amount of numbers allowed has been extended from 13 to 30 to accommodate the length of international phone numbers.

The Autotransmit Utility submodule is located in the Laboratory Management module.


• Modified the C.A.P. Report module to scan the files more efficiently. With large C.A.P. Reports in the SQL systems, the report and purge function took an excessive amount of time to print.

• Corrected a SQL error that terminated the Action Management Maintenance program. Action management tasks could not be accessed in the maintenance submodule.

• Increased the lines of result text printed in Cumulative lab reports to a system maximum of 98 lines when only the first 12 lines of reports printed.

• Corrected the truncation of performing multi-site name and address fields in Cumulative lab reports, returning to 30 characters from the truncated 25.

• Corrected the urine result range flags in the Urinalysis Results Entry that were not being retained in the database at initial entry. This occurred only in SQL systems.

• Corrected incomplete results queued for review, which occurred when the result review feature was active and a urine result included manually entered result text comments.

• Corrected removal of the primary care doctor from the sample when a test was added via urine reflex or micro decision support.

• Corrected the lab received date being intermittently set to zero when the lab received date was updated.

• Corrected termination of the Call Report Phone List submodule with a fatal error 4:6 when the All Sites option was selected along with the Full Client List. The error occurred only when the last sample for the last listed client was selected and completed.

• Corrected an error in the Order Entry submodule where a new patient demography for a child was expressed in zero years rather than months.

• Corrected a malfunction of a Delete button in Micro Instrument Results Edit submodule. When the button was selected, the results were not deleted from the to-be-edited (pending) micro results file.

• Corrected an error in the Specimens In Transit submodule (SQL systems only), where the Print-Unbatched report and the Create-Preloaded Batch option did not produce a complete list or worksheets.


LAB_NFG_V7.3.0_1 5-5

• Corrected an error in Differential Results Entry, where differential cell counting via the keyboard-strike method allowed the count to pass the CyberLAB cell limit of 999.

• Corrected improper scanning of the SQL database in the Batch Specimens In Transit submodule (SQL systems only) when a new batch is created. The improper scanning did not allow the sample ID selection list to populate.



Documents

CyberLAB Version 7.3.0 New Features Guide · aimed at helping providers, payers, vendors, and non-covered entities with the transition to ICD-10. CyberLAB’s support of ICD-10 codes