Docs · Files

Manifest format & sample files.

The order wizard’s second step says, in the product: “Upload the order manifest exported from your LIS, then review the parsed accessions.” Here is the shape that file takes — fourteen columns, one row per specimen — plus two fictional files so you can run the whole loop before your first real specimens.

Fourteen columns, one row per specimen

The manifest is the CSV your LIS already exports. These are the fourteen columns the parser reads, with the demo lab’s own seed row as the example.

#ColumnWhat it holdsExample
1clientThe ordering client the accession reports back toElite Lab
2accessionYour accession identifier for the specimenE2305080189
3ref accessionThe ordering side’s own reference for the same specimenIP234234
4patient first nameThe patient’s given nameMichael
5patient middle nameBlank when there is noneR
6patient last nameThe patient’s family nameAnderson
7date of birthDate of birth2000-08-20
8genderAs recorded on the orderMale
9testThe panel to run, by its short nameUTI
10specimen typeWhat was collectedUrine
11collection dateWhen the specimen was collected2023-05-08
12received dateWhen it arrived at your lab2023-05-09
13physicianThe ordering physicianDr. Rao
14facilityThe ordering facilityElite Lab

After parsing you review the accessions before anything is created — and a field that parsed wrong is a bulk edit, not a retype: select the rows and change client, collection date, received date, test or specimen type in one pass.

Header rows, and files that arrive in fives

Skip rows tells the parser how many rows to ignore before the data begins — the default is 1, the heading row, and every result file carries its own per-⁠file setting. Drop several manifest files on one order and they merge instead of fighting. The software adapts to the file, not the reverse.

Two sample files, fictional end to end

No patient in either file exists, so you can take an order from upload to released report without a single real specimen on our side — and without PHI. The manifest matches the fourteen columns above; the result file matches it accession for accession.

sample-manifest.csv

An order manifest in the fourteen-column shape — a handful of fictional accessions.

sample-results.csv

The matching instrument result file, ready to attach on the Upload Result step.

Asked before, answered here

Can I upload more than one manifest on an order?
Yes. Multi-file import parses each file and merges the accessions onto the same order, and the review table shows the combined list before anything is created.
My export has a preamble above the heading row.
Raise Skip rows until the first data row is the first row read. Result files carry the same setting, per file.
Which result files can I attach?
The result-file type is chosen per file — BioRad-Cfx exports among them — and the instrument list covers the QuantStudio and CFX lines. Each target is matched on Name in Result File, character for character against what the instrument wrote.

Raise the order.

The wizard’s own promise holds the whole way: “You can Save as draft at any step and finish later.” Start with the sample files, and the first real manifest will hold no surprises.

A file that won’t parse: support@pcrlabpro.com.