Experience with the Gambro Phoenix Hemodialysis Machine using Diascan and Exalis in a Pediatric Hemodialysis Unit
Bibliographic record
Abstract
Introduction: In 2001 our Renal Dialysis Unit underwent a major renovation to five stations. The new space and funding allowed for acquisition of new state‐of‐the‐art hemodialysis machines. We describe our experience with the Gambro Phoenix with Diascan and Exalis. Prior to the move an evaluation was undertaken. Criteria for selection with a scoring tool were utilized to rate machine performance for use in children. The decision for the Gambro Phoenix machine was based on: the performance rated highly due to ease of set up; large viewing touch screen; compatibility with existing equipment; benefits of online clearance monitoring (Diascan); network data management system (Exalis) and the future availability of blood volume monitoring (Hemoscan). Our program was the first center to dialyze a pediatric patient on the Phoenix machine in Canada. Patients and results: 13 patients (age 2–23 years) were hemodialyzed between May 2002 and September 2003 for periods of 2 week to 16 months, greater than 5000 h of dialysis time. The move was not uneventful. During the first months of operation issues such as inadequate electrical supply for the new machines, reverse osmosis (RO) pump failure, leaks, and no emergency power to the RO were prevalent. The new software also exposed glitches. Subsequent Phoenix use proceeded uneventfully. Staff were able to problem solve easily with clinical and technical support from Gambro Canada. Education for the online clearance monitoring, Diascan and Exalis, was necessary. No major problems with dialysis were encountered. The benefits and reliability of Diascan have been previously described (Lindsay RM, Sternby J, Semin Dial. 2001; 14:300). Diascan readings provided real‐time measurement of sodium (Na), which correlated well with laboratory values. Automatic readouts of Kt/V allowed for monitoring of dialysis adequacy which was consistent with calculated percent reduction in urea (PRU). At this point, use of the Phoenix has been demonstrated to work well in a pediatric facility.
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.002 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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".