The value of a scan often shows only at the second scan. That assumes the first dataset was kept complete, named clearly and captured under conditions that can be reproduced.
1. What one capture should leave behind
Keeping only a screenshot turns analysable data into a promotional image. A complete record should contain at least the original 3D model, the texture, the capture date and device information, the capture conditions, the analysis results, the report files and, if a simulation was made, the design version.
The original model is the basis for any later recalculation. A report can be redone; a lost model is hard to replace. Keep raw data and reports in separate folders rather than saving exported files only.
2. Naming rules: do not use the patient name as a file name
A recommended structure is patient ID_date_device_region_version, using the hospital record or file number instead of the name. When a name appears in a file name, personal information leaks easily during transfer, backup and screenshots.
Version numbers separate first visits, follow-up visits and design revisions. Without them, it is hard to tell six months later which file holds the latest plan.
3. Follow-up re-capture: the protocol matters more than the device
For re-capture, use the same device, the same working distance, the same posture and the same expression instruction where possible. Makeup, lighting and hairstyle should also stay as consistent as possible, and the record should note how this session differed from the last.
If the device or software version changed in between, mark it in the record. Cross-device comparison is not ruled out, but conclusions have to be more cautious: a device difference is not a patient change.
4. How to read a time-series comparison
Three common views: the color map shows the overall distribution of differences, the cross-section shows height change at one plane, and the multi-open view puts several models on one screen (up to 8 models). Together with volume, area and height-difference metrics, they form a record that can be reviewed.
Confirm the protocol first, then read the difference. When protocols do not match, even a polished color map cannot serve as a basis for judgement.
5. Storage, backup and permissions
The system supports local processing and storage, so data stays inside the institution and is easier to manage. A scheduled backup routine is still advisable, with clear rules on who may export and who may delete. At staff handover, accounts and dongles should be logged together.
| Record field | Content | Purpose |
|---|---|---|
| Patient identifier | Hospital ID, not the name | Links to the medical record and lowers leak risk |
| Capture information | Date, device model, software version, operator | Shows whether data are comparable |
| Capture conditions | Distance, posture, makeup, lighting | Reproduces the protocol at re-capture |
| Raw model | 3D mesh and texture | Later recalculation and re-analysis |
| Analysis results | Metrics, maps, measured values | Consultation communication and follow-up comparison |
| Reports and designs | Report files, simulation versions | Plan discussion and version traceability |
6. Boundaries of personal information handling
3D facial data is personal information and may count as sensitive personal information in some contexts. Obtain clear consent before capture, stating the purpose, retention period and sharing scope; de-identify data for external display and avoid using an identifiable face model directly in public promotion.
The exact consent wording, retention period and access rights should follow institutional policy and local regulations. This article discusses the data management workflow only and does not constitute legal advice.
Related pages: 3D Digital Plastic Surgery System, Procurement and service FAQ, MVS-P6, MVS-800.
This article describes product functions and workflows and is not medical advice; specific configurations, metrics and deliverables are subject to the product version and contract.