Serum alkaline phosphatase isoenzyme profiles in phenobarbital‐treated epileptic dogs
Bibliographic record
Abstract
BACKGROUND: Serum total alkaline phosphatase (AP) activity commonly is high in dogs receiving phenobarbital. Specific isoenzymes responsible for this increase are not well documented. OBJECTIVES: The purposes of this study were 1) to qualitatively and quantitatively describe serum AP isoenzymes in phenobarbital-treated dogs and 2) to monitor changes in serum AP isoenzyme activities associated with phenobarbital treatment over time. METHODS: Serum AP isoenzyme activities were determined in a cross-sectional study of 29 dogs receiving phenobarbital (duration of treatment 2 months to 6.5 years). Additionally, in a prospective study of 23 dogs, serum AP isoenzyme activities were determined before and 3 weeks, 6 months, and 12 months after the start of phenobarbital treatment. Isoenzyme activities were quantitatively determined using wheat germ lectin precipitation and levamisole inhibition, and qualitatively (ie, present or absent) evaluated using cellulose acetate affinity electrophoresis. RESULTS: In phenobarbital-treated dogs with high serum total AP activity in the cross-sectional study, the increase was due predominantly to increased activities of the corticosteroid-induced (C-AP) and liver (L-AP) isoenzymes. Prospectively, serum total AP and L-AP activities were significantly higher at 3 weeks, 6 months, and 12 months after the start of phenobarbital treatment compared with pretreatment values. Serum C-AP and bone isoenzyme (B-AP) activities were significantly higher after 6 and 12 months of treatment. B-AP accounted for only a small amount of the total AP activity. No unusual or previously unidentified AP isoenzymes were identified. CONCLUSIONS: Phenobarbital treatment was associated with increased C-AP and L-AP isoenzyme activities and with a minor increase in B-AP activity. No unique "phenobarbital-induced" isoenzyme was identified. Isoenzyme analysis does not appear to be useful for differentiating between high serum total AP due to phenobarbital therapy and other causes.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".