Skip to content

anarchie init

Scaffold a new anarchie deployment - the directory tree that holds every EHR, template, and derived index.

Usage

anarchie init [path] [--system-id <id>] [--minimal]
Argument / option Default Description
[path] . Directory to create the deployment in.
--system-id <id> anarchie.local The creating-system identity stamped into every version_uid.
--minimal off Create an empty CDR without the bundled starter templates.

Example

$ anarchie init --system-id anarchie.example.org
Initialised anarchie deployment at .
  system_id: anarchie.example.org
  starter templates (8):
    - vital_signs_encounter.v1
    - problem_list.v1
    - adverse_reaction_list.v1
    - medication_list.v1
    - laboratory_result_report.v1
    - immunisation_list.v1
    - procedure_list.v1
    - encounter_note.v1

By default init seeds the deployment with 8 bundled starter Operational Templates, so the CDR can store clinical data immediately. Pass --minimal for an empty CDR with no templates registered (it prints starter templates: none (--minimal)). The Initialised ... at line echoes the path argument verbatim - . when no path is given - not an absolute path.

What it creates

Path What it is
anarchie.toml Deployment config: system_id, RM version, index settings.
ehrs/ One git repository per patient record.
templates/ Registered Operational Templates and their index.
index/ The derived query index. Disposable and .gitignored.

The index/ directory is .gitignored because it is a derived view, regenerable from the canonical files, and never belongs in version control.

See also