Case 18 — A useful source-review update: what changed since the opening post?
Add a dated status block with the original concern, the response actually received and the point still outstanding. Do not label the case resolved until the stated remedy is documented.
Case 18 — A useful source-review update: what changed since the opening post?
This reference thread contains an initial concern, a support reply and a proposed resolution. How should its opening summary be updated without turning an unresolved case into a positive review?
Exercise PHARMACY-00298/18: address this question within its stated limits.
Case 18 — A useful source-review update: what changed since the opening post?
Does the support message promise an action or confirm that it happened? Quote only the necessary short phrase and identify it as a promise when completion is not established.
Case 18 — A useful source-review update: what changed since the opening post?
Keep transaction-service observations separate from product-quality claims. A refund or a delivered parcel can resolve a service issue without establishing medicine identity, efficacy or safety.
Case 18 — A useful source-review update: what changed since the opening post?
A correction entry should show the old statement, the revision and the supporting record. If a claim cannot be substantiated, remove its assertion from the summary and explain the correction.
Case 18 — A useful source-review update: what changed since the opening post?
Avoid trust scores based on the number of friendly replies. Each material claim should have its own evidence status, including reports that remain disputed.
Case 18 — A useful source-review update: what changed since the opening post?
The final index entry can say documented, unresolved or corrected, with a date and links to the relevant posts. This template is not an actual customer endorsement.
Case 19 — Redacting a review: which details should stay private?
A draft review includes a shipping label, a medicine label and a support screenshot. Which details should be removed from the public version while preserving evidence for a professional or service enquiry?
Exercise PHARMACY-00298/19: address this question within its stated limits.
Case 19 — Redacting a review: which details should stay private?
Use opaque redactions in a flattened exported copy, then reopen that copy and inspect it at full size. Do not rely on a translucent marker or a reversible edit layer.
Case 19 — Redacting a review: which details should stay private?
Remove names, addresses, prescription identifiers, contact details, account references, tracking tokens and scannable codes from the public copy. Keep originals privately rather than destroying the only evidence.
Case 19 — Redacting a review: which details should stay private?
Image metadata can also contain sensitive information. Check the exported file with a suitable metadata viewer and share only the copy you have inspected.
Case 19 — Redacting a review: which details should stay private?
Batch and product information may be relevant to a pharmacist or regulator. Decide what belongs in that private enquiry rather than automatically publishing every field or redacting the professional’s only useful evidence.
Case 19 — Redacting a review: which details should stay private?
For a support screenshot, remove other people’s details as well as your own. Summarise irrelevant portions instead of uploading an entire conversation.
Case 19 — Redacting a review: which details should stay private?
The public post should still state the question, the sequence of events and the evidence that can be described safely. Privacy protection need not turn it into an unsupported accusation.
Case 20 — A source review checklist that separates evidence from reassurance
How can a review template make evidence gaps visible without asserting that a seller is safe?
Exercise PHARMACY-00298/20: address this question within its stated limits.