
Remote support is safer and faster when the engineer receives a factual, structured report rather than a vague message that a device is “not working.”
Prepare a fault report with safe status, equipment identity, symptom timeline, operating context, visible evidence, data permissions, and a clear request—without opening the device or attempting hazardous repairs.
At Hongdee, we recommend making the report useful for triage while preserving patient privacy and staff safety. A remote contact should help an authorized support person understand what happened and decide the next safe step; it should not turn an untrained user into an internal repair technician.
What safety status should you establish before reporting?
The first decision is whether the equipment can remain in service while information is collected. A good report begins with risk control, not troubleshooting enthusiasm.
If there is damage, smoke, unusual heat, burning smell, exposed electrical material, unexpected movement, or another suspected hazard, stop use, secure the equipment, and contact authorized technical support according to local policy.

Separate symptom reporting from repair
Tell the user to stop and isolate the device when the symptom could create risk to a patient, operator, data, or facility. Record the status as “removed from use,” “on hold,” or the clinic’s equivalent. Do not repeatedly power-cycle a device that smells hot, sparks, moves unexpectedly, or shows physical damage. Do not open a cover, touch live parts, defeat an interlock, or bypass a lockout to obtain more information.
A report can say what was observed without claiming the cause. “The illumination stopped during setup” is useful. “The power board failed” is a diagnosis that remote staff may need to establish. We recommend keeping those statements separate so a guess does not become the repair plan.
If a patient was present, follow the clinic’s incident and clinical escalation procedures. This article does not provide patient treatment advice. Record only the information needed by the responsible team and support engineer. The immediate goal is to prevent recurrence or further exposure while preserving an accurate account.
Assign a safe reporter
Name the person who observed the symptom and the person responsible for the equipment. The reporter should be able to describe normal operation and follow only authorized, low-risk instructions. If support asks for a step that appears unsafe or conflicts with the manual or clinic policy, pause and request clarification. A support call is not permission to improvise.
Which identity and timeline details make a fault report actionable?
The second decision is whether the support team can identify the exact equipment and reproduce the context without guessing among product versions or sites.
Include the site, equipment category, exact model and serial information where appropriate, configuration, software environment, symptom time, recent changes, and the sequence that preceded the fault.

Capture identity before interpretation
Use the approved asset record, order record, or equipment label to document the manufacturer, model, serial or asset identifier, installation location, and relevant accessories. Add the table, stand, camera, computer, or interface connected when the symptom could involve the wider setup. The Hongdee service page provides a support contact route, but a service conversation still needs the exact equipment context.
Record the software name and version only if the clinic’s policy permits it and the information is visible through normal user controls. Include power or network context when relevant, but do not expose credentials or sensitive infrastructure details in an open channel. If the equipment was recently moved, cleaned, updated, connected to an accessory, or used in a new workflow, note the change and date without assuming it caused the fault.
Write a timeline that another person can follow
Use time-stamped observations: normal state, action taken, first symptom, visible message, immediate response, and current status. Note whether the symptom is constant, intermittent, or linked to a particular authorized step. If a restart was performed under the manufacturer’s instructions, record that fact and the result; do not conceal unsuccessful attempts. If no repeat was attempted because safety was uncertain, state that clearly.
Useful wording is concrete: “display shows an error after startup” or “motor movement stops before the selected position.” Avoid conclusions such as “the sensor is broken” unless an authorized technical source has already confirmed it. The engineer needs the observation and the conditions, not a confident but unsupported theory.
The third decision is how to give support enough evidence while protecting patient privacy, staff identity, and sensitive clinic information. A screenshot or video can contain more than the fault.
Collect only the minimum evidence needed, remove or mask patient identifiers, obtain the clinic’s authorization, and use the approved support channel rather than sending unrestricted files.

Prefer controlled evidence
Start with a written description and the exact on-screen error text, transcribed where possible. If a photograph of the equipment label is needed, frame only the relevant label. If an image or video is necessary, check for patient faces, names, dates of birth, medical record numbers, examination images, open email, passwords, or other unrelated screens. Crop or redact according to the clinic’s policy before transfer.
Ask who is authorized to send the material and where it may be stored. A supplier’s request for a file does not automatically authorize disclosure of patient information. If consent, privacy review, or a data-processing route is required, complete it before sending. Do not use a personal messaging account to bypass the approved channel.
We also recommend recording the evidence inventory: filename, capture date, what it shows, redaction performed, and recipient. If remote screen sharing is offered, confirm the session scope, participants, recording status, and stop procedure. A support engineer should not receive broader access than the fault requires.
Record what was not collected
Sometimes the safest choice is not to capture a patient-area video or to avoid repeating the symptom. State “no video supplied because patient information could be exposed” or “not repeated because movement was abnormal.” This gives the engineer a useful boundary and prevents them from mistaking missing evidence for negligence.
How should you send the report and control remote actions?
The final decision is whether the report creates a clear, authorized handoff. A technically detailed message can still be unsafe if the recipient, remote action, or next step is undefined.
Send the report through the approved support route, identify the requested help, confirm authorization for any remote session, and document instructions, decisions, and escalation boundaries.

Use a one-page fault template
A practical report can contain: contact and site, safe status, equipment identity, intended function, symptom summary, timeline, visible messages, recent authorized changes, accessories connected, evidence inventory, privacy approval, and the specific request. Ask whether support needs clarification, a manual, a controlled remote session, an authorized service visit, or a return/inspection decision.
| Report field | Good content | Avoid |
|---|---|---|
| Current status | Removed from use; no repeat attempted | “Probably safe” |
| Identity | Exact model and asset reference | Generic product family only |
| Symptom | Observable behavior and message | Unsupported component diagnosis |
| Timeline | Time-stamped sequence | “It suddenly broke” |
| Evidence | Redacted label or error text | Unrestricted patient image |
| Requested help | Triage and next safe step | Permission to open the unit |
Before a remote session, confirm who can authorize actions and whether the session may change settings, access data, or restart equipment. Keep a staff member present if clinic policy requires it. Stop if instructions could expose a hazard or exceed the agreed scope. The Hongdee quote contact page is intended for configuration and quotation questions; use the appropriate service route for a fault and confirm the support scope rather than assuming a commercial contact is an emergency channel.
Close the loop
After support responds, append the advice, date, recipient, and next action to the report. Record whether the equipment remains on hold, returns to service after authorized review, or requires further inspection. Do not write a “resolved” conclusion merely because a message was answered. Resolution should reflect the responsible technical or clinical process.
If the support route offers remote troubleshooting, treat it as a controlled information exchange. Remote guidance is not a blanket authorization to bypass safeguards or perform internal repair. Suspected electrical or mechanical hazards belong with authorized personnel.
Sources and scope
- Haag-Streit, “Services and service packages” (accessed 2026-10-12; peer example of technical support, field or factory service, loan-unit, and safety-testing concepts; not a Hongdee promise).
- Eyeconic EOE, “After-sales support” (accessed 2026-10-12; peer example of phone, video, and remote-support modes; not a Hongdee promise).
- World Health Organization, “Procurement resource guide” (accessed 2026-10-12; foundational documentation and procurement context).
Conclusion
A safe fault report states the hazard status, exact identity, timeline, privacy limits, and requested next step. Keep the equipment isolated when risk is suspected and leave internal repair to authorized professionals.

