An Endymed Pro output stop should be classified by whether it is a single event or a recurring one, because the two carry different evidence. A stop that happens once and never returns may have a different explanation from one that repeats every session, and a stop that appears only with one electrode or handpiece points in a different direction from one that appears with every configuration. The clinic’s first task is to record the pattern of the failure, not to explain it.

This pattern-based event file is for clinic staff who run an Endymed Pro and need to document an RF output stop without performing service work. It captures the occurrence, the components in use and the preserved consumable evidence, and it leaves the cause to a qualified review.

Record the reported RF symptom, error message and operating context

Quote the RF-related message or code exactly as the console shows it, with the date, the time and the operator’s name. Note which generator channel or output the session was using, which handpiece was connected and which electrode type and quantity were in place.

Record the pattern: was this the first stop for this configuration, or has the same configuration stopped before? Note whether the stop happened on the first firing attempt of the session or after the unit had been running, because the position in the session is part of the context.

If the clinic makes one further attempt, record the result and stop there. A failure that repeats immediately and one that does not are different evidence patterns, and the file must show which pattern occurred rather than leaving it to memory.

Record whether the stop occurred on the first treatment of the day or later in the session list. The position of the event in the day is context, and the review weighs it alongside the message.

Check the unit file for earlier stops with the same handpiece or electrode type. A recurring pattern is escalated with the earlier file so the qualified review can compare the events.

Ask whether the electrode type used at the stop was the type the treatment required and whether the quantity matched the session setting. A configuration mismatch is a context finding, not a cause, and it stays in the file for the review.

Note handpiece, electrode and connection state without disassembly

Check the visible state of the handpiece, the electrodes in use and the connection points: seating, labels, serials where present, wear, moisture or damage. Every observation is dated and photographed before anything is cleaned or changed.

Preserve the electrode evidence as it was at the stop. Electrodes are consumable components whose state at the event is evidence, and cleaning, replacing or re-fitting them before the review removes the very record the qualified party needs.

Photograph the electrode faces and connection surfaces before handling them. The surfaces are evidence, and handling them first can change what the photo would have shown.

If the console supports more than one channel, note which channel the session used. The channel number belongs in the file because a later test on the same channel is the one that counts.

The console state at the stop is written down before power-down, and the file lists what was not checked: no panels, covers, electrical measurements or adjustments. Those actions belong to the qualified party, and the list keeps the file honest about its own limits.

Separate user-error evidence from manufacturer-defined RF-delivery error records

Evidence is separated by source: the configuration and steps the operator used, and the console’s RF-delivery records. A deviation in the first group is a documented fact, and the two groups are never merged.

Console RF-delivery records sit in their own group: dated events that name this unit, its software state and the channel or component involved. The clinic asks the qualified party for these records and never reconstructs them from the message.

The groups stay separate so the review never has to untangle which evidence produced which finding. Each group is weighed on its own before anything is compared.

If the clinic runs several handpieces on the same console, the file names the serial of the handpiece in use at the stop. A stop logged without the handpiece serial cannot be compared with the next event on the same console.

Set safe shutdown and qualified-escalation conditions, preserving electrode evidence

When output stops, the clinic follows the documented shutdown and does not restart the unit to test. The preserved electrode evidence and the file then carry the event to the qualified party.

The unit and the electrodes from the event are set aside when the stop involves visible damage, moisture, an unusual odour or any safety-relevant condition. They stay set aside, marked unavailable, until the review ends.

The clinic writes its stop rules before the next event: repeated RF output stops with the same configuration, unexplained messages and safety-related conditions all stop the unit. The rules are kept with the event file so every shift applies the same standard.

The escalation package handed to the qualified party contains the event file and the preserved electrode evidence. The clinic does not clear the message, re-test after a reset or call the event a repair; those actions belong to the qualified record.

Define what a qualified diagnostic record must contain

The qualified diagnostic record must name the unit serial and software state, the channel and handpiece tested, the electrode configuration used, the method, the instruments, the date, the performer and the findings. Without the electrode configuration named, the record cannot be attached to this event.

The diagnostic record must respond to each open row in the event file: which evidence group the failure belongs to, what was tested, what was found and what was corrected. It also names what was not tested, because the record is judged on its limits as well as its findings.

Do not accept a summary that names no unit, no configuration and no date. The attributable record is requested in writing and kept in the file.

The record should state whether a software update occurred near the event and which version the console ran at the stop. A version change close to the stop is context the review needs to weigh.

Define evidence required before return to service

Service can resume only when three records are present: the qualified diagnosis, the corrective action naming the unit and configuration, and a verification that passed. The file, not the display, is the gate.

The event file and the diagnostic record are compared before acceptance: the finding must correspond to the recorded pattern and configuration, and a mismatch stays unresolved in the file rather than being waved through.

When the same configuration stops again, the clinic attaches the earlier file and asks the review to compare patterns. The recurrence is the subject of the escalation, not a footnote to it.

Ask whether the corrective action’s channel re-test used the same handpiece and electrode configuration as the stop. Verification under a different configuration leaves the pattern question open.

The corrective action should also name which electrode configuration was used in the verification, so the pattern question can be answered from the record rather than from the provider’s memory.

The clinic keeps the event file number on the service request it sends, so the provider’s response can be matched to the event without re-explaining it.

Keep the event file with the unit history and keep the preserved electrode evidence identified by serial until the review ends. A file without the consumable evidence cannot support a recurrence comparison, because the second event would have nothing to be compared against.

The file receives a review date when it is closed, and the clinic checks on that date whether the unit, the serials and the records still match. A file that is never re-checked drifts from the asset it describes.

Frequently Asked Questions

Why must electrode evidence be preserved before escalation?

Because electrodes are consumable components whose state at the event is evidence, and cleaning or replacing them before the review loses it. The register preserves the serials and photos as part of the escalation file.

How should the clinic treat a stop that does not repeat on the next attempt?

Record it as a single-occurrence event with the configuration and context intact, and keep the file rather than treating it as nothing. A stop that does not repeat is still an event the qualified review may need to compare if the same configuration stops again later.

References

• EndyMed official website (manufacturer resource)