Minimum necessary payload

Description

The pattern that constrains what data a given message, API call, or activation carries to only the fields the communication actually needs, regardless of what the upstream system has available. The architectural counterpart to data minimization at collection, applied at egress rather than ingestion. Especially load-bearing under HIPAA's minimum-necessary rule and under GDPR's purpose-limitation principle.

Common failure modes

• 01Payload schema mirrors the source record schema by default, so personally identifying or sensitive fields ride along with every message because removing them was extra work
• 02Minimum-necessary check applied only to new integrations, never retroactively to existing ones that were grandfathered with maximalist payloads
• 03Payload composition reviewed at architecture time and never re-reviewed as fields are added upstream, so the payload accretes additional fields silently
• 04Audit log captures that the message was sent but not what was in it, so post-hoc minimum-necessary review is structurally impossible

Tools for this pattern

The capability a stack needs to run this pattern, and the vendors that provide it, on Martech Stack Builder.

• NeedsData Access Control
• RelatedPrivacy Vault / Tokenization

Recipes composing this pattern

No published recipes compose this pattern yet.