Customer clarity
Can the buyer understand what the result means and what to do next?
Example output structures
Show the value of pathogen genomics in a format people can act on.
These examples show how pathogen-genomics analysis can translate into executive, technical, and operational artifacts for commercial lab customers.
Output philosophy
Different readers need different levels of evidence.
Commercial pathogen-genomics services often fail when every audience receives the same technical output. A strong service line separates executive action, scientific review, operational evidence, and customer education while keeping them traceable to the same workflow.
Example 01
Executive brief
A concise customer-facing structure for leaders who need the finding, context, confidence boundaries, and recommended next action.
Finding categoryRelatedness signal identified among selected isolates; further epidemiologic context required before action.
Operational contextOutput is intended to support infection prevention discussion, not replace case investigation or clinical review.
Recommended next stepReview sample metadata, collection dates, facility context, and technical appendix before escalation.
Example 02
Technical interpretation summary
A scientific review structure that keeps QC, workflow provenance, organism-specific notes, and interpretation boundaries close to the result.
| Section | Purpose | Example contents |
|---|---|---|
| Run and sample QC | Document whether inputs are fit for interpretation. | Coverage, read quality, contamination notes, pass or warning criteria. |
| Workflow provenance | Make the analysis reproducible and reviewable. | Workflow name, version, parameters, reference data, execution environment. |
| Finding summary | Separate result categories from explanatory context. | Lineage, taxon call, AMR evidence, relatedness note, or cluster context depending on scope. |
| Limitations | Protect against overinterpretation. | Sampling context, resolution limits, missing metadata, or required confirmatory review. |
Example 03
Workflow and evidence map
A map that operations teams can use to understand what happens at every step and where review is required.
A
Input acceptedSequence files, metadata, sample identifiers, and accession context are checked for completeness.
B
Workflow executedControlled workflow and parameters generate QC, taxon-specific findings, and evidence artifacts.
C
Scientific reviewQC warnings, exception conditions, relatedness signals, and interpretation boundaries are reviewed.
D
Report packagedExecutive brief, technical appendix, and evidence record are assembled for the intended audience.
Use in a pilot
What these sample outputs help prove.
Scientific review
Can the lab defend how the result was generated and reviewed?
Operational fit
Can the process be supported by real staff, turnaround, and handoff expectations?
Commercial story
Can sales and customer success explain the service without overselling the science?
Output design
Turn a pilot into something stakeholders can evaluate.
Theiagen can help create the output package that makes a commercial pathogen-genomics service concrete for customers, scientific reviewers, and operations teams.
Request sample-output support
Use this when your team needs an example report, technical appendix, or evidence map for a service-line decision.