Tuesday, June 11, 2024

Systematic review search filter for Ebsco APA PsycInfo

I needed one of these but couldn't find one.   I did find a multi-database filter for Ovid, including APA PsycInfo, from Canada's Drug Agency, CADTH, so modified it to use in EbscoHost.

I could find no relevant publication types to match line 1 of the original filter, so replaced it with a modification of line 17, and then omitted line 17, so my filter has 22 and not 23 lines.    I changed Ovid's adj3 into N2 (and changed any other adjn in the same way).

This is the result.   I have not validated or tested this filter, although the original one is labelled as having had "pragmatic" testing.


S1 MR (systematic review or meta analysis)

S2 DE "systematic review" OR DE "meta analysis"

S3 ((systematic* N2 (review* or overview*)) or (methodologic* N2 (review* or overview*)))

S4 ((quantitative N2 (review* or overview* or synthes*)) or (research N2 (integrati* or overview*)))

S5 ((integrative N2 (review* or overview*)) or (collaborative N2 (review* or overview*)) or (pool* N2 analy*))

S6 (data synthes* or data extraction* or data abstraction*)

S7 (handsearch* or hand search*)

S8 (mantel haenszel or peto or der simonian or dersimonian or fixed effect* or latin square*)

S9 (met analy* or metanaly* or technology assessment* or HTA or HTAs or technology overview* or technology appraisal*)

S10 (meta regression* or metaregression*)

S11 (meta-analy* or metaanaly* or systematic review* or biomedical technology assessment* or bio-medical technology assessment*)

S12 (medline or cochrane or pubmed or medlars or embase or cinahl)

S13 (cochrane or (health N1 technology assessment) or evidence report)

S14 (comparative N2 (efficacy or effectiveness))

S15 (outcomes research or relative effectiveness)

S16 ((indirect or indirect treatment or mixed-treatment or bayesian) N2 comparison*)

S17 (multi* N2 treatment N2 comparison*)

S18 (mixed N2 treatment N2 (meta-analy* or metaanaly*))

S19 umbrella review*

S20 (multi* N1 paramet* N1 evidence N1 synthesis)

S21 (multiparamet* N1 evidence N1 synthesis)

S22 (multi-paramet* N1 evidence N1 synthesis)

S23 S1 OR S2 OR S3 OR S4 OR S5 OR S6 OR S7 OR S8 OR S9 OR S10 OR S11 OR S12 OR S13 OR S14 OR S15 OR S16 OR S17 OR S18 OR S19 OR S20 OR S21 OR S22

Sunday, May 26, 2024

Avian influenza (bird flu)

At the time of writing, there have been two human cases of avian influenza in the USA, connected to dairy farming,  and the Dutch daily newspaper De Volkskrant is asking if we are ready for a major outbreak of avian influenza in humans (in Dutch, and subscription needed).  

There are other posts on this blog about avian influenza, but from some time ago, so this is a more up to date list of suggested links.

The UK government's page on the latest situation in England, last updated on 26th April 2024, is a comprehensive page including links to information on how to spot avian influenza in birds, and a link to a page to get information on cases in animals in England (that page enables you as well to find details of any case of any notifiable disease in animals), and separate links to case information in the other home nations.

Direct links to government information in the other home nations are:

Northern Ireland

Scotland

- Wales - English, Cymraeg (ffliw adar)

Information from our geographical neighbours from the European Centre for Disease Prevention and Control.

Information from the Centers for Disease Control and Prevention in the United States.

Information from the NHS (last updated in January 2022).

Click this link for PubMed results, sorted by date with most recent first.   The search is filtered to humans, which may lose the most recent references, so to remove the human filter, untick the human filter in the options on the left of the results.  You will then find reports of research in birds or animals as well.   If there are articles at the top of the list under a "Found by citation matching" heading, note they may not be very recent.

Thursday, May 23, 2024

Defibrillators - an update

I have been browsing (sorry) back through some older posts on this blog.   An earlier post  from March 2023 was about the church's investigations into getting a public defibrillator (AED).

Things have progressed, so I think an update is needed.   This is it, and it also corrects a faulty assumption I had made!

I am involved with two churches, and both were discussing getting an AED.   I did the investigating for both, so could use experience gained in one for the benefit of the other.   

One church had a donation of money specifically to acquire a defibrillator, so just needed to decide how to acquire it, and how to maintain it.   

The other church had to decide those same things, but also raise the money.  That church applied to a Department of Health and Social Care fund (I don't know if it is still open), and paid £750 towards the device.  I don't know what criteria were used to decide who was successful.   The £750 was raised through donations, sales from a church book stall, and donations from external groups that use the building.

Both churches now have a defibrillator, installed late last year or early this year.   Here is what we have learned.

You need a qualified electrician to install the cabinet.   The cabinet is permanently connected to the mains via a trip switch, but not to charge the battery (this was my mistaken assumption) but to keep the cabinet lit, and heated if the external temperature is low.   The battery has a fixed lifespan (several years) and when it's flat, it gets replaced.

Then you need to register the device on The Circuit.   The person registering it ends up as the contact, and if the code to unlock the cabinet is given out by the emergency services, that contact person gets an email to say the device "may have been used today".     If the code is given out, the device is made unavailable on The Circuit, so the code is not given to anyone else.

We decided in both churches not to put the code on display or give it to church members or groups, or to external groups using the building.   The reasons for that were 1) we would not know if the device had been used unless remembered to tell us, and 2) the emergency services would not know the device had been used and could give the code to someone who then could potentially not access the device.

Both churches decided who would get emails if the code was issued, and who would then check if the device is present, and if it is, whether it has been used.  I am the Circuit contact and the checker for one of the churches and have had three emails since the start of the year.

The device has not actually been used on any of the three occasions.  On receipt of the email, I check if the pads are present, and if they are, if they are still sealed, and if the "rescue kit" (razor, scissors, wipes) has been used.   Pads and rescue kit would need replacing if not sealed, or of course if not present.    I then test the device.    If nothing needs replacing and all is working, I make the device available again on The Circuit.

For that church, I perform weekly checks on the device.   The devices in both churches actually test themselves.  The device in one church displays an error sign if there's something wrong, then we would need to read the manual or contact the supplier to find out what to do.    Someone else keeps an eye on this.

The device in the church where I am the tester could give us a report if we had bought a particular software (we didn't) and had a way to connect to the device.  (I need to check if the device will connect with the church wifi, which we installed after we had got the device).   In that church, once a week I make the device run a test.  I keep a note that I have done this, in a folder in the church office.  When I test it, I also check the cabinet for damage, and check the power supply is working.