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 accessed from the session detail page via the Report button, which opens the report builder at /reports/<session-id>.
The PDF report
The PDF is landscape, designed to read on a single screen or print without scaling. Header band carries your clinic logo alongside the ForceIQ mark. Footer carries the clinician's name, the assessment date, and a small "Generated by ForceIQ" line. Patient identifier is the patient code by default; if PHI mode is enabled for the clinic and the patient has a name on file, the name appears alongside the code.
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:
- Single assessment. One joint and action, both sides if it was bilateral. The most common report.
- Full visit. Every joint and action tested on that date, in one combined PDF. Useful when the patient sees a return-to-sport gatekeeper who wants the full picture in one document.
Single-assessment reports keep the page count low. Full-visit reports add one block per joint-action with a continuation page if needed.
Section toggles
Every section is on by default and 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.
| Section | What it contains |
|---|---|
| Bilateral Metrics | The full metric tile grid: peak, RTD Early, RTD Late, nRMSE, CV, Yank. One column per side, plus the LSI percentage when both sides were tested |
| LSI Summary | The radar plot and the per-metric breakdown table. Only available when the assessment has bilateral data |
| Torque-Time Curve | The annotated chart capture: onset marker, RTD windows, plateau region, peak indicator. Rendered at print resolution |
| Dashboard Overview | The longitudinal view: radar at current visit, metric trend grid across the patient's history, any custom-metric trends |
| Clinical Outcomes Table | Any custom metrics entered for this patient: hop tests, surveys, range of motion. Only available when the patient has at least one custom entry |
| Longitudinal Progress | A summary timeline of every prior session for this patient, with values and percent change. Only available when the patient has more than one visit |
| Clinical Notes | The free-text clinical notes attached to the session. PHI under most clinic configurations |
Default to leaving every available section on for a return-to-sport or discharge summary. Trim to just Bilateral Metrics and Torque-Time Curve when generating a quick referring-provider update where the audience wants the headline and the curve.
Display options
The same unit controls that govern the dashboard view also govern the report:
- Force or torque (Nm or N), with the patient's unit preference applied
- Mass normalization (/kg), available only when bodyweight is entered on the patient
These are baked into the PDF at generation time. Re-exporting with a different display setting produces a new PDF.
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>_<date>_<joint>_<action>.pdf for single-assessment reports and ForceIQ_<patient-code>_<date>_visit.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 to patient option (right side of the report builder) sends a time-limited link rather than an attachment. The patient receives an email containing a link that expires after 48 hours; the PDF itself stays on the platform's storage, not in the patient's inbox. The email goes to the address on the patient profile. If the patient has no email on file, the button is disabled until you add one.
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_t1,peak_force_t2,peak_force_t3(one column per trial)peak_force_mean,peak_force_sd(summary across trials)- Same pattern for
peak_torque,rtd_early,rtd_late,nrmse,cv,yank,contraction_duration
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
| Need | Reach for |
|---|---|
| Patient chart entry | PDF, single assessment, all sections on |
| Return-to-sport summary for referring provider | PDF, full visit, all sections on |
| Quick "here's where they are" update | PDF, single assessment, Bilateral Metrics + Torque-Time Curve only |
| Plotting in a spreadsheet for one patient | CSV long format |
| Per-visit comparison spreadsheet | CSV wide format |
| Research export or external pipeline | CSV long format, then transform downstream |
| Sending the patient their own summary | PDF, then Email to patient (requires patient email and PHI mode) |
What to do next
- Generate a PDF on one patient before you need one for real. It surfaces the unit and section preferences you'll want to set defaults on, and it shows you whether your clinic logo renders the way you expected.
- Check the section toggles before clicking Generate. 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.