Help
i2b reads a database somebody already has — a shop, a site, a forum — works out what is in it, and carries it into a new one. These pages describe the product that is running now. Where a page states something a screen also states, it reads the same source the screen reads, so the two cannot drift apart.
Getting startedOpen a database, read what it holds, and see what a migration would cost you.EnginesWhich shop and site engines i2b maps, and which of them have been checked against the vendor’s own published schema.Correcting a migrationThe six things an operator does by hand: a wrong link, a table, a value inside a cell, a loss, a row, and the order of the work.LicencesWhat each plan permits, and which screens stop without one.Your dataWhat leaves your database, what we keep, and for how long.Agents (MCP)How an agent reads a workspace, what it may suggest, and what it can never decide.QuestionsThe ones that come up before anybody has tried it.
What this does not do
These pages do not describe work in progress. Anything not deployed is not here, which means the help centre is sometimes behind what has been built and never ahead of it.
They are not a manual for your own database either. They say what i2b does with the engines it knows; what your particular installation holds is something only reading it can answer, and the workbench is where that happens.