Dynamic Angular Petrissage as Treatment for Axillary Web Syndrome Occurring after Surgery for Breast Cancer: a Case Report
Bibliographic record
Abstract
BACKGROUND: In the context of breast cancer, axillary web syndrome (AWS), also called lymphatic cording, typically presents in the weeks after axillary surgery. This painful condition, likely lymphofibrotic in origin, restricts upper extremity range of motion (ROM). There is no established treatment, although physical therapy and other approaches have been used to variable effect. This report describes treatment of a female client with AWS, who had recently undergone a unilateral simple mastectomy with sentinel node biopsy plus axillary dissection. METHODS: The client presented with pain upon movement (self-reported as 5 on the 0-10 Oxford Pain Scale), visible cording and restricted use of the ipsilateral upper extremity. Clinical assessment included determining the extent of AWS cording (taut, from axilla to wrist) and measuring glenohumeral joint ROM (140° flexion by goniometer). A therapeutic massage with movement protocol, termed dynamic angular petrissage, was administered over two sessions: Swedish massage combined with dynamically taking the limb through all possible angles of movement (passive ROM), controlling stretch and tension while simultaneously and segmentally applying petrissage and non-petrissage techniques to the underlying soft tissue. Careful attention was taken to not break the cord. Home care consisted of prescribed exercises performed by the patient. RESULTS: After Session One, pain was reduced (to 0/10), ROM improved (to 170° flexion), and cording was visibly reduced. After Session Two the cord was residually apparent only on hyperextension, with no ROM restrictions in glenohumeral joint flexion. Follow-up at three months revealed absence of visual or palpable evidence of cording, unrestricted glenohumeral joint ROM, and absence of movement-associated pain. CONCLUSION: The signs and symptoms of AWS were quickly and effectively eliminated, without causing any pain or discomfort to the client. We propose that dynamic angular petrissage may be an efficient and safe treatment approach for reducing the pain, mobility restrictions, and cording of AWS.
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.000 | 0.002 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.006 | 0.003 |
| Insufficient payload (model declined to judge) | 0.002 | 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".