Metawebservice is ME-TA's validated statistical computing environment for clinical trial biometrics. This guide takes you from first sign-in to released deliverables. For what the platform is and why, see the platform overview.
What you need depends on how you work with the platform.
The web application runs at metawebservice.com in a current browser. Study setup, file upload and download, review, and team management all happen here. You install nothing.
SAS programs execute locally, not on the server. To run them you need a Windows PC with a local SAS 9.4 installation and the ME-TA SCE desktop client, which ME-TA deploys through Microsoft Intune.
The client syncs study files between the server and your PC and runs SAS against your local installation.
Access is by invitation. If your organization does not yet use Metawebservice, contact ME-TA at contact@me-ta.dk (see Support).
Authentication runs on AWS Cognito with two sign-in methods.
Go to https://metawebservice.com/.
Enter your email address and choose Send verification code. An 8-digit code is sent to your inbox.
Enter the 8-digit code and you are signed in. Each sign-in uses a fresh code; there is no password to manage.
If your organization is set up for single sign-on, a Sign in with Microsoft option appears alongside the email form. Choose it and sign in with your Microsoft work account instead of a code.
Work on Metawebservice is organized in studies.
Day-to-day work follows one loop. The platform uses three file classes: inputs (the source files a study consumes), deliverables (what the study produces), and AI knowledge (reviewed reference material for AI-assisted programming).
You upload raw data, specifications, and other source files to the study's upload area in the browser. Re-uploading a file under the same name does not discard anything; every prior version is retained on the server.
SAS programs are managed as SAS jobs in the study, with execution order and dependencies tracked by the platform. The ME-TA SCE client syncs programs and data down to your PC, and you run SAS 9.4 locally.
The client detects local changes and uploads them, verifies file integrity with MD5 checksums, and uploads execution logs for monitoring and log analysis. Everything a SAS job produces is stored as a deliverable.
You review outputs in the browser, with per-file preview. Every version of every file is retained on the server, so earlier states stay traceable.
When a deliverable is final, it is released. Released files are listed in the study's released area, separate from work in progress.
Files you provide as AI knowledge (the study's context area) each carry a review status. You preview a file first, then approve it. Until a file is approved it cannot be downloaded from that area or used in AI-assisted work.
The audit trail is not an add-on; it is how the platform stores work.
Every version of every file is retained, with timestamps and MD5 checksums, so which data and which SAS program produced which output remains traceable.
Access is logged: who had access to what, and when. Application-level audit logging is backed by AWS CloudTrail at the infrastructure level, with immutable, tamper-evident records.
The platform is designed for 21 CFR Part 11, EU Annex 11, ICH E6(R3), ICH E9, and GDPR alignment, backed by ME-TA's 22-policy version-controlled Quality Management System at policy.me-ta.dk.
ME-TA welcomes vendor audits, and a vendor-qualification package is available on request. All data is stored in AWS eu-west-1 (Ireland), encrypted with AES-256 at rest and TLS 1.2+ in transit.
Yes, to run programs. SAS executes locally on your Windows PC using your own SAS 9.4 installation. The platform stores, versions, and syncs study files; it does not execute SAS server-side.
Yes, for everything except SAS execution. Study setup, uploading inputs, reviewing outputs, and team management run in the web application. The ME-TA SCE desktop client is needed only to run SAS on your PC.
In AWS eu-west-1 (Ireland). Data is encrypted with AES-256 at rest and TLS 1.2+ in transit.
Yes. The platform is a .NET Core API with 159 REST endpoints, documented with OpenAPI 3.0. Swagger UI is served at the API root, api.metawebservice.com.
Access is by invitation. If your organization does not yet use Metawebservice, contact ME-TA at contact@me-ta.dk.