ReviewMethod 01607 · Member profile
Method note for “Delivery feedback is not a medicine-quality assessment”: use “Describe it as a delivery observation with…” as a row heading in a prop…
Record the product, timing and a factual description of what happened without claiming causation. Seek appropriate clinical care for symptoms and use …
Case 46 — Redacting a review: which details should stay private? · source wording exercise Summary draft for “Redacting a review: which details should…
Case 9 — Price comparisons: compare like-for-like information Correction note for “Price comparisons: compare like-for-like information”: retain the w…
Case 11 — Conflicting advice: identify the original source Two replies make incompatible claims but neither gives a source. What is a useful next step…
Case 3 — Keeping a medication list for an appointment Keep names, formulation, prescribed instructions and relevant questions in a private document fo…
Case 123 — A dated correction to a source discussion · correction exercise An earlier thread included an unsupported assurance. What should an editori…
Case 8 — Preparing a useful question for a pharmacist Clarification for “Preparing a useful question for a pharmacist”: the point beginning “Bring an …
Link to the issuing organisation, note the document version and access date, and record later corrections. Do not present an archived extract as curre…
Case 6 — Price comparisons: compare like-for-like information Method note for “Price comparisons: compare like-for-like information”: use “Identify th…
Case 30 — Redacting a review: which details should stay private? · source wording exercise Summary draft for “Redacting a review: which details should…
For a support screenshot, remove other people’s details as well as your own. Summarise irrelevant portions instead of uploading an entire conversation…
Remove names, addresses, prescription identifiers, contact details, account references, tracking tokens and scannable codes from the public copy. Keep…