Reports & templates
The report is the product. It prints on your letterhead.
Templates authored in HTML and CSS with a live preview, merge tokens that fill themselves in at render time, per-test and per-client assignment with one enforced default, and a branded PDF rendered by the backend for every released accession. When a correction happens, version 2 carries the reason, the who, the when, and a supersedes line on the face of the document.
A rename that never made it onto the next report.
In March the lab renames an assay; in April a report goes out under the old name, because the name lived inside a template file someone had to remember to edit. Same lab, different week: a corrected report replaces a wrong one, and the only record of what changed is an email thread. Neither failure is scientific. Both are what happens when the report is treated as an output instead of a record.
Here, the document is a record with rules.
Templates are assigned, not attached: a template naming this test wins, otherwise the one default catches it — and exactly one default is enforced, so no accession can ever print ambiguous. The PDF Name on each target resolves at print time, so a rename follows through onto reports you haven’t run yet. And a correction produces a version, never an overwrite.
HTML and CSS in. A branded PDF out.
- A live preview while you author.
- HTML and CSS on one side, the rendered page on the other — a sandboxed preview of the same accession you’ll release.
- Merge tokens, click to insert.
- Client, test, lab and report date fill themselves in at render time.
- Assignment with a resolution order.
- Per test, per client, and the one enforced default. Every accession shows exactly which template it will print with, before you release it.
- Normal and Premium types.
- A template catalogue you can browse and take copies from; Premium designs carry a price.
- Rendered by the backend.
- The released PDF is produced server-side on your letterhead — your logo, your director, your declaration — the same document every time, on every machine.
A correction makes version 2, and version 2 says so.
Upload the corrected result file and the report becomes v2: a reason you have to type, who amended it and when, and “supersedes report of 14 March” printed on the face of the document. One amendment per report, with an audit entry to match — a v3 negotiated over email can’t happen, because there is nowhere for it to happen.
It never reassigns a sample.
The order, run and specimen binding stays read-only under amendment, and the server rejects a corrected file that tries to move it. A correction corrects a measurement; if the sample itself was wrong, that isn’t an amendment — it’s a different report, and the software will not let the second problem borrow the first one’s paper trail.
We render it. You sign it.
The letterhead is yours, the director’s name is yours, the declaration text is yours — the release gate won’t let a report out without them. Our part is the rendering and the record-keeping, downstream of your LIS and your instrument, where the report actually leaves.
Your letterhead by this afternoon.
Upload a logo, set your declaration, pick or author a template, and release your first report free — a branded PDF with your director’s name on it, before you decide anything.