Platform, configuration and devices · C0836
How many jurisdiction profiles does one deployment load, and who has to sign it?
Designed, not yet built
Short answer
No. The specification describes it, but the pilot does not include it. REQ-0105 says each deployment must load exactly one active Jurisdiction Profile per country context, signed by AuroraMed and countersigned by the customer's privacy officer/DPO. Its acceptance check: deployment refuses to start clinical services without a valid profile; the profile hash is on the ledger.
This is designed, not built.
- Specification item
- REQ-0105
- 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
- Can administrators add new members of an artifact family without waiting for a software release? Designed
- What can a jurisdiction profile configure, such as retention, residency and breach timers? 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
- Who signs each release of the element type registry, and how is it checked before use? Designed
See it in context: Configuration, Element Type Registry and Jurisdiction Profiles · Search the help center · Ask a question