Least data
We aim to collect only what the reporting workflow requires, and we ask practices to use their own non-identifying references wherever a label is needed.
Data responsibility
Careful with information, plain about limits.
OraQuest takes a deliberately cautious approach to information. This page describes how we think about data and what this demonstration environment does and does not do. It makes no certification or compliance claims.
Access by role
Practice users, reporting specialists and administrators see different things. Access to a case is limited to the practice that created it and the specialists responsible for reporting it.
Recorded activity
Status changes, assignments, information requests and report releases are recorded so a case history can be reconstructed.
Notifications kept thin
Where notifications are sent, the intent is to reference a case number and a general status only, with details available after signing in.
Limits of this environment
What this prototype will not do
- It does not accept, transmit, process or store real patient information of any kind.
- It does not accept CBCT or DICOM studies, medical images or clinical reports. The upload step is a simulation and file storage for clinical material is disabled in this build.
- All cases, attachments and reports visible in the portal and workspace are synthetic demonstration content.
- Nothing produced here is suitable for clinical use, and nothing on this site should be read as clinical advice.
Enabling real clinical file handling would require a separately reviewed and approved backend, together with completed privacy, security, contractual, retention, deletion, backup, breach-response and jurisdictional work. That work has not been done and is out of scope for this phase.