iSTAT PT Plus transition
25 followers
4 Likes
+ 1 more
Good Morning!
My sister hospital and I are in the process of transitioning from the iSTAT PT cartridge to the iSTAT PT plus cartridge but the correlation between the PT plus cartridge and our Stago analyzer is failing every sample. The correlation is showing a consistent increased for the PT on the Stago. We are using a red top tube tested immediately on the iSTAT and then the blue tube for the Stago. Is anyone else experiencing the same issues? Does anyone have any insight as to why?
My sister hospital and I are in the process of transitioning from the iSTAT PT cartridge to the iSTAT PT plus cartridge but the correlation between the PT plus cartridge and our Stago analyzer is failing every sample. The correlation is showing a consistent increased for the PT on the Stago. We are using a red top tube tested immediately on the iSTAT and then the blue tube for the Stago. Is anyone else experiencing the same issues? Does anyone have any insight as to why?
21 Replies
Displaying items 16-21 of 21 in total
Reply
Subgroup Membership is required to post Replies
Join POCT Listserv now
Suggested Posts
Topic | Replies | Likes | Views | Participants | Last Reply |
---|---|---|---|---|---|
CLIA Lab Director Site Visit Form/Checklist | 0 | 0 | 118 | ||
Rapid molecular tests for Covid, FluAB, RSV and Strep A | 0 | 0 | 244 | ||
Hemosonics Quantra CPT Code | 4 | 0 | 103 |
Precision looks great. Samples via venipuncture or capillary collection on regular people all look good. I am just trying to figure out how to get some elevated INR results for this whole blood validation.
At the University of Minnesota Medical Center, Fairview, we had to upgrade our DE to v2.11 also. We are not going to have to generate a new test code as our middleware sends out the same, results process and collection was the same, and location in EPIC would be the same. We will just make sure we have used up our PT/INR cartridges before starting the PTPLUS cartridges (is what i was advised should be the process).
We were not able to validate the Reportable Range at the upper end, so we adjusted the settings in DE so it will only report out our verified range.