Skip to content

Report Management

Inspect reports from the command line. Editing and signing reports is a web-UI workflow because the Approve-and-Sign modal is part of the audit chain; the CLI provides read access and scripting helpers.

Prerequisites

  • CLI installed and authenticated.
  • A selected project.

Listing reports on an order

iflow reports list --order ORDER_ID

Output includes each report's id, status (draft, pending_review, approved, signed, amended), template_type (clinical, hereditary, somatic), and timestamps.

Getting a report

iflow reports get REPORT_ID

Sample output:

Report: abc123-...
  Status: signed
  Template: somatic
  Order: ORD-2026-0042
  Signed by: jane.smith@lab.example
  Signed at: 2026-02-14T17:12:04Z
  Signed PDF: orders/ord-2026-0042/signed-report.pdf

Downloading the signed PDF

The signed PDF lives at orders/{slug}/signed-report.pdf in the project bucket. Download it with the files CLI:

iflow files download orders/ord-2026-0042/signed-report.pdf ./signed.pdf

See File Operations.

Listing variants on a report

iflow reports variants REPORT_ID

Listing comments

iflow reports comments REPORT_ID

Filter by comment type:

iflow reports comments REPORT_ID --type review
iflow reports comments REPORT_ID --type signoff

Listing snapshots

iflow reports snapshots REPORT_ID

Signing is UI-only

Approve-and-Sign runs through the web UI because the confirmation modal is part of the audit chain. There is no CLI equivalent for committing a signed report.

What the CLI does not do

  • Approve-and-Sign — the sign-off confirmation modal is part of the audit chain and is driven only from the web UI.
  • Render the final PDF — again, ties into sign-off; only the web UI is authorised to commit the atomic sign-off transaction.
  • Create an amendment — the amendment workflow lives in the web UI.

Read-only API access

curl "https://report.<env-domain>/api/v1/reports?order_id=ORDER_ID" \
  -H "Authorization: Bearer $IFLOW_PAT" \
  -H "X-Project-ID: $PROJECT_ID"