Exporting reports and downloading data

Two ways to get data out of ForceIQ. A clinic-branded PDF report for the patient chart or a follow-up visit, and CSV downloads (wide or long format) for spreadsheet analysis. This walks through what each section of the PDF contains, the units it prints in, how to scope a report to a single assessment or a full visit, and when to reach for each CSV format.

Updated October 15, 2026

ForceIQ generates two kinds of exports. The PDF report is the clinic-branded document you put in the patient chart or send to the referring provider. The CSV exports are the raw numeric tables for spreadsheet analysis, research, or pulling into another system. They're complementary; the PDF is for humans and the CSV is for whatever pipeline you've built around the data.

Both are reached from the report builder. Open it with Export Report on the dashboard or Export on a session's detail page. Either way it starts on the full visit.

The PDF report

The PDF is landscape, designed to read on a single screen or print without scaling. The header carries your clinic logo and name (the ForceIQ name when no logo is uploaded), the patient code, the date and the involved side. The footer carries the clinician's name, the clinic, the page number and a small "Generated by ForceIQ" line. The patient is identified by their patient code. The PDF never prints the patient's name, even with PHI mode on.

Each page holds two rows. In a single-assessment report the results are one page: the best trial and the metric table, then the radar and trends, with short notes beside them. The progress table, clinical outcomes, longer notes and the interpretation notes follow on an Additional Details page. In a full-visit report each test gets its own page in the same layout, followed by a notes page, the Athletic Shoulder figure and the clinical outcomes. A full-visit report has no progress table or outcome trend charts; export a single assessment for those.

Scope: one assessment or the whole visit

A visit can contain multiple assessments (knee extension, hip abduction, ankle dorsiflexion, all run on the same day). The scope toggle at the top of the report builder lets you pick:

  • Full visit. Every joint and action tested on that date, in one combined PDF. This is the default, since a visit is what a note is written about, and it is what a return-to-sport gatekeeper wants in one document.
  • Single assessment. One joint and action, both sides if it was bilateral.

A full-visit report is one page per test, plus the pages that follow.

Section toggles

Every section except ASH per-position detail and Interpretation notes is on by default, and any can be toggled off if it isn't useful for the audience. Sections that have no data for the selected scope are disabled in the toggle list so you know why a section isn't producing output.

SectionWhat it contains
Bilateral MetricsThe six metrics, each named the way the app names it (Strength, Explosiveness, Build-up, Drift from peak, Steadiness, Smoothness) with the technical name and unit beside it. The mean of the trials on each side, plus the LSI when both sides were tested
LSI SummaryThe headline LSI above the table, the same number the patient's dashboard leads with (Strength LSI with Speed and Control beneath it in the simplified view, the weighted LSI and its lowest metric in the expanded view), and the symmetry radar when Dashboard Overview is also on. The table's LSI column prints either way. Only available when the assessment has bilateral data
Torque-Time CurveThe best trial on each side, overlaid from onset, with the plateau shaded, in the report's unit
Dashboard OverviewThe longitudinal view: the symmetry radar at this visit (when LSI Summary is on), the metric trends across the patient's history, and, in a single-assessment report, trends for any clinical outcomes
Clinical Outcomes TableAny custom metrics entered for this patient: hop tests, surveys, range of motion. Only available when the patient has at least one custom entry
Longitudinal ProgressEvery assessment of the same test (same joint, action and position) for this patient: the date, the patient's headline LSI (Strength LSI or the weighted LSI, as their view leads with), and the mean peak on each side in the report's unit. Single-assessment reports only. Only available when the test has been done more than once
Clinical NotesThe free-text clinical notes attached to the session. PHI under most clinic configurations
ASH per-position detailFor an Athletic Shoulder test, the full metric panel for each of the I, Y and T positions. Off by default: the ASH figure already covers all three positions, and the speed and control rows are not what the test is read on
Interpretation notesThe data-quality and setup notes session detail shows beside the numbers: sample rate and how precise the rate of force development is at it, a possible tare or pretension problem, limb weight at the test angle, and how the torque conversion was estimated. Off by default, because the report usually goes to a patient or a physician. When on, they print on a page after the results (Additional Details in a single-assessment report, the notes page in a full visit). The numbers themselves print either way

Default to leaving every available section on for a return-to-sport or discharge summary. Trim to Bilateral Metrics, LSI Summary and Torque-Time Curve when generating a quick referring-provider update where the audience wants the headline and the curve.

Units

The report opens in your unit preferences, the same ones the dashboard and session detail use, so it starts in the units you were just looking at. Switching force or torque, or the unit, on the dashboard or a session page saves it as your preference. Changes on the report page apply to that export only.

  • Torque or force, in the unit you choose (Nm, kgm or ft-lbs for torque; N, kg or lbs for force). A test prints in torque only if it has a torque conversion, which needs a supported joint and action plus the patient's height. A force-only test such as grip in a full-visit report prints in force rather than zeros under a torque unit.
  • Per bodyweight, per kilogram (or per pound with lbs and ft-lbs). It is available only when bodyweight is entered on the patient, and it opens in whatever state the page you exported from was showing.
  • Also show a second unit, printed in small type beside Strength, Explosiveness and Build-up, for example "160.0 · 400.0 N". It opens as plain force when the report is in torque or per bodyweight (the number a referrer can check against a device reading), and as force per bodyweight when the report is in plain force and bodyweight is on file. Pick None to leave it out. A second unit that would print the same as the first is left out.

Within each test, the metric table, the trend charts and the progress table use the same unit, so the numbers always match the units printed beside them. The LSI follows the quantity you choose. The best-trial curve uses the same unit too, except when the plotted trial has no torque conversion, in which case it is drawn in force and its axis says so.

Trend charts

Show each trial is on by default: each trial is a dot, with the range behind the visit's mean, as on the dashboard. Turn it off for the mean alone. These choices are baked into the PDF at generation time. Re-exporting with a different setting produces a new PDF.

Copying a summary into your notes

Copy summary puts a plain-text summary of every test in the visit on your clipboard, ready to paste into an EMR. Each test gets a small table: the six metrics on each side, their LSI, and the change since the previous assessment of the same test. The numbers match the dashboard: peak comes from the maximal efforts, and the Speed and Control metrics come from RTD trials and submaximal holds when both sides have them. Each test is printed in its own unit, force or torque, and a change is left blank when the previous visit measured that metric a different way (for example ballistic trials this visit and maximal efforts last time). The patient's name is included only when your clinic has PHI enabled; the patient code always is.

What ends up in the file

The PDF is generated entirely in the browser and downloaded directly. Nothing is uploaded to a third-party service for rendering. File name is auto-suggested as ForceIQ_<patient-code>_<joint>_<action>.pdf for single-assessment reports and ForceIQ_<patient-code>_visit_<date>.pdf for full-visit reports. Patient code only; no patient name in the filename even when PHI mode is on.

Emailing the report to the patient

The Email Report to Patient panel sends a time-limited link rather than an attachment. The email goes to the address on the patient profile, and Send Report stays disabled until you confirm the patient agreed to receive the report by email. The link expires after 48 hours, and the PDF stays in the platform's storage rather than in the patient's inbox. The emailed copy opens as ForceIQ-report.pdf rather than the suggested download name, so the link itself carries no patient code or date. ForceIQ only sends a report built for the session's own patient: one built while a different patient was selected is not sent, and you can open it from that patient's session and send it again.

This delivery path requires the patient email field on the patient profile to be set, and the clinic's PHI mode to be enabled. Patient email is a PHI field and is only collected when the clinic explicitly turns PHI on.

CSV exports

The CSV downloads sit on the same page as the PDF builder, under their own button row. Two formats, both downloaded to your machine immediately.

Wide format

One row per assessment date per limb. Each metric gets its own set of columns:

  • peak_force_N_t1, peak_force_N_t2, peak_force_N_t3 (one column per trial)
  • peak_force_N_mean, peak_force_N_sd (summary across trials)
  • Same pattern for peak_torque_Nm, rtd_early_force_N_s, rtd_early_torque_Nm_s, rtd_late_force_N_s, rtd_late_torque_Nm_s, nrmse_pct, cv_pct, yank_s1 and contraction_duration_ms, with each column named for its unit

Excluded trials are dropped before the mean and SD are computed, so the summary columns reflect the patient's actual data, not the trial count. The trial-level columns (_t1, _t2, _t3) preserve exactly what was recorded.

Wide format is what you want for per-visit comparisons, per-patient trial-by-trial review, or for pulling into a spreadsheet where each row is a meaningful unit (a visit) and each column is a measure.

Long format

One row per metric. Columns are: patient code, date, limb, metric name, value, units, trial index.

Long format is what you want for plotting, pivot tables, or importing into a research database. The single-row-per-observation shape is what most analysis tools expect.

Always SI units

Both CSV formats export in SI base units (N for force, Nm for torque, kg for mass), regardless of the unit preference set in the app. Scientific data should be in standard units; conversion belongs in whatever tool consumes the file. If your downstream pipeline needs lbs or ft-lbs, convert in the spreadsheet.

What's not in the CSV

  • Custom metrics are included as additional columns (wide) or rows (long) when the patient has any entered.
  • Patient identifiers are limited to the patient code. PHI fields (name, DOB, email, injury text) are never written to a CSV, even when PHI mode is enabled. CSV exports are designed to leave the system safely.

When to use which

NeedReach for
Patient chart entryPDF, single assessment, all sections on
Return-to-sport summary for referring providerPDF, full visit, all sections on
Quick "here's where they are" updatePDF, single assessment, Bilateral Metrics + LSI Summary + Torque-Time Curve only
Plotting in a spreadsheet for one patientCSV long format
Per-visit comparison spreadsheetCSV wide format
Research export or external pipelineCSV long format, then transform downstream
Sending the patient their own summaryPDF, then Email to patient (requires patient email and PHI mode)

What to do next

  • Export a PDF on one patient before you need one for real. It shows you which sections and units suit your usual reader, and whether your clinic logo renders the way you expected. Section and unit choices on the report page apply to that export only; the units open on your preferences each time.
  • Check the section toggles before clicking PDF Report. Sections with no data are disabled in the list, which is the fastest way to know that, say, a longitudinal progress page won't render because the patient only has one visit on file.
  • For research workflows, set up the long-format export as your standard. It's friendlier to every analysis tool, and it doesn't require knowing the metric column layout in advance.
Was this helpful?