How it works
The stack behind every Sutrix study
01Staff review
Cases the rules cannot settle go to your team with the evidence beside them. Each decision is recorded: who decided, when, the reason and the record it applies to, so a reviewed case enters the study dataset with its decision attached.
02Repeatable preparation
Each study's preparation runs as the same ordered steps: source intake, study definitions, record linking, reconciliation, rule checks, staff review and the approved update. New cases and protocol changes reuse the steps instead of a new script.
03Study record
The chain behind each prepared field: the source it came from, the definition applied, the reconciliation decision, the review and the approved version, kept with the dataset so a prepared value can be traced or audited later.
04Permissions and access control
Workspaces and studies are scoped per team, source credentials are stored encrypted with AES-256-GCM, and every tabular upload is screened before it is stored, with columns that look like identifiers recorded on the file for your team's review.
05Study definitions
The protocol, codebook and data dictionary become the study's rules: definitions, time points, required fields and checks. REDCap dictionaries and Qualtrics question rows are read as the codebook, and the rules stay with the study for every update.
06Connectors
File upload for CSV, Excel, SAS transport, REDCap and Qualtrics exports; connected sources for REDCap, OpenClinica, Qualtrics, Oura wearables and FHIR (EHR sandboxes today); public files such as NHANES load directly. Sutrix runs in its own cloud and connects to your approved endpoints; deployment into your institution's cloud is a scoped option.