Why Can a DEKA ONDA Plus Stop Delivering Output?

An ONDA Plus output stop is defined by the pair that was running when it happened. The generator and the connected applicator are separate serviceable units, and the same stop message can mean one thing with one applicator attached and another with a different applicator. The clinic’s first task is to fix the pair in the record: which generator serial, which applicator serial and which software state were in use at the moment output stopped.

This pair-focused event file is for clinic staff who run an ONDA Plus and need to document an output stop without opening equipment. It records what was connected, what the console showed and what was visible, and it leaves the cause to a qualified review.

Record the reported symptom, error message and operating context

Quote the message or code exactly as the console shows it, with the date, the time and the operator’s name. Then name the pair: the generator serial and software state, the applicator serial that was connected and the cable used between them.

Record the session context: what the treatment was doing, how long the applicator had been in use and whether the stop happened at the start of a sequence or during it. A stop that occurs as the sequence starts and one that occurs halfway through describe different moments of the same event.

One retry is made on the same pair and its result recorded; after a confirmed stop, no further retries happen. The single result tells the review whether the pair repeated the failure without adding extra operation to the record.

Check whether the same pair has stopped before by looking at the unit file. A recurring stop on the same generator and applicator pair is escalated with the earlier file, because the history of the pair is evidence about the pair.

Record whether the software state shown at the stop matches the version named in the last service record for the generator. A mismatch between the two is a context finding, not a cause, and it belongs in the file for the review.

Note applicator, cable and connection state without disassembly

Check the visible state of the pair: the applicator seated in its connection, the serial and label readable, the cable free of cuts, kinks or moisture and the connectors free of damage at both ends. Each observation is dated and photographed.

Record the console display at the stop: the message, any status indicators and whether the console still recognised the applicator or showed it as disconnected. Whether the pair stayed recognised is part of the event and is noted before power-down.

Note whether the applicator seated without resistance and stayed seated during the attempt. Seating behaviour is observable, and the audit records it as it happened rather than interpreting it.

Note whether the applicator cable routes through any moving part of the cart or arm, and record visible pinch or strain points along its length. A pinch point is a finding on the cable row even when the cable still passes a signal.

Note what was not checked. The clinic does not open the generator, remove covers, measure electrically or adjust applicator components, and the file says so in the same place as the observations.

Separate user-error evidence from manufacturer-defined microwave and interlock records

The file splits evidence by its origin: the operator’s handling of the pair and the console’s microwave and interlock records. Deviations from the documented procedure are entered under the first origin as facts, not as blame.

The second group holds the manufacturer-defined microwave-delivery and interlock records: documented events that name this generator and applicator pair, its software state and what the console registered. These records are requested from the qualified party and are not inferred from the message.

The two evidence origins are kept apart so the qualified review can weigh the operator’s handling and the console records independently. A blended account would make both impossible to attribute.

If the clinic holds more than one applicator of the same model, the file names the serial of the one connected at the stop. Same-model applicators without serials cannot be compared, so the pair must be identifiable on every page.

Set safe shutdown and qualified-escalation conditions

Stop the sequence using the documented procedure and power the unit down; do not restart it to see whether the message repeats. After shutdown, the operator’s part of the event is finished and the file carries it forward.

If the stop involves visible damage, moisture, an unusual odour or a safety-relevant condition, the generator or applicator is set aside and marked unavailable. The marking stays until the review is complete.

Before the next event the clinic writes what triggers escalation for a pair: a repeated stop on the same generator and applicator, an unexplained message or a safety-related condition. The trigger list sits with the pair file so the decision is the same on every shift.

Escalation goes to a qualified party with the file, and the clinic never describes the event as repaired. The word repair belongs to the qualified party’s record, not to the clinic’s file.

Define what a qualified diagnostic record must contain

The qualified diagnostic record must name the generator serial and software state, the applicator serial connected at the stop, the components tested, the method, the instruments, the date, the performer and the findings. Without the pair named, the record cannot be attached to this event.

For every open row in the pair file, the record supplies the evidence group, the tests, the findings, the correction and the tests not performed. An open row that the record skips remains open.

The clinic does not accept a summary that omits the pair, the method or the date. The full attributable record is requested in writing, and the request stays with the file.

The record should name the software version current when the test was run and the version current at the stop. A version change between the two is visible in the file rather than discovered later.

Define evidence required before return to service

The pair is cleared for service when the file contains the qualified record, a corrective action naming the generator and applicator, and a successful post-work verification. A ready screen without those documents is not clearance.

The diagnostic record is compared with the pair file: the finding must correspond to the documented pair and symptom, and any mismatch is resolved before the work is accepted. The comparison also anchors any later warranty claim.

A recurring stop is handled as a pair history: the new event is attached to the earlier pair file, and the comparison asks whether the same generator and applicator failed again or the pair changed. The file must be able to show which one occurred.

Ask whether the corrective action was verified on the same applicator serial that was connected at the stop. If the verification used a different applicator, the pair question is not closed.

Where the clinic owns a backup applicator, the review should state whether the stop was reproduced on the backup pair. A stop that follows the applicator is different from one that stays with the generator, and the file records which happened.

The pair file also notes whether the generator or applicator was moved, serviced or updated between the stop and the qualified review, because a change of state in that gap is context the diagnosis must account for.

Keep one event file per generator serial and name the applicator serial on every page. A stop that is logged without the pair cannot be compared with the next stop, and the file exists to make that comparison possible.

When the event is closed, request current condition, configuration and evidence for the exact DEKA ONDA Plus option before deciding its future. The platform context is in the ONDA Plus comparison guide, and the ONDA Pro treatment comparison covers the sibling view; DEKA ONDA systems is the product reference.

Frequently Asked Questions

Why does the clinic file never describe the event as a repair?

Because calling the event a repair would claim an authorisation the clinic does not have. The file records evidence and escalation, and repair language belongs to the qualified party’s record alone.

What if the same stop appears with a different applicator attached?

Log the new event with the new pair and attach the earlier file. A stop that moves between applicators points away from a single applicator, and the qualified review needs both pairs named before it can compare them.

References

• DEKA official website (manufacturer resource)