Four files for a lab director, molecular pathologist, lab operations lead, or diagnostics BD conversation. Sample layout, example payload, scoping agenda, compliance line.
Each file is linked from the diagnostic laboratories page. Nothing here is a named customer, a revenue figure, or a clinical claim.
01 · Report
A print-ready HTML layout of a fused multi-omic report under a partner laboratory’s brand. Open it and use the browser’s Print → Save as PDF. This repository has no server-side PDF generator. The file is structure only: it is not a patient result and not a diagnosis.
Open the sample report →02 · LIMS / API
A JSON example of a report-ready webhook shaped from the public endpoint names on the API page (/v1/reports/{id}, /v1/samples, webhooks). Illustrative schema for technical scoping. Not a production contract and not a credential.
Download the example JSON →03 · Scoping
The agenda for a demo and technical scoping call. It repeats timing language already published on the API page and the FAQ, and it states that those sentences are not a service-level agreement.
Open the scoping outline →04 · Compliance
ISO 9001:2015 certified · pursuing ISO 13485 · GDPR compliant. Decision-support, not diagnosis — every interpretation traced to evidence and signed off by a qualified human.
Open the compliance line →ISO 9001:2015 certified · pursuing ISO 13485 · GDPR compliant. Every interpretation is traced to evidence and signed off by a qualified human. The sample report is a branding and structure specimen. It must not be forwarded as a patient result.
The same line is in the plain-text file. The medical disclaimer is the longer statement.
