Access
Controlled access while in development.
The workspace sits behind authenticated sign-in; the public pages carry no patient data. Pilot access is scoped and granted deliberately per partner while the product is in controlled release.
Request a pilot
Request a 3DPainMap pilot.
Start with one clinic, course, or study. Tell us about your use case and we will follow up about fit, access, and next steps.
Security & privacy
Data & trust, agreed up front.
Data handling
Sensitive information, handled responsibly.
Records derive from one finding-level model and export only what a pilot needs. De-identified or simulated data is used for demos and education, and governance specifics are agreed with each pilot partner up front rather than asserted as a blanket claim.
Ownership
Your records, in portable formats.
Pilot partners keep ownership of their records. The canonical JSON tier is a lossless, versioned source of truth, and a vendor-neutral FHIR R4 DocumentReference Bundle is available for handoff.
Is 3DPainMap HIPAA compliant?
We do not make a blanket compliance claim. 3DPainMap is designed for responsible handling of sensitive information, and we agree the specific data-governance and any required agreements with each pilot partner before sensitive data is involved.
Does it use AI to interpret pain?
No. 3DPainMap captures what the patient reports and measures the painted surface. The derived metrics are deterministic calculations over that surface — there is no automated interpretation or prediction.
Are the measurements validated?
Not yet. The pipeline is built for validation — reliability, construct validity, and responsiveness studies are scoped on the roadmap — but we present metrics as derived symptom-burden measures, not validated clinical endpoints.
Where is my data stored, and who can see it?
Records are scoped to the authenticated workspace. The pilot form stores only what you submit, and a pilot agreement sets out storage, access, and retention before any patient data is handled.