The real value of a 3D device is not that it scans a model, but what happens once the model enters the consultation: can it be analysed, can it produce a report, can it be used for design, can it be compared.
1. Capture: standardize the data first
The same patient, the same device, the same working distance and the same posture are the preconditions for any later comparison. Floor-standing devices such as the MVS-P6, MVS-800 and MVS-C6 complete a full scan in under 2 s; the MVS-M6 and MVS-M2N in under 9 s; the MVS-N1 is used intraoperatively; the ZETTA completes a full scan in under 25 s.
Before capture, deal with hair, makeup, reflections and occlusion. The hairline, the preauricular area and the mandibular border are common gaps; after capture, check mesh completeness in the software before moving on to analysis.
2. Analysis: how to use 60 facial metrics
The 3D Digital Plastic Surgery System provides 60 facial metrics covering proportions, angles and symmetry, and a curvature map for skeletal and soft-tissue analysis. Many metrics does not mean all of them should be explained to the patient; in a consultation it is better to choose 3-5 around the chief complaint.
For the nose, for example, discuss the nasofrontal angle, the nasolabial angle and the dorsum curve; for the midface, the midfacial proportions and volume distribution; for the contour, left-right differences and continuity of the mandibular border. Numbers give a description a reference point; they do not replace judgement.
3. Reports: turning what is on screen into something to take away
A report is the carrier that fixes the content of a consultation. The system supports report output and printing, and can include model screenshots, metric values and notes. A report should state the capture date, device model and metric definitions so it can be compared at follow-up.
A report is communication material, not a diagnostic conclusion. Judgements about indications, risks and treatment plans remain with the clinician.
4. Design: aesthetic design and injection simulation
Adjusting a preview on the 3D model turns "what if this point were slightly higher" into a visible change in form. Injection simulation is used to observe contour change after volume adjustment; aesthetic design supports plan discussion for the nose, chin, midface and other areas. The nasal design workflow on the MVS-M6, MVS-M2N and MVS-M6HD follows the same logic: capture first, then design, then compare.
Design results are used for communication and plan discussion, not as a commitment about post-treatment results. This should be stated clearly during the consultation.
5. Comparison and archiving: two dedicated pages
For how to use the color, cross-section and multi-open comparison views, and what photos, 2D and 3D can each show, see Pre- and post-treatment comparison: what photos, 2D and 3D can each show. The point to stress here is the precondition: the same device, the same distance and the same expression, otherwise the numbers are not comparable.
For which fields a record should keep, how to name files and how to re-capture at follow-up, see 3D scan data in records and follow-up. The bottom line is to keep the raw model, the analysis results, the report and the design version together: save screenshots only and the data can no longer be analysed.
| Step | Output | Common issues |
|---|---|---|
| Capture | 3D model + texture | Hair occlusion, makeup reflections, posture drift |
| Analysis | 60 metrics, curvature map | A pile of metrics with no link to the chief complaint |
| Report | PDF / printout | Missing capture conditions and metric definitions |
| Design | Simulation plan | Treating a simulation as a commitment about results |
| Comparison | Color / cross-section / multi-open views | Inconsistent protocol before and after |
| Archiving | Case record | Keeping screenshots but not raw data |
Related pages: 3D Digital Plastic Surgery System, MVS-P6, MVS-800, MVS-C6, MVS-M6, MVS-M2N, MVS-N1, ZETTA.
This article describes software functions and workflows and is not medical advice; specific metrics, modules and report layouts are subject to the software version and contract.