UGT1A1 and atazanavir: name the bilirubin question

A report section labelled “liver risk” may sound much broader than the evidence it summarises. For UGT1A1 and atazanavir, it is important to identify the actual endpoint: bilirubin changes and their consequences are not a complete description of liver health or treatment effectiveness.

The CPIC atazanavir guideline publication discusses UGT1A1 in relation to bilirubin handling and the likelihood of bilirubin-related treatment discontinuation. It does not make a UGT1A1 result a general test of whether every liver function is normal.

The heading may be broader than the evidence

Consider a fictional report with a coloured row beside atazanavir. The explanatory text discusses visible yellowing and whether that could affect continued use. A reader copies the row into a notebook as “liver damage risk”. That rewrite changes the meaning. It replaces the specified outcome with a different, broader clinical claim.

A better note keeps the original endpoint wording. If the report is unclear about what the colour summarises, the question is “Is this about bilirubin, another adverse effect, or something else?” The purpose is to recover the report’s meaning, not to classify a person’s liver health from a gene label.

This distinction is also useful when two sources seem to disagree. One may discuss a biochemical change, another visible jaundice, and another treatment discontinuation. Those outcomes are connected but not identical. Before comparing claims, identify which one each source actually measured or addressed.

A gene result is not a bilirubin measurement

The NCBI Medical Genetics Summary for atazanavir and UGT1A1 describes the medicine–gene relationship. In this research session its official indexed summary was readable, while the full page was blocked. We use it for the named relationship, not a claim that every table or label revision was inspected.

A genetic result, a current blood measurement and a symptom description belong on separate lines. The genetic result records tested inherited information. The measurement records what was measured at a given time, with its units. A symptom account records what the person noticed. None automatically supplies the missing details of the others.

In a fictional worksheet, Theo writes “UGT1A1 report available” on one line and leaves the current bilirubin line blank because no result is at hand. Theo does not fill that blank with a predicted number. This may seem obvious on paper, but automated summaries and short labels can blur the same boundary if the measurement is omitted.

Do not turn a possible explanation into a diagnosis

The report may provide relevant information for a professional assessing a medicine-related question. It does not establish the cause of yellow skin or eyes. Nor does a UGT1A1 label let a reader diagnose a benign inherited condition or dismiss a new symptom.

The NHS jaundice advice says to seek an urgent GP appointment or help from NHS 111 if the skin or whites of the eyes look yellow. Keep that advice visible. The existence of a pharmacogenomic result is not a reason to wait for an educational article, a report lookup or a routine future review.

This safety boundary is specific to the symptom question. It does not imply that every person with a UGT1A1 result is ill. It simply prevents a gene–medicine explanation from being used as a personal diagnosis when the current symptom has not been assessed.

Ask about the exact outcome and medicine

For a routine report discussion, bring the complete document and the actual medicine list. Ask what endpoint the relevant section addresses and whether its interpretation applies to the current prescription. If the report lists several drugs under the same gene, keep their sections separate; sharing a gene does not establish an identical recommendation.

You can also ask whether the result is being used as background information, alongside a current measurement, or as part of another assessment. Recording the answer helps avoid later retelling it as “the gene explains everything”. The professional may be addressing a narrower question than the report’s front-page heading suggests.

The practical takeaway is to replace broad shorthand with a named endpoint. Save “UGT1A1–atazanavir, bilirubin-related question” rather than inventing a general liver score. It leaves room for the actual measurement, symptoms and clinical assessment to remain visible instead of being swallowed by one coloured row.

Scope and source access

Research accessed 4 October 2026: the 2015 CPIC guideline PDF, the NCBI indexed summary and the NHS jaundice page. The historical guideline publication is not presented as a complete current live-table audit. No diagnosis, treatment choice or medication change is offered.