Clinical Configuration
Your organization doesn't manage clinical rules, but the governance process is documented here for transparency. Atticus manages care plans, prescribing safety, screening rules, and AI prompts through a structured process that treats clinical configuration with the same rigor as code deployment.
Clinical configuration is managed by Atticus Health's clinical team. This page provides transparency into how clinical rules are governed, reviewed, and applied across your program.
What's Governed
Every configuration change moves through a proposal workflow — draft, review, approval, apply — before it affects care. Nothing reaches production without deliberate human review.
Changes are managed by Atticus's clinical team, ensuring consistent, evidence-based care across all sites. A single proposal can touch multiple services and applies atomically: if any part fails, the whole thing rolls back, so partial updates never reach patients.
Clinicians can describe rules in natural language, and AI suggests structured conditions for review. A visual rule builder supports 34+ operators, AND/OR logic groups, and nested conditions — rendered as readable English so clinicians verify intent without reading code. Humans always review and refine before a rule enters the proposal workflow.
Every proposal records who created it, who reviewed it, what changed, and when it was applied — with all review comments preserved for compliance.
Why Governance Matters
Clinical configuration directly affects care recommendations, medication dosing, and screening protocols. A misconfigured rule could suppress a critical screening or surface incorrect dosing. The governance workflow makes configuration changes deliberate, reviewable, and reversible — treating clinical configuration with the same rigor as code deployment.
How It Works
- Create proposal — Select a configuration domain, make changes in the editor, and submit as a proposal
- Review — Reviewers see an inline diff of exactly what changed, with context for the affected domain
- Approve — Authorized reviewers approve or request revisions with comments
- Apply — Approved changes deploy atomically across all affected services. If any service rejects the change, the entire proposal rolls back
- Audit record preserved — The full lifecycle — creation, review comments, approval, and application timestamp — is retained
Configuration Categories
| Category | What's Managed |
|---|---|
| Clinical care | Care plans, care plan tasks, care offerings |
| Medication & safety | Dosing templates, prescription instructions (SIGs), drug groups |
| Patient education | Education materials, forms |
| Clinical decision support | Rules, AI prompts, diagnoses |
| Operational | Locations, appointment types, resource items |
Each domain is schema-driven. Adding a new configuration domain requires a schema entry — no application code changes.