The genetic report, read against the medicines the patient is actually on — and a hereditary cancer family’s cascade testing.
A genetic report arrives as a PDF and is filed. This puts it beside the prescription. The report is recorded as the laboratory issued it — its reference, its panel, and each finding in the laboratory’s own words — and the gene-drug flags are computed where three things meet: a finding that states a phenotype, a rule in the pharmacogenomic table this hospital has loaded, and a medicine the patient is currently prescribed. Every flag carries the rule, the table and the source that table came from, so a clinician can see whose guideline this is before acting on it. NOTHING IS PRE-LOADED. This product ships no gene-drug content at all: a table written from memory would be plausible, incomplete in ways nobody could see, and read as a reason to change somebody’s medicine, so what ships is the importer and an honest empty state, and the hospital loads the licensed table it uses. Hereditary cancer: a family with a hereditary cancer risk is kept as one record — the index patient’s gene, variant and classification as the laboratory reported them (linked to the filed report where there is one) beside every relative, whether they have been offered cascade testing, declined, been tested and what the laboratory found — so the family’s risk picture builds over years instead of living in a separate file for each relative. Genetics orders and interprets the tests; the app keeps the family’s status.
/genomicsgene.readWhat it does not do, by design. A listing with only benefits is an advertisement.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.