Core software & modules

What are the core software and modules?

Our software is built using specifications gathered from laboratories around the world. Along with HistoTrac Core Software, the additional modules enable the laboratory to maintain lab-specific records pertaining to purchasing, supply inventory, and mailings. Use these modules to assist in the organization of your work, to reduce the need for extra paper and spreadsheets, and to eliminate hand-written labels.

Core software

The Core Package is the center of the software, supporting all the basic functions of the laboratory.

 

Patient and donor database

Handle samples and orders on patients and donors from test requests through reporting of results. Look up patient demographics and test history.


Key features

  • Patient/donor case building with viewing haplotype and mismatch results
  • Sample, test, and report history
  • Ad hoc query tool
  • Audit history for tracking both field- and record-level user actions

HistoTrac database server

Minimum hardware specifications

  • No additional requirements beyond the minimum requirements for SQL Server

Required software

  • Microsoft SQL Server

Optional software

  • If faxing, software such as WinFax
  • If writing additional reports, license for SAP® BusinessObjects®

HistoTrac user workstation

Minimum hardware specifications

  • 733MHz Pentium III processor
  • 256MB memory
  • 50GB hard drive
  • VGA (1024x768 resolution) monitor
  • Ethernet adapter
  • Keyboard/mouse

Required software

  • Microsoft Windows 10 or higher

Web server

Minimum hardware specifications

  • 733MHz Pentium III processor
  • 256MB memory
  • 50GB hard drive
  • VGA (1024x768 resolution) monitor
  • Ethernet adapter
  • Keyboard/mouse

Required software

  • Microsoft Windows 2016 server or higher
  • Internet Information Services 7.0 or greater

Reagent Vendor Utilities (RVU)

Save time and reduce transcription errors


RVU Software utilization saves time and reduces transcription errors by importing test results directly from the testing analysis software into your HistoTrac Software.

The larger your volume, the more important it is to have the software manage the data entry. With imported results, the review cycle can be reduced, minimizing the need for detailed visual review and freeing time to focus on other tasks. Use an RVU for every testing method.

These interfaces may be bi-directional and begin by exporting a sample ID from HistoTrac to the RVU Software—no more manual entry of sample IDs into text files. After testing is completed and results are analyzed, the user imports test results from the RVU Software into the HistoTrac Software. For a uni-directional interface, the user would only import from the RVU to HistoTrac.

The workflow for the use of RVU is facilitated by batching tests and building trays in your HistoTrac Software. The build-a-tray feature helps you create tray maps organized by various criteria.

Histocompatibility and non-histocompatibility interfaces

  • Molecular typing
    • Reverse Sequence-Specific Oligonucleotide (rSSO)
    • Sequence-Based Typing (SBT)
    • Sequence-Specific Primer (SSP)
    • Next Generation Sequencing (NGS)
    • Quantitative Polymerase Chain Reaction (qPCR)
  • Antibody screening and identification
    • Luminex
    • Flow — custom to instrument & assay
  • Crossmatch
    • Flow — custom to instrument & assay
  • DNA measurement
  • Chimerism testing

Key features

  • Manage entire test batches from ordering through reporting with single data entry
  • Implement interfaces with each analysis software used
  • Create a 96-well tray using the Tray Wizard, then export the sample ID associated with each well location
  • Export test batches
  • Connect directly to the RV database or use XML file transfer
  • Import results without manual data entry:
    • Antibody specificities and Mean Fluoresence Intensity (MFI) data
    • Median Channel Shift (MCS) and Molecules of Equivalent Soluble Fluorochrome (MESF) values
    • Alleles, serological equivalents and National Marrow Donor Program (NMDP) codes
  • Select from Import Settings to determine the placement of results in your tests

HL7 interfaces

The solution for full integration


HistoTrac Software can be connected with your hospital and/or laboratory system to provide full integration with the patient’s electronic medical record. Patient demographics, test orders, billing transactions, and test results or reports move between medical software systems using an HL7 formatted transaction. Each interface is separate and requires the accompanying hospital or laboratory information system interface.

Key features

  • Import patient demographics into the HistoTrac Software from an ADT feed
  • Bring in patient demographics and orders for a specific test with an Orders feed
  • Transmit a billing transaction from the HistoTrac Software to your hospital billing system
  • Send individual test results or reports, depending on the specifications of the receiving system

Software add-on modules

Validate your HistoTrac database to ensure all patient data is up-to-date and accurate.

UNOS Waitlist Management

Maintaining an accurate listing of patient data used in the UNOS patient-donor matching process is critical


This module provides a means to identify differences between the patient data in HistoTrac Software and UNOS. The UNOS Wait List is downloaded from UNet and imported into HistoTrac with validation between the two systems using the patient’s identification.


The user can update HistoTrac values such as the UNOS-listed flag, CPRA, and patient status with data from the Waitlist file, and apply updates to the entire list or individual records.

UNOS Unacceptables

Updating patient’s unacceptable specificities in UNOS is a complex, time-consuming, and tedious necessity for HLA Labs


The UNOS Unacceptables utility provides an API with the patient’s unacceptable specificities, formatted according to the UNET standard. This feature not only saves time but also eliminates transcription errors.

UNOS Final Crossmatch

Speeding up donor workups for laboratories that perform large numbers of final crossmatch tests per donor is the goal of this vital tool


Tests can be ordered for cytotoxicity or flow methods. The donor is added to the patient’s case. A custom-designed report provides test results for coordinators or surgeons.

NMDP Confirmatory Typing API

Updating donor and/or recipient molecular typing results in a timely manner is crucial for stem cell transplant patients


This module is designed to export donor and/or recipient molecular typing results for Form 117 and Form 22. An API sends the most recent results to the NMDP for import into the registry database on a scheduled basis, perhaps daily, thus saving time and eliminating transcription errors.

Paired Kidney Exchange (PKE)

 

The Paired Kidney Exchange (PKE) module provides a complete and flexible tool for swapping previously incompatible patient/donor pairs. The data for calculating matched pairs are all found within the HistoTrac database — no more sending data to third-party programs. Select the optimal chain length, determine the source of antibody testing used to rule out donor incompatibility, and establish the factors that influence the PKE score for each chain.

 

What key benefits does the PKE module provide?

The PKE module provides the data and programming required for formatting sensitized patients with a compatible donor.  As patient test data are updated, the matches can be re-run without sending new data to a third-party system.


The match program provides the flexibility needed to use the criteria of your transplant program. Adjust the parameters for one patient that might be different from another.

The program can be run by the clinical staff or can be used within the laboratory. A report documents the chains created.

The Matching Algorithm

Not all transplant programs use the same matching protocol when selecting a donor for a patient. The HistoTrac PKE module provides choices at each of the various match criteria:

  • Source and strength of antibody specificities
  • Level of match at selected loci
  • ABO matching vs. ABO compatibility
  • Non-HLA factors like infectious disease
  • Weight and age of donor for pediatric patients

 

Key features
  • Use patient unacceptable specificities or MFI data with selected cutoff per locus for assessment against donor antigens
  • Adjust variance to allow a lower antibody level at selected loci
  • Enable an alert for mismatched ABO pairs
  • Select HLA typing values from either serology or serological equivalents from molecular testing, depending on data present on your pairs

The PKE Score

Each chain’s score is calculated based on user-defined rankings such as the length of time the patient has been waiting for a transplant, the patient’s antibody level, and the importance of HLA match between the pair members. The higher the score, the more difficult the patient is to transplant.

 

Key features
  • Score points for Days in Program
  • Factor the CPRA into the score
  • Give points for matching weighted differently at each locus
  • Evaluate the scores to select the most difficult-to-transplant patient

For Laboratory Use.