Translational Software Alternative: What PGx Labs Should Look for in a Replacement

A Translational Software alternative should be interpretation software that runs downstream of your existing variant and star-allele calling, reconciles CPIC and other guideline sources, and routes every report to your licensed medical director for sign-out. Labs displaced by the 2023 PGxPortal discontinuation should audit evidence depth, guideline maintenance, LIS and FHIR integration, and migration support before committing.

Why Are Translational Software Labs Evaluating Alternatives Now?

If you ran your pharmacogenomic reporting on PGxPortal, you already know why this question is live. In October 2023, Translational Software announced it would stop providing its PGxPortal pharmacogenetic decision-support service in the US by year-end, following the FDA's rejection of its 510(k) submission (as reported by GenomeWeb in October 2023). Trade-press reporting at the time noted the shutdown left nearly 100 laboratory customers searching for new PGx result-reporting options.

For a molecular lab, losing your interpretation layer is not a minor vendor swap. Your validated calling pipeline still works, your test menu is unchanged, and your medical director still signs out cases, but the software that turned diplotypes into guideline-backed, orderable reports went away. That is a specific, bounded problem: you need a replacement reporting and interpretation layer that plugs into the pipeline you already trust, not a rebuild of your assay. This guide walks through what to audit so you choose once and cut over cleanly.

What Actually Happened With the PGxPortal 510(k) Determination?

The details matter because they shape what a safe replacement looks like. Per GenomeWeb and Precision Medicine Online, Translational Software pursued FDA 510(k) clearance for PGxPortal, attempting to show substantial equivalence to an FDA-authorized comparator device; the FDA determined PGxPortal was not substantially equivalent. This was a denial of clearance, not the revocation of an existing one, because PGxPortal never held 510(k) clearance.

According to reporting on CEO Don Rule's statements, the rejection centered on concerns about PGxPortal's diplotype-calling feature and on the company's use of guideline recommendations from expert bodies such as CPIC, which the FDA does not formally recognize as an authoritative source. The 510(k) process reportedly spanned roughly 2020 to 2022 before the negative determination and the October 2023 announcement.

One clarification worth stating plainly: Translational Software discontinued the specific PGxPortal decision-support product, not its entire business. Its current website (checked August 2026) offers a different product line, a "PGx Toolkit" for labs to develop and validate their own CLIA- and MolDX-compliant pharmacogenomic LDTs, with no FDA-clearance claim attached. So the accurate framing is narrow: a specific product you relied on was retired, and you need a replacement for that layer.

How Does the Current LDT Regulatory Backdrop Affect Your Decision?

The regulatory picture has shifted since 2023, and it changes the calculus for any lab building or buying a PGx pipeline. FDA published its LDT Final Rule in the Federal Register on May 6, 2024. On March 31, 2025, the US District Court for the Eastern District of Texas, in the consolidated ACLA v. FDA and AMP v. FDA cases, vacated and set aside that rule in its entirety, holding that FDA lacks statutory authority under the FDCA to regulate laboratory developed tests as medical devices (ACLA's summary of the ruling).

FDA did not appeal and formally rescinded the rule via a new final rule on September 19, 2025, reverting to the pre-2024 enforcement-discretion posture. As of August 2026, no FDA LDT Final Rule is in effect. FDA has stated it retains authority over specific device components, such as commercially distributed kits and reagents, RUO/IUO products, and software meeting the Software-as-a-Medical-Device definition. Separately, CMS issued a CLIA Request for Information in mid-2026 and federal legislation (H.R. 8890) was introduced to move LDT oversight under CMS/CLIA, but neither is finalized law. This is not legal advice; confirm current status with your regulatory counsel before relying on it.

What Are the 5 Critical Capabilities to Audit in a Translational Software Alternative?

Evaluate candidates against the same rubric so comparisons are apples-to-apples. These five capabilities separate a durable reporting layer from a fragile one.

1. Evidence depth and provenance. Confirm which guideline bodies and drug-label sources the platform ingests, how many pharmacogenes and medications it covers, and whether every recommendation is traceable to a named source.
2. Guideline reconciliation and version maintenance. CPIC, DPWG, and FDA labeling do not always agree, and they change. Ask how the platform reconciles conflicts and how it handles version drift when a guideline is updated after a report is signed out.
3. Director sign-out workflow with an audit trail. Your licensed medical director owns the final report. The software should support human review, not bypass it, and record who changed what and when.
4. Integration with your LIS and the EHR. Look for structured intake of already-called genotypes plus outbound delivery via FHIR, CDS Hooks, and SMART on FHIR.
5. Migration and validation support. Bulk re-processing of historical cases, side-by-side comparison against prior reports, and white-label output that matches your lab's letterhead.

Why Does Downstream-of-Calling Architecture Matter for Your Lab?

This is the single most important architectural question, and it is where many labs get the framing wrong. SignalPGx is interpretation and reporting software that intakes already-called genotypes from VCF, PharmCAT, Agena MassARRAY, or CSV. It is explicitly downstream of variant and star-allele calling; it does not align reads and does not call variants or diplotypes.

That boundary is a feature, not a limitation. You have already validated your NGS or microarray assay and your calling pipeline under your CLIA license. A downstream reporting layer plugs into that validated output without duplicating or displacing it, so your existing analytical validation stays intact and only the interpretation-and-reporting step is replaced.

It is also a meaningful architectural distinction from PGxPortal, which performed calling-adjacent diplotype work; a downstream-only layer keeps the interpretation step cleanly separated from calling. This is an operational-fit point, not a regulatory claim of any kind: SignalPGx is not FDA-cleared and is not a diagnostic test, and its architecture implies nothing about FDA status.

How Should a Replacement Handle Evidence Reconciliation and CPIC Maintenance?

Interpretation quality lives or dies on evidence handling. SignalPGx draws on a broad evidence base spanning 50-plus pharmacogenes, 950-plus medications, and 7,700-plus drugs with documented drug-drug interactions, pulled from 16 named sources including CPIC, DPWG, FDA, OpenFDA, HCSC, EMA, Swissmedic, PMDA, PharmGKB, PharmCAT, PharmVar, ClinVar/ClinGen, RxNorm, DailyMed, Onsides, and gnomAD. The medication intelligence graph makes each recommendation traceable back to the source that produced it.

The harder problem is time. Guidelines move, and a report that was defensible last quarter can fall out of step when CPIC revises an allele-function assignment or a dosing recommendation. A deterministic interpretation engine gives you reproducible output for the same genotype input, and living reanalysis flags previously signed-out reports affected by a guideline change so your director can decide whether a case warrants a reissued report. That is the mechanism that prevents silent version drift, not a promise that reports never change.

Where Does Director Sign-Out Fit in the Workflow?

Every report is your report. SignalPGx is designed around human-in-the-loop review: the software assembles genotype-to-guidance content and surfaces the supporting evidence, and your lab's own licensed medical director reviews and signs out each case under your CLIA license. The software helps the director; it does not interpret or sign out as a service, and final prescribing decisions rest with the treating physician.

Where AI assists, it is bounded. SignalAI is a guardrailed, cite-or-refuse assistant that supports reviewers with sourced context and declines when it cannot cite, never acting autonomously. Underneath, an audit trail and access controls record who reviewed and released each report, which is exactly what you need when a payer, an inspector, or a treating clinician asks how a result was produced. For a deeper look at how raw calls become defensible, signed-out reports, see the walkthrough on the genotype-to-guidance pipeline.

Does It Integrate via FHIR, CDS Hooks, and SMART on FHIR?

A reporting layer that cannot reach the ordering clinician creates manual work and delays. Confirm that any replacement delivers structured output your downstream systems can consume, not just a PDF. SignalPGx supports EHR-facing integration through FHIR resources, CDS Hooks for point-of-prescribing alerts, and SMART on FHIR for embedded, read-only report views inside the clinician's existing workflow.

The practical test during evaluation is whether a result can travel from your LIS into the EHR and back to the prescriber without a human re-keying data. Ask each vendor to demonstrate a genotype coming in from your pipeline and a structured, guideline-backed result going out to a test EHR. The mechanics of standing this up, including where CDS Hooks and SMART launch fit, are covered in the guide to PGx EHR integration with FHIR and CDS Hooks. Integration depth is often what separates a reporting tool that scales from one that quietly adds FTEs.

How Do You Plan the Migration: Timeline, Validation, and Cutover?

Treat replacement as a validation project, not a switch you flip. A workable sequence keeps your current process running until the new one is proven.

1. Scope and map. Inventory the genes, drugs, and report templates you use today, and identify the input format your pipeline produces, whether VCF, PharmCAT, MassARRAY, or CSV.
2. Parallel run. Process a representative set of historical cases through the new platform and compare its output, line by line, against your prior signed-out reports.
3. Reconcile differences. Where results differ, determine whether the cause is a guideline update, a source difference, or a defect, and document the resolution with your medical director.
4. Validate and template. Finalize your white-label report layout, confirm branding, and complete your internal verification under your CLIA quality system.
5. Cut over. Move new orders to the platform, keep read access to legacy reports, and monitor the first weeks closely.

If you are also weighing an in-house build against a vendor for the long term, the build-versus-buy analysis for PGx reporting lays out the maintenance burden that usually decides it.

Why SignalPGx Fits Labs Already Running Variant Callers

The reason SignalPGx maps cleanly onto a displaced PGxPortal lab is structural. You already own the hard, validated part, your assay and your calling pipeline, and you already have a licensed medical director who signs out cases. What you lost was the layer that turns validated calls into guideline-backed, integration-ready reports. That is precisely the layer the SignalPGx platform provides, and only that layer.

It does not ask you to re-validate calling, it does not call variants or diplotypes, and it does not position itself as a diagnostic service or claim FDA clearance. It reconciles a broad, sourced evidence base, keeps a deterministic engine reproducible, flags guideline drift for director review, and delivers structured output to the EHR. That combination is designed to slot into your existing CLIA workflow rather than replace it wholesale.

The Bottom Line for Displaced PGx Labs

The PGxPortal discontinuation was a bounded event with a bounded fix. You do not need to rebuild your test; you need to replace one layer, the interpretation and reporting software, with something that respects the boundaries your lab already operates within. Audit candidates on the five capabilities above: evidence depth and provenance, guideline reconciliation and version maintenance, director sign-out with an audit trail, LIS and EHR integration, and real migration support.

Do that evaluation rigorously and the decision gets simpler, because most of the criteria are objective. Choose a downstream-of-calling reporting layer that keeps your validated pipeline intact, keeps your medical director in control of every sign-out, and keeps every recommendation traceable to a named source. Regulatory frameworks around LDTs may keep shifting, so favor a partner whose architecture is transparent and whose evidence handling you can inspect and defend, and confirm any regulatory question with your own counsel before you rely on it.