1. Introduction
2. 1. Why FerroEHR exists
3. 2. Getting started
4. 3. Installation
   1. 3.1. Try it in Codespaces
   2. 3.2. Docker Compose
   3. 3.3. Kubernetes & Helm
   4. 3.4. Cluster hardening
      1. 3.4.1. The cluster: hosts, control plane, access
      2. 3.4.2. Images: build, provenance, scanning
      3. 3.4.3. The workload: security context & admission
      4. 3.4.4. Namespaces, network & policy
      5. 3.4.5. Secrets, detection & response
   5. 3.5. From source
   6. 3.6. Configuration reference
      1. 3.6.1. Server, database & telemetry
      2. 3.6.2. Authentication & access
      3. 3.6.3. Integrations
      4. 3.6.4. Audit
      5. 3.6.5. Privacy & data minimisation
      6. 3.6.6. CLI & production checklist
5. 4. Concepts
   1. 4.1. openEHR primer
   2. 4.2. System architecture
   3. 4.3. Storage architecture
   4. 4.4. The AQL engine
6. 5. Using the API
   1. 5.1. Resource walkthroughs
   2. 5.2. Content negotiation & errors
   3. 5.3. Problem types
7. 6. Querying with AQL
8. 7. Templates & validation
9. 8. Beyond the core
   1. 8.1. EHR Extract & messaging
   2. 8.2. FerroEHR as a federation node
   3. 8.3. Demographics
   4. 8.4. Terminology servers
   5. 8.5. Change events (AMQP)
   6. 8.6. S3 multimedia
10. 9. Security
    1. 9.1. Verifying releases
    2. 9.2. Threat model
    3. 9.3. Data protection impact assessment
    4. 9.4. Records of processing
    5. 9.5. Go-live checklist
    6. 9.6. Enterprise identity providers
    7. 9.7. SMART App Launch
    8. 9.8. Audit trail (IHE ATNA)
    9. 9.9. Version signing
       1. 9.9.1. Digest signing
       2. 9.9.2. PGP signing
11. 10. FerroEHR Viewer
    1. 10.1. Dashboard & queries
    2. 10.2. Templates & EHRs
    3. 10.3. Parties
    4. 10.4. Terminology
    5. 10.5. Server & audit log
    6. 10.6. Event subscriptions
    7. 10.7. Preferences & the theme
12. 11. Operations
    1. 11.1. Admin & messaging APIs
    2. 11.2. Usage report
    3. 11.3. Returning to the original state
    4. 11.4. Decommissioning
13. 12. Conformance
14. 13. Performance
15. 14. Benchmarks
16. 15. Rust crates
17. 16. Contributing
18. 17. Licensing & legal
    1. 17.1. Compliance overview
    2. 17.2. Shared responsibility
    3. 17.3. Retention, restriction and objection
    4. 17.4. Secondary use
    5. 17.5. Control matrix
    6. 17.6. Cyber Resilience Act
    7. 17.7. CRA information and instructions to the user
    8. 17.8. Complaints, incidents and vulnerabilities
    9. 17.9. Intended purpose
    10. 17.10. CRA risk assessment
    11. 17.11. Hazard log: the logging component
    12. 17.12. The logging component's intended performance
    13. 17.13. Claims review