Published research and reference, not medical advice. Full notice below.
The data behind the standard.
This is the data contract: what a research dataset from Arcametric actually contains before you ask for one. It sets out the export boundary, the data model, the variable domains, and the standard export modules a principal investigator, data-science team, or review board would evaluate.
What exports, and what stays with the clinic.
Arcametric keeps the clinic's identity records separate from the research export. Direct identifiers and the site's own subject map stay local; the export carries de-identified, structured data only. By design, no field in the shared model can hold a patient name.
Stays with the clinic
- Patient name
- Date of birth
- Address, phone, email, MRN
- Site-local subject map
- Narrative clinical notes
In the standard export
- Synthetic subject ID (stable within the dataset)
- Pseudonymous session ID
- De-identified outcomes and safety data
- Structured assessment scores
- Dose and vitals events
Seven domains. Select one to see its fields.
The export is organized around seven stable domains, from subject baselines to experiential observations. Select any domain to see the exact variables it carries.
- Age band or age at session
- Sex
- Weight range (kg)
- Smoking status
- PHQ-9
- GAD-7
- PCL-5
- ACE
- MEQ-30
- Expectancy scale
- Substance class (RxNorm)
- Route of administration
- Dose (mg)
- Dose per kg (mg/kg)
- Cumulative dose (mg)
- Administration time
- Relative timepoint
- Session identifier
- Heart rate
- HRV
- BP systolic / diastolic
- SpO2
- Respiratory rate
- Temperature
- Consciousness level
- Relative minutes post-dose
- MedDRA code
- CTCAE grade (1 to 5)
- Causality classification
- Resolution status
- Intervention type
- Override justification codes
- Substance (RxNorm CUI)
- Concomitant medication (RxNorm)
- Interaction severity tier (as referenced)
- Mechanism of action (structured)
- Management category recorded by the clinician
- Follow-up window
- Daily mood
- Daily anxiety
- Daily sleep
- Daily connection
- Follow-up PHQ-9
- Follow-up GAD-7
- C-SSRS
- Observation concept (from the governed list)
- Classification (experiential or acute effect)
- Source (patient-reported or clinician-observed)
- Session-relative time
- Aha Moment marker
Each field ships with machine-readable and reviewer-readable metadata: type, unit, timepoint, source, and its standard or vocabulary. The vocabulary crosswalk is the Coding Landscape.
Structured outputs, ready for analysis.
Each module is a flat, machine-readable file scoped to one analysis job. They open in Python, R, SPSS, and SAS with no cleaning step first.
Longitudinal Outcome Trajectory
CSV, JSON
Python, R, SPSS, SAS, meta-analysis
Dosing Administration
CSV
Route, dose, timing, and protocol analysis
Safety Event Extract
PDF, CSV
Adverse event review and IRB reporting
Assessment Score Extract
CSV
Instrument scores by subject and timepoint
Follow-Up Window Completion
CSV
Retention, durability, collection-window review
Audit Documentation Support
PDF, CSV
Protocol review and documentation completeness
The record, as it is captured.
These are short clips of the actual software, built from de-identified demo data. Each one answers a question a reviewer tends to ask about how the record is captured.
Request a technical review.
Arcametric is open to qualified research review. Request access for a technical walkthrough of the data model, the export boundary, and the current export formats; we will name the limitations directly.