-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perfusion data entry #620
Comments
Time from first craniotomy to perfusion (overall brain health/infection) |
Regarding the quality of the perfusion, some tell-tale signs of a poor perfusion are: bleeding from the nose during perfusion, heart stopped beating before needle insertion, liver does not lose red color during perfusion (blanching) |
After talking with Steven, a more thorough list is:
fields with other are machine readable ; indicate differences in perfusion notes |
@anne-urai , I did not add ''Time from first craniotomy to perfusion'' as this can be already retrievable from Alyx via the different surgery dates. Would it be simpler for analysis to have a field with this information in though (could be done automatically @rossant ?)? |
Hi all, I just wanted to copy-paste some of my discussion with @GaelleChapuis here for you all to see: I believe the best way to assess perfusion is by confirming the liver has cleared of blood during the flushing with PBS. This provides a convenient and clear (no pun intended!) classification between a 'good' and 'poor' perfusion. Everyone should really be using the EM grade 16% Formaldehyde vials I listed on the Perfusion SOP, as the formaldehyde made from these will be very pure, and will not contain any small particles of PFA, that often remain when you depolymerise PFA to make formaldehyde solution, which can occlude small blood vessels during perfusion (there is a paper on this, but I cannot find it right now). The perfusion SOP currently lists a standard of 24 hours at 4C, although I think longer would not be a problem. Under-fixation could be a problem though, and it would be good to check the fixation time to see if it makes any impact. In terms of assessing perfusion quality, in my experience the perfusion is either good, and the liver will clear of blood, or if you mess it up, the liver just doesn't clear. As the quality of perfusion really is determined by how good a fit your needle makes with the heart ventricle - if you puncture the heart so your perfusate flows out of that hole and not through the circulatory system, you have a bad perfusion. Otherwise it "should" be good. If perfusate starts to come out through the nose, this could potentially indicate a bad perfusion, although that does vary somewhat, as this just means the needle has punctured the wall between left and right ventricles, and now is pumping perfusate through both the left and right ventricles - with perfusate going through the right ventricle heading through the lungs and then eventually being released via the nose. But if this does happen, often I find the perfusion is still OK. I would also just like to add that when I do a perfusion I actually cull before beginning the perfusion with an overdose of isoflurane, which I deem as more humane. In this state, the heart is in fibrillation, which makes it a lot easier to setup the perfusion, and I still get absolutely fine perfusions and subsequent histology. So it isn't necessary for the heart to be beating - this is a myth that seems to perpetuate in histology circles. I should also say I have used this method for perfusions for the past 5-6 years, and I only do histology, so it has been well validated! I have incorporated these notes into the Perfusion SOP. |
@rossant when could this be implemented? |
Here's a proposition: class Perfusion(BaseAction):
pfa_solution = models.ForeignKey(
PerfusionSolution, null=True, blank=True, on_delete=models.SET_NULL,
related_name='pfa_solution')
liver_cleared = models.BooleanField(blank=True, default=False)
post_fixation_time = models.PositiveIntegerField(blank=True, default=0)
post_fixation_temperature = models.ForeignKey(
PerfusionTemperature, null=True, blank=True, on_delete=models.SET_NULL,
related_name='post_fixation_temperature')
transport_time = models.PositiveIntegerField(blank=True, default=0)
transport_temperature = models.ForeignKey(
PerfusionTemperature, null=True, blank=True, on_delete=models.SET_NULL,
related_name='transport_temperature')
transport_solution = models.ForeignKey(
PerfusionSolution, null=True, blank=True, on_delete=models.SET_NULL,
related_name='transport_solution')
time_to_imaging = models.PositiveIntegerField(blank=True, default=0) As a BaseAction, this new model will also have the following fields:
There will be initial fixtures, as follows:
Is that correct? |
1 .--------------------------------------------------------------- Based on feedback, I would suggest making an object '' Solution change '' that contains the fields:
Fields for solution type:
That object could be added as needed. Users would input to start with: (example)
Then upon changing into PBS or transport solution: (example)
Remove field:
Edit field:
2. ----------------------------------------------------- 3.----------------------------------------------------- Remove temperature of transport, and put instead:
4.-----------------------------------------------------
|
The histology WG noted that there is some variability in the auto-fluorescence brightness signal. There seems to be some unknown cause of protocol discrepancy. To help us tackling this, we would like to add some fields, notably:
Exact implementation to be discussed.
The text was updated successfully, but these errors were encountered: