Straight answers about what Panorama TMF QC does, what it needs from you, and what you get back. We'll start where the work starts — with your data.
A defined export of your Trial Master File — a point-in-time extract rather than a connection to your live system. In practice that means three things: a document metadata table describing the records in the file, the correlated audit-trail table covering their history, and the raw files those records point to. Most eTMF systems can produce this directly.
No. Panorama works entirely from the export. We never need credentials, logins, or a live connection to your eTMF, and we never write anything back to it. The assessment runs against a copy, so your production system is untouched.
No. We never have access to your source system, and we can never touch your source data. Panorama only reads the export you provide — it makes no edits, no status changes, and no writes of any kind. Nothing we do can alter your live TMF.
It's vendor-neutral. Because we work from a standard export rather than a system integration, Panorama is compatible with the major eTMF platforms — including Veeva Vault, Medidata, Oracle, ArisGlobal, and Phlexglobal — as well as in-house or hybrid repositories. If your system can produce a metadata table, an audit trail, and the underlying files, we can assess it.
All work runs in an isolated environment — your data is never sent to the cloud and never shared with third parties. Participant personal identifiers are never transcribed into findings; participant-level evidence is referenced by location, not reproduced. For blinded trials, treatment-revealing content is treated as restricted and cited by location only, never exposed in outputs.
The assessment is a snapshot as of the export's cutoff date. Everything in the findings reflects the state of the file at that moment, so the extract date is recorded and travels with the results. When the file moves on, a fresh export gives you a fresh assessment.
A file that can't be opened, parsed, or read is itself a result — an availability or legibility issue — not something quietly dropped. Every file is accounted for: the totals reconcile so that records read plus records that failed equals the full population. You see exactly what was covered and what couldn't be, with nothing hidden in the gap.
You don't — there's nothing to install. Our software is proprietary, and we sell the service, not the tool. You provide the export; we run the assessment and return the findings. Nothing is deployed into your environment.
Yes. Get in touch and we'll arrange a conversation to understand your operating constraints, then work out an arrangement that fits how your data is allowed to move. Restrictions like these are common — they're a starting point, not a blocker.
Yes. Contact us for a custom inspection set built around your SOPs, so the assessment reflects the standards your file is actually held to — not just generic expectations.
Tell us about your file and what you're trying to answer. We'll walk you through how a pilot would work.
Request a pilot