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?
Record format: question; proposed response; source or method; limitation. Use a dated correction only if the underlying wording or evidence changes. Record PHARMACY-28564.
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.
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.
Image metadata can also contain sensitive information. Check the exported file with a suitable metadata viewer and share only the copy you have inspected.
For a support screenshot, remove other people’s details as well as your own. Summarise irrelevant portions instead of uploading an entire conversation.
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.
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.
Clarification for “Redacting a review: which details should stay private?”: the point beginning “Remove names, addresses, prescription identifiers, contact details, account references, tracking tokens…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
Limit of the answer in “Redacting a review: which details should stay private?”: “Remove names, addresses, prescription identifiers, contact details, account references, tracking tokens…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.
Method note for “Redacting a review: which details should stay private?”: use “Remove names, addresses, prescription identifiers, contact details, account references, tracking tokens…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.
Correction note for “Redacting a review: which details should stay private?”: retain the wording beginning “Remove names, addresses, prescription identifiers, contact details, account references, tracking tokens…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.
Summary draft for “Redacting a review: which details should stay private?”: the answer addresses “Remove names, addresses, prescription identifiers, contact details, account references, tracking tokens…”; the related point is “Keep originals privately rather than destroying…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.