No platform could do what Genate needed. So we built one.
Genate needed genetic data held to HIPAA requirements, algorithms we could version, and reports a clinician and a patient could both read. SNPhub does all three.
The platform that turns a genotype into a clinical deliverable
SNPhub is the secure platform behind every Genate test. Ordering, chain of custody, laboratory results, analysis, reporting and dispensing run in a single system, built on AWS and operated to HIPAA requirements.
Why we built it
Three jobs, one system
- 01
Compliant storage
Genetic data held to HIPAA requirements — encrypted at rest under a key we control, recoverable to a point in time, with every action against it logged.
- 02
The analysis layer
Our algorithms run against that data inside the platform. Each one is named and versioned, so any result can be traced to the analysis that produced it.
- 03
One portal
Providers, patients, partners and referral sources sign in to the same system and see the reports their role gives them.
The gap it closes
A genotype file is not a clinical deliverable.
Genetic data arrives as a list of variants — SNPhub translates lab data, matching a result to the right patient, running the analysis, rendering it in language that supports a conversation, and connecting it to actionable recommendations.
From order to outcome
-
Order.
A provider orders test kits through the portal. The kit is assigned to the patient at registration, so the result connects providers and patients.
-
Collection.
The kit is shipped and tracked in both directions. Status is visible to the practice and patient throughout, without a phone call.
-
Laboratory.
A CLIA-certified laboratory processes the sample and returns genotype data directly into the platform.
-
Analysis.
Versioned algorithms run against the result.
-
Report.
The provider report and the patient report are generated from that single analysis.
The algorithm layer
Configuration, not code.
Algorithms in SNPhub are configuration, not code. Each is a named, versioned object with its own lifecycle status, carrying the variants it reads, the weights it applies, the thresholds that separate one result band from another, and the pathway logic that produces the output.
Any result can be traced to the exact algorithm that produced it. And the science can advance without the platform being rebuilt around it.
Two reports, one analysis.
The provider report and the patient report are generated from the same analysis. They differ in depth and in language, never in conclusion. A clinician and a patient reading their own copies are reading the same result.
Built for practices
Built for practices, not logins.
Organizations hold the account and providers work beneath it. Access is scoped by role: a provider sees their own patients, a practice administrator sees the organization, a genetic counselor sees the reports they are supporting.
Supplement catalogs are configured per organization. Counseling sessions are tracked against the report they relate to.
Infrastructure and security
-
Built on AWS
SNPhub runs entirely on managed AWS infrastructure, defined as code and deployed through an automated pipeline. There are no hand-built servers in the system and no manual path to production.
-
Security and compliance posture
SNPhub was built to HIPAA requirements from the infrastructure up. Patient data is encrypted at rest under a key we control and encrypted in transit, records are recoverable to a point in time, access is scoped by role, and every action against the platform is logged. These are properties of the system, not procedures people are asked to follow.
What SNPhub is
SNPhub was built to run Genate. What it is, underneath, is a system for turning inherited variation into clinical action — securely, repeatably, and with every result traceable to the analysis that produced it.
Need to get genetic reports to patients?
We would be glad to demo SNPhub and walk through how it handles secure storage, analysis and reporting.