RALS Pathway Connectivity
Reduce manual data entry and potential transcription errors in Physician Office Labs
Connectivity for the tests you run in your office lab everyday... [RALS Pathway PDF]
Comes pre-configured and installed on a virtual machine for ease of implementation
Collects test results from devices used in Primary and Secondary Care
Eliminates the need for multiple software or hardware dedicated to a vendor’s specific device
Provides access from anywhere/anytime with full functionality
Supports result, operator, patient and instrument management
Manages all QC in a single system
Includes a wide range of reports
Can be interfaced to an EMR / EHR / LIS
Connectivity based on proven RALS platform used in ~50% of U.S hospitals: [Demo]
Depending on the device, data can be transferred from devices to the RALS Pathway system via an RALS Dataport, a RALS Remote Connect (RRC) PC connection, or a Direct Network Connection. Results can be via RALS Pathway viewed anytime/anywhere on a PC connected to the POL network and can then be sent to the EMR / EHR / LIS for posting on to the patient's record/chart. For device-specific connectivity, contact the Informatics Executive or Regional Business Manager in your area.
For more information, contact your Informatics Executive or Regional Business Manager.
Device Dependent Communication The RALS system is interfaced to point-of-care market share leaders in glucose, coagulation, blood gas and electrolyte and cardiac markers. This position relates to real data management connectivity - bi-directional communication and full data management of patient test results (as well as operating QC data, etc.) not just capturing test data only and moving it along to the LIS.
Bi-directional Connectivity In this two-way communication, the data manager can upload data to the device in addition to reading data from it. For devices that feature bi-directional capability, the RALS system can upload a wide range of data including lists of valid operators, reagent lot information (lot #, ranges, etc.), and device configuration information. This is one of the key differences between a "data mover" and a "data manager".