External data operations
External data,
ready for your study.
Move vendor deliveries from specification to reviewed study data. Configure the transfer, run quality checks, reconcile records, and keep every exception connected to its source.
Discuss your workflowA configuration you can inspect.
Explore a field mapping and its governing specification.
PK field mapping
| Source field | Output field | Mapping rule |
|---|---|---|
| USUBJID | Study + participant | |
| SAMPLEID | Direct mapping | |
| collection_timepoint | Controlled timepoint | |
| PCORRES | Preserve source value |
Mappings connect to the specification. Configuration changes remain reviewable before execution.
Transfer design
Start with the specification. Keep the mapping in view.
Bring vendor specifications, expected fields, and study requirements into one review. Proposed mappings stay connected to the source that supports them.
Inspect a field, follow its citation, and review the proposed transformation before it becomes part of a versioned configuration.
Sample IDPK-015Collection timepoint2 hResult14.7 ng/mLQuality & reconciliation
Find the discrepancy. See exactly where it came from.
Evaluate incoming deliveries against configured checks and study references. An exception brings the conflicting values, the applicable rule, and the supporting records into the same workspace.
A matched sample can still carry inconsistent collection timepoints. Compare the vendor value with the registry record, down to the cited workbook cell.
Review the discrepancy before this delivery is released.
Review & release
Move the delivery forward with a record of the decision.
Resolve findings with a documented rationale, then review the delivery against its release policy. Keep configuration changes, exception decisions, and release authorization distinct.
Unresolved blockers hold release. The reviewed output retains its source lineage and the decisions that made it ready for the next step.
Resolve the timepoint mismatch for PK-015 with the vendor.
Timepoint discrepancy · source records linkedA reviewer must resolve the blocking exception.
The Panoptive foundation
Connected to the rest of your study.
Transfer agreements, vendor files, study references, and earlier decisions share one data foundation. Each delivery has the context needed to interpret it and a retained record of its execution.
Explore the shared foundationAccountable execution
Execution your team can govern.
Agents prepare mappings and execute configured checks. Your team reviews consequential changes, resolves exceptions, and defines the policy for making reviewed outputs available.
Security and data protectionVersioned configuration
Keep the specification and workflow version used for each delivery.
Source-level evidence
Follow a result back to the original file, field, and supporting record.
Controlled release
Apply review requirements and retain the rationale behind each decision.
See it with
your workflow.
Talk with our team about the sources, decisions, and reviews behind your study.
Talk to our team