Data Safety
Practical guidance for giving Workbench enough context to help without giving it information that should stay elsewhere.
More useful context does not mean more sensitive data.
For a strong result, bring the material that explains the job: permitted notes, field names, business rules, deadlines, constraints, audience and the outcome you need. When the original source contains restricted information, use the lowest-information path that still lets the work be completed.
Permitted files, de-identified or aggregated facts, schemas, process notes, policies, business rules, constraints and independently synthetic examples.
PHI/ePHI, direct patient/client identifiers, SSNs, credentials, full bank/card data, sensitive HR case files, privileged legal content and security secrets unless specifically authorized.
De-identification
Removing or changing a name alone may not make a real record safe to share. Follow your organization’s approved de-identification process and applicable legal or regulatory requirements.
When in doubt
Describe the structure or business rule without the underlying protected record, or complete the source-sensitive portion in the approved system.