Technical partner resources
Integration notes.
Workspace conventions and support references for the clinical operations platform.
Platform revision 2026.11 Updated 4 November 2026
Regional workspaces
Use the regional directory to locate a team's workspace. The us-clinical-platform team owns sponsor-level catalogue changes; regional teams own their source exports.
Cloud integration uses temporary workload credentials. Credential generations are supplied by the runtime and must not be embedded in source control or copied into long-lived configuration.
Operations tools
Study search accepts a programme or document reference. Document preview reads the supplied source and returns a bounded response. The legacy report renderer accepts a study reference and output format.
Support manifest
During an integration investigation, collect the current runtime manifest. It contains the workspace region, catalogue location and workload credential-provider path. Treat returned runtime credentials separately from the diagnostic metadata.
Data conventions
Release packages use a stable release_id, study reference, status and destination. File-level handoffs include a source region and version. Never place patient identifiers or clinical records in support requests.