MétaCan
Menu
Back to cohort
Record W4318479027 · doi:10.3390/life13020336

Effectiveness of Manual Trigger Point Therapy in Patients with Myofascial Trigger Points in the Orofacial Region—A Systematic Review

2023· review· en· W4318479027 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueLife · 2023
Typereview
Languageen
FieldBiochemistry, Genetics and Molecular Biology
TopicMyofascial pain diagnosis and treatment
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsMedicineRandomized controlled trialOrofacial painPhysical therapyManual therapyMyofascial pain syndromePhysical medicine and rehabilitationAlternative medicineSurgeryPathology

Abstract

fetched live from OpenAlex

The objective was to compile, synthetize, and evaluate the quality of the evidence from randomized controlled trials (RCTs) regarding the effectiveness of manual trigger point therapy in the orofacial area in patients with or without orofacial pain. This project was registered in PROSPERO and follows the PRISMA guidelines. Searches (20 April 2021) were conducted in six databases for RCTs involving adults with active or latent myofascial trigger points (mTrPs) in the orofacial area. The data were extracted by two independent assessors. Four studies were included. According to the GRADE approach, the overall quality/certainty of the evidence was very low due to the high risk of bias of the studies included. Manual trigger point therapy showed no clear advantage over other conservative treatments. However, it was found to be an equally effective and safe therapy for individuals with myofascial trigger points in the orofacial region and better than control groups. This systematic review revealed a limited number of RCTs conducted with patients with mTrPs in the orofacial area and the methodological limitations of those RCTs. Rigorous, well-designed RCTs are still needed in this field.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: Systematic review
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.052
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0020.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.025
GPT teacher head0.309
Teacher spread0.284 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it