Platform, configuration and devices · C0837
What can a jurisdiction profile configure, such as retention, residency and breach timers?
Designed, not yet built
Short answer
REQ-0106 is a top-priority requirement for all three tiers: Jurisdiction Profiles must configure at least: language set, legal bases allowed, consent formats, data residency, retention periods, breach-notification timers, subject-rights SLA, DPO requirement, workforce analytics switch, and crypto-erasure acceptance. Not yet. It is designed in the specification and not built in the pilot. To verify it, the specification says each parameter is present in the profile schema; missing parameters block activation; parameters with unknown legal value are shown as (still an open decision). Parts of it are explicitly marked as open in the specification.
This is designed, not built.
- Specification item
- REQ-0106
- Specification priority
- P0 (of P0 to P3)
- Tiers
- Small, Medium, Large
Status as of September 30, 2026. Version 0.2.0, synthetic data only. See what's built today. Not legal, medical or security advice.
Related answers
- How many jurisdiction profiles does one deployment load, and who has to sign it? Designed
- Does AuroraMed ship profile templates for US (HIPAA baseline), BR (LGPD), CO, CL, MX, PE and AR, each with values marked [verify] until counsel confirms? Designed
- Can a clinic switch between the base, local, strict and sovereign privacy tiers? Designed
- Can administrators add new members of an artifact family without waiting for a software release? Designed
See it in context: Configuration, Element Type Registry and Jurisdiction Profiles · Search the help center · Ask a question