Skip to documentation content

Documentation · Process

PRISMA flow

Write the counts in the order the review moved through them. Each row is a step in the flow, a side box says what was dropped there, and the four phase bands are read off the rows themselves.

Open PRISMA flow

When to use it

Report how a systematic review's records moved from identification through screening and eligibility to the studies it included, following the PRISMA 2020 statement.

Each row is a step in the flow and each side box says what was dropped there. Keep the counts consistent, so what leaves one row is what the next row begins with.

Working example

Copy this complete example into the Source tab, then press Generate. Change its labels or values to make your first version.

Tingraph source
prisma "PRISMA 2020 flow diagram" {
  band "Identification"
  row "Records identified from" 1423 {
    "Databases" 1200
    "Registers" 223
  }
  side "Records removed before screening" 468 {
    "Duplicate records removed" 300
    "Records marked as ineligible by automation tools" 100
    "Records removed for other reasons" 68
  }

  band "Screening"
  row "Records screened" 955
  side "Records excluded" 812
  row "Reports sought for retrieval" 143
  side "Reports not retrieved" 20

  band "Eligibility"
  row "Reports assessed for eligibility" 123
  side "Reports excluded" 110 {
    "Reason 1" 50
    "Reason 2" 35
    "Reason 3" 25
  }

  band "Included"
  row "Studies included in review" 13 {
    "Reports of included studies" 16
  }
}

Syntax reference

The same reference used by the editor and AI briefing. Syntax is notation-specific; use the keywords listed here.

Diagram

SyntaxMeaning
prisma "Title" {open a PRISMA 2020 flow diagram
band "Identification"name the phase the rows after it stand in

The flow

SyntaxMeaning
row "Records screened" 955a step and its total
row "Records identified from" 1423 {a step with lines under it
"Databases" 1200one line and its own count
side "Records excluded" 812 {what left the flow at the row above
"Duplicate records removed" 300one reason and its count

Look

SyntaxMeaning
style formalformal, banded, bold
bands onthe four phase bands down the left
text 12caption size
size 820 660how big the flow is drawn
# commentline comment (also //)

Language rules

  • The file is one prisma "Title" { ... } block. Nothing may sit outside it.
  • The title is the name of the flow, written above it.
  • A band names the phase every row after it stands in, until the next band. Consecutive rows naming the same band share one strip, so Screening may cover two rows.
  • A step is row "Caption" 955, optionally followed by a { ... } block of lines. Each line is "Caption" 1200.
  • A side box follows the row it belongs to and says what left the flow there. It takes the same caption, total and block.
  • Counts are written plainly and drawn as (n = 955). Leave the number out to draw the caption on its own.
  • Settings are written as name value, in any order.
  • Do not invent settings. Every one the language has is listed above.

Edit on the canvas

  • Select any caption to rename it, or use the controls beside a box to add or remove a line of the flow.
  • Edit every row, count, exclusion reason and phase band in the PRISMA panel.

Generate replaces the drawing from source. Save before generating again if you want to preserve manual finishing touches.

Read Saving & exporting

Write it with an assistant

Tingraph AI already knows this notation. For another assistant, copy the tutorial below, describe your diagram under MY DIAGRAM, then paste the returned source into the editor. This prompt includes every syntax row, rule and working example above.

Read the complete prompt
You are writing Tingraph source. Tingraph is a small text language that draws a PRISMA 2020 flow diagram. Answer with Tingraph source only.

SYNTAX
Diagram
  prisma "Title" {            open a PRISMA 2020 flow diagram
  band "Identification"       name the phase the rows after it stand in

The flow
  row "Records screened" 955  a step and its total
  row "Records identified from" 1423 {  a step with lines under it
  "Databases" 1200            one line and its own count
  side "Records excluded" 812 {  what left the flow at the row above
  "Duplicate records removed" 300  one reason and its count

Look
  style formal                formal, banded, bold
  bands on                    the four phase bands down the left
  text 12                     caption size
  size 820 660                how big the flow is drawn
  # comment                   line comment (also //)

RULES
- The file is one `prisma "Title" { ... }` block. Nothing may sit outside it.
- The title is the name of the flow, written above it.
- A `band` names the phase every row after it stands in, until the next `band`. Consecutive rows naming the same band share one strip, so Screening may cover two rows.
- A step is `row "Caption" 955`, optionally followed by a `{ ... }` block of lines. Each line is `"Caption" 1200`.
- A `side` box follows the row it belongs to and says what left the flow there. It takes the same caption, total and block.
- Counts are written plainly and drawn as `(n = 955)`. Leave the number out to draw the caption on its own.
- Settings are written as `name value`, in any order.
- Do not invent settings. Every one the language has is listed above.

WORKED EXAMPLE
prisma "PRISMA 2020 flow diagram" {
  band "Identification"
  row "Records identified from" 1423 {
    "Databases" 1200
    "Registers" 223
  }
  side "Records removed before screening" 468 {
    "Duplicate records removed" 300
    "Records marked as ineligible by automation tools" 100
    "Records removed for other reasons" 68
  }

  band "Screening"
  row "Records screened" 955
  side "Records excluded" 812
  row "Reports sought for retrieval" 143
  side "Reports not retrieved" 20

  band "Eligibility"
  row "Reports assessed for eligibility" 123
  side "Reports excluded" 110 {
    "Reason 1" 50
    "Reason 2" 35
    "Reason 3" 25
  }

  band "Included"
  row "Studies included in review" 13 {
    "Reports of included studies" 16
  }
}

OUTPUT
- Reply with one fenced code block and nothing else.
- The block starts with `prisma "…" {` and ends with `}`.
- Do not invent keywords: use only the ones listed above.
- Keep labels short enough to read inside a box, and keep every ID unique.

MY DIAGRAM
Describe what you want here, then send this message.
How AI requests, attachments and privacy work

Something unclear? Contact support or read the Privacy Policy.