When a Fotona SP Dynamis Pro stops delivering output, record the symptom, error message, time and operating context, preserve any system logs or screen information, and note only externally visible connection states. Do not open the unit, bypass interlocks or attempt repairs; follow only the operator-visible checks stated in the current manufacturer instructions, otherwise stop use and escalate with the preserved evidence.

This guide owns the safe symptom-evidence and escalation decision for a used or in-service SP Dynamis Pro. It does not diagnose causes, and it does not provide repair, disassembly or service-mode instructions. Its purpose is to collect the evidence that a qualified party needs and to define when use must stop.

Use this guide the moment output stops, while the evidence is still fresh. The record is time-sensitive: the symptom, the message, the context and the logs are best captured immediately, before anyone restarts the unit or changes the configuration. What the record does not contain is as important as what it does: no repair theories, no conclusions and no steps that were not performed.

Assign one person to own the evidence file. When multiple people see a failure, the file needs a single owner who collects the symptom record, the logs and the escalation request, and who keeps the timeline coherent. Without an owner, evidence is scattered and the timeline is reconstructed from memory.

Record symptoms, error messages and operating context

Record what happened before output stopped: the symptom as observed, the exact error message or code shown, the time and date, and the operating context such as the application, the handpiece in use and the steps immediately before the event. Record the information as observed, without interpreting it as a cause.

Keep the record factual and dated. A symptom log that states what was seen and when is evidence; a log that guesses why is not. Do not add repair theories to the record, and do not let a restart that restored operation be treated as proof of safety.

Record the sequence of events as it happened: what was being done, what the display showed, what the operator did next and what changed. The sequence helps a qualified party separate the trigger from the symptom, but only the recorded facts belong in the file, not an interpretation of which event caused which.

Also check:  What is the Minimally Invasive Laser & Aesthetic Market Forecast for May 2026?

Note anything unusual in the environment at the same time: power events, recent configuration changes or service work, and any other systems on the same circuit. These are context facts, recorded as observations, and they help the qualified party without being treated as causes.

Buyer-observable checks that do not open or bypass the system

Limit checks to what the current manufacturer instructions allow an operator to see: externally visible connection states, seating of handpieces and connectors, and any status the system displays. Follow only the operator-visible checks stated in the current manufacturer instructions; otherwise stop use and escalate with the preserved evidence. Never open the housing, bypass interlocks, reset errors to continue running, or modify software or service mode.

If the manufacturer instructions do not specify an operator-visible check for the situation, do not improvise one. The absence of a listed check is a stop-and-escalate condition, not an invitation to experiment.

Photograph or capture what the system displays where the instructions allow, and keep the captures with the log. Screen information is evidence only when it is dated and unmodified; do not crop, annotate or stage it in a way that could change what it records.

If a capture is not possible, write the exact message text and the time verbatim. A handwritten record is weaker than a capture but far better than nothing, and it still carries the date and the context needed for escalation.

Configuration, interlock-status and service-record evidence

Record what can be documented without intervention: the configuration in use, any interlock status the system reports, and the relevant service history. Preserve system logs, screenshots and any messages shown, dated at the time of capture. These records let a qualified party work from evidence rather than from memory.

Do not assume that configuration or interlock mechanisms apply unless the system or the manufacturer documentation states them. Record what the system reports; leave the interpretation to qualified diagnosis.

Attach the relevant service history to the record if it exists: recent service dates, parts replaced and configuration changes. History is context, not cause; it helps a qualified party understand the unit’s background without replacing the diagnostic record.

Also check:  Is Your B. Braun Inventory Safe? A May 2026 Recall Update

Do not alter the service history to fit the event, and do not let a recent service date become an automatic explanation. The history is attached as-is; the qualified diagnostic record is the place where causes are identified.

Conditions requiring safe shutdown and escalation

Stop use and escalate when output stops without an operator-visible explanation, when the system reports an error that the manufacturer instructions do not list as operator-resolvable, when a connector or cable shows damage, or when any attempt to continue could bypass a safety function. Safe shutdown means powering down according to the manufacturer instructions and preserving the evidence before the unit is moved or serviced.

Escalation goes to qualified service with the preserved record: symptom, error messages, time, context, configuration, logs and service history. A complete escalation file is what turns a stopped unit into a diagnosable one.

State in the escalation request what was observed and what was not done: no disassembly, no bypass and no error reset. This protects both the unit and the clinic, because it tells the qualified party exactly what evidence is untouched and what boundaries were respected.

Agree the escalation path before it is needed: who the qualified party is, how the unit will be transported or accessed, and who authorises the work. A clinic that has agreed the path in advance escalates faster and with less friction than one that starts looking for a service provider after the failure.

What a qualified diagnostic record should contain

A qualified diagnostic record should state the system and software version, the date, the technician or organisation, the diagnostic method, the findings and the recommended next step. It should separate measured results from interpreted conclusions, and it should identify which parts or tests were involved.

Request the record in writing before any return-to-service decision. A verbal explanation is not a diagnostic record, and a record without attribution or method cannot support a safety decision.

Review the record against the failure file: does it name the system and software version, does it address the recorded symptom, and does it state the method and findings? A record that does not connect to the failure evidence is a service report, not a resolution of this event.

Evidence required before the system returns to service

Before the system returns to service, require documented evidence that the condition is resolved: a qualified diagnostic record, any repair or replacement performed with attribution, and a functional-test record from the same qualified party. The buyer’s evidence file from the failure is part of that record and should be kept with it.

Also check:  What Is the Womed Leaf PREG2 Trial and Its Cost?
Evidence item What to record Required before return to service
Symptom and error record Symptom, message, time, context Yes
System logs and screens Dated captures as shown Yes
Operator-visible connection state Externally visible state only Yes
Qualified diagnostic record System, method, findings, attribution Yes
Repair or replacement record Scope, parts, attribution Yes if work performed
Functional-test record Dated qualified test result Yes

Return to service only when the record shows the condition is resolved by qualified work and the functional test is dated and attributable. A restart that restored operation is not such evidence on its own.

Keep the complete file, from the first symptom to the return-to-service test, in one place. If the unit fails again, the new event is compared against this file; if a warranty question arises, the file shows what happened and who resolved it. The file is the asset that survives the repair, and it is the same file the clinic should show to any future service provider for this unit.

When the evidence is complete, review Fotona laser systems and request current service, support and warranty information in writing. The used SP Dynamis Pro risk framework covers the wider evaluation, and the new-vs-refurbished cost comparison covers the price side of the decision.

Frequently Asked Questions

Can a clinic clear an error code and continue using the system?

Only if the current manufacturer instructions list that action as an operator-resolvable step and the condition behind the error has been understood. Otherwise, clearing the error to continue running is a bypass and must not be performed; stop use and escalate with the preserved evidence.

What evidence should be kept after a qualified repair?

Keep the symptom record, the logs, the qualified diagnostic record, the repair or replacement record and the dated functional-test result together. This file is what supports the return-to-service decision and any later warranty question.

References