Standards over one-off interfaces

Many labs still return PGx results as a static document that a clinician has to find, open, and interpret alone. That approach fragments the workflow and buries actionable gene-drug findings. Delivering results over shared interoperability standards keeps every finding structured, queryable, and available where prescribing decisions are actually made.

SignalPGx maps every result to coded FHIR resources. Diplotypes, phenotypes, and therapeutic implications are expressed as FHIR R4 Observations and DiagnosticReports, so any conformant EHR can ingest, index, and display them. The result is not a document to chase, but discrete data the record can act on.

FHIR R4 and HL7 ORU for the record

Different systems speak different dialects, and a result that cannot be parsed is a result that gets ignored. Meeting each EHR on a format it already trusts removes that friction before it starts.

SignalPGx supports both modern and established transports. Delivered results are:

• structured

• coded

• auditable

FHIR R4 for modern APIs, HL7 v2 ORU for legacy interfaces, one reconciled report behind both.

CDS Hooks at the point of prescribing

A result buried in a lab tab does nothing when a clinician is actively ordering a new medication. The guidance has to arrive at the moment of the decision, not after it.

CDS Hooks lets SignalPGx surface a gene-drug advisory inside the prescribing workflow as the order is written. When a patient's genotype affects the chosen drug, a card appears with the relevant CPIC guidance and a link to the full report. SignalAI flags the interaction and the medical director's signed-out interpretation is what the card carries, while the ordering clinician stays in control of the final decision.

SMART on FHIR for the full report

A single alert card cannot hold an entire multi-gene report. Clinicians sometimes need the complete picture without leaving the chart they are already in.

SMART on FHIR launches the full SignalPGx report as a read-only view embedded directly in the EHR, authenticated against the patient in context. Clinicians can review the patient's results across all 50 pharmacogenes without a separate login or a second system to learn.

A Patient Passport patients control

Patients move between providers, and their genotype does not change when they do. A PGx result should follow the person rather than stay locked inside one health system.

The Patient Passport is a revocable QR link to a minimal-PHI patient view.

Patients can share it with any clinician, only essential information is exposed, and the issuing lab can revoke access at any time. The genotype travels with the patient while the lab keeps full control of the data.

decision = model.predict(input_data)
execute(decision)

Living Reports keep delivery current

Delivery is not a one-time event. Guidelines evolve and patients start new medications, so a report that was accurate at sign-out can quietly drift out of date.

Living Reports watch for change:

1. when CPIC or DPWG guidance shifts

2. when a patient's medication list changes

3. when a flagged report needs re-review

When something changes, the report is re-analyzed and any flagged case is routed back to the medical director for a fresh sign-out, then re-delivered downstream automatically.

Conclusion

Integration is not a feature bolted onto a report; it is how the report becomes clinically useful in the first place.

Labs that deliver evidence-graded PGx results over FHIR, HL7, CDS Hooks, and SMART on FHIR gain a real advantage: guidance at the point of care, running on secured AWS with strict tenant isolation and full audit trails, and most labs live in five to seven days. SignalPGx is not a diagnostic test and never replaces the clinician; final prescribing always stays with the ordering physician.