Medical Device Incident Reporting for Indian Clinics: MvPI, Evidence, and Investigation Handovers

The Indian Pharmacopoeia Commission, or IPC, provides reporting resources through the Materiovigilance Programme of India, known as MvPI. Its current toolkit includes resources for healthcare professionals, consumers, in-vitro diagnostics and field safety corrective actions. IPC medical-device reporting tools.

Do not assume that every safety concern belongs on a medicine-related adverse drug reaction form. Use the separate ADR reporting guide when a suspected medicine reaction is involved.

A single event may require more than one connected process. For example, patient care, a device investigation and a complaint response can proceed together without becoming the same record.

Assign someone to confirm the appropriate reporting pathway with MvPI or the relevant authority. Do not make the first staff member who notices a problem responsible for interpreting every regulatory requirement.

The clinician’s assessment and the clinic’s emergency procedures take priority over report preparation.

Administrative staff should promptly communicate what they observed, including whether the device remains in use. Decisions about continuing treatment, using an alternative device, reviewing earlier measurements or contacting affected patients belong with appropriately qualified professionals.

Avoid two unsafe shortcuts:

• Continuing to use a suspect device simply because a replacement is inconvenient.
• Abruptly disconnecting equipment supporting a patient without clinical direction.

The clinic’s procedure should identify who coordinates the immediate response and who provides technical support. For a small practice, one person may coordinate several tasks, but clinical and technical judgements still need the right expertise.

Document the decisions actually made. Do not retrospectively write an ideal sequence that differs from what happened.

“Problem with the monitor” is not enough when the clinic has several similar units.

IPC’s medical-device reporting form requests identifying information such as model, batch or lot, serial number, software version where applicable, and associated accessories. These details help distinguish the product family from the particular equipment involved. IPC MDAE reporting form, version 1.2.

For the clinic’s own preparation, connect three references:

Photograph readable labels where safe and authorised. Keep the original image, and check any transcribed identifiers against it.

Record uncertainty explicitly

If a label is damaged, record that limitation and request supporting documentation. Do not substitute the number from a neighbouring device.

If an accessory was exchanged before the incident was recognised, document the exchange and what remains uncertain. A complete-looking record containing guessed identifiers is less useful than an honest record with a clearly assigned follow-up question.

An incident can become difficult to investigate if the device is repaired, discarded or reset before anyone considers the evidence.

The UK’s MHRA advises against throwing away or repairing a device involved in an incident. This supports the general evidence-preservation principle; its reporting arrangements are UK-specific, not Indian legal requirements. MHRA guidance on device incidents.

For an Indian clinic, agree the next steps with the responsible clinician, competent technical personnel and relevant investigating parties.

Where safe and appropriate, the clinic’s procedure can provide for identifying and restricting access to affected equipment while instructions are obtained.

Do not improvise handling of contaminated devices, sharps, electrical hazards or implanted equipment. Evidence preservation does not override infection prevention or immediate safety.

Before an authorised repair or transfer changes the available evidence, record what is being changed, why, who authorised it and what information has been retained.

Use a short chronological account rather than a conclusion disguised as a description.

Compare:

“The device was defective and caused the incident.”

With:

“During the recorded procedure, the display showed an unexpected message. The operator informed the clinician. The clinician directed the immediate response. The device was subsequently removed from routine availability.”

The second account leaves room for investigation.

Record the context necessary to understand the observation: intended activity, observed behaviour, relevant times, operator account and immediate response. Label approximate times as approximate.

Keep direct observation separate from information received later. If a supplier subsequently offers an explanation, attribute it to the supplier and retain the supporting report.

WHO’s post-market surveillance guidance explains the importance of information gathered after devices enter use. A clinic’s account contributes evidence; it does not have to become a complete engineering investigation. WHO device-surveillance guidance.

The patient record should contain the relevant clinical assessment, decisions, communication and follow-up.

The device case should contain equipment identification, evidence references, technical correspondence and reporting activity.

Connect the two through controlled references. Avoid copying an entire patient chart into every supplier email or service ticket.

A useful arrangement is:

• The clinical record explains what happened to the patient and what care followed.
• The device case explains what equipment was involved and what happened to it.
• The submission record preserves what was sent externally.
• The action list identifies unfinished work.

Access requirements may differ across these records. A service engineer’s need to identify a device does not automatically justify access to unrelated patient information.

Where a clinical entry needs correction, use the clinic’s authorised amendment process. The medical-record correction guide explains why the original history should remain understandable.

A courier collection or engineer visit should not break the connection between the incident and the physical equipment.

Before an authorised transfer, prepare a brief handover record:

• Incident and asset references.
• Identification of the equipment and accessories transferred.
• Sender, recipient, date and purpose.
• Relevant handling instructions from qualified personnel.
• Documents or photographs accompanying the transfer.
• Expected next response and responsible contact.

Record what remains at the clinic as well as what leaves.

Do not confuse replacement with investigation

A replacement may restore operational capacity. It does not explain the original event or establish that patient follow-up and reporting are complete.

Similarly, a commercial credit note settles a financial transaction. It is not a technical finding.

Ask the recipient to acknowledge the items received. Track the investigation response separately from delivery of a replacement, and retain any limitations stated in the technical assessment.

These are suggested clinic controls, not a claim that one universal chain-of-custody template satisfies every investigation.

Use IPC’s current reporting materials rather than a saved form whose version is unknown.

The version 1.2 instructions distinguish initial, follow-up and final reports. They also explain the difference between notifying the manufacturer and submitting a report on the manufacturer’s behalf. IPC instructions for the MDAE form.

That distinction matters operationally. “The supplier knows” is not evidence that the clinic’s intended report has been submitted.

Have the responsible professional review the clinical content and any assessment fields. Have someone familiar with the equipment check its identifiers.

Do not invent an answer to complete a mandatory field. Seek clarification through the official reporting channel when required information is unavailable.

Confirm applicable reporting requirements and timelines promptly. This guide does not impose a single deadline across healthcare professionals, manufacturers, importers, device categories and event circumstances.

IPC publishes an ADRMS stakeholder manual specifically covering medical-device adverse-event reporting. It describes the online reporting workflow and instructs users to connect follow-up information to the original report number. IPC ADRMS manual for MvPI reporting.

Start from IPC’s official resources when accessing the reporting service. This article does not establish that every clinic already has the necessary account or access.

For internal tracking, distinguish:

• Prepared for professional review.
• Ready to submit.
• Submitted through the selected channel.
• Receipt or reference recorded, where available.
• Additional information requested.
• Follow-up sent.

Retain the submitted content, submission date, destination and available reference. If receipt is uncertain, label it uncertain and arrange follow-up; do not mark it confirmed.

A manufacturer report, an engineer’s email and the clinic’s submission may have different references. Link them without treating them as interchangeable.

Keep later information attributable rather than silently replacing the first account.

An in-vitro diagnostic concern can involve a test system rather than one piece of equipment.

IPC provides a dedicated IVD form covering products such as kits, reagents, controls and analysers. Its event categories include invalid tests, wrong results and suspected false-positive or false-negative results. IPC IVD reporting form.

The operational task is to preserve the relevant combination of information for qualified review.

For example, a concern involving a test result may require the laboratory’s original report, the relevant product identifiers and the laboratory’s investigation response. The clinic should not infer a device defect merely because two results differ.

Where another laboratory performed the work, distinguish what the clinic knows directly from what the laboratory has confirmed.

Any decision to reinterpret a result, arrange further testing or contact patients must be clinician-led. Do not turn an administrative tracking guide into a diagnostic protocol.

Consider this fictional exercise—not a customer incident or treatment example.

A clinic records unexpected behaviour from a reusable diagnostic device. The responsible clinician manages the immediate situation. An authorised coordinator arranges technical review.

The supplier offers to collect the main unit, but an accessory used at the time has already been moved to another room.

What the rehearsal should reveal

Can the team identify the original unit without relying on where it usually sits?

Can it establish which accessory was attached, or clearly record that this is uncertain?

Does the collection record specify the actual items transferred?

Can the coordinator find the relevant clinical entry without sending an unrestricted patient-record export?

Who checks whether the supplier’s response addresses the accessory question?

Add a late-arriving finding

Two days later, the technical report discusses the main unit but says the accessory was not examined.

The clinic should preserve that limitation. It should not summarise the report as “equipment checked; no problem.”

The responsible professionals decide what further assessment is needed. The coordinator records the decision, updates the investigation task and arranges any appropriate follow-up to the earlier submission.

The exercise tests traceability and communication—not whether staff can diagnose a technical failure.

Avoid a single “resolved” checkbox covering everything.

Before closing the internal coordination task, review the relevant responsibilities separately:

• Has patient follow-up been addressed by the responsible clinician?
• Is the device’s location and permitted status clear?
• Has the technical response been received and reviewed?
• Are reporting questions or requests still outstanding?
• Has any required follow-up submission been handled?
• Are corrective actions assigned and checked?

A device can remain unavailable while the reporting task is complete. A replacement can be operational while the investigation remains open.

Record the actual state and any outstanding dependency. Do not declare an unresolved cause “confirmed” merely because the clinic needs to finish its monthly paperwork.

If similar concerns recur, bring the connected records to the appropriate professional or reporting body rather than relying on an isolated service-ticket history.

CliniKite’s public features include longitudinal clinical records, investigation records, role-based access, audit logs, backups and exports. These can provide relevant source information for an incident review. CliniKite features.

Those capabilities do not establish a dedicated medical-device incident register, equipment investigation system, automatic MvPI submission or ADRMS integration.

During a CliniKite demonstration, use the fictional scenario and ask:

• Where would the clinical account be recorded?
• How would authorised staff retrieve relevant documents?
• What history remains after a correction?
• Which records can be exported, and by whom?
• Where would device custody and technical correspondence be tracked?
• Which reporting steps would remain outside CliniKite?

Review the security and data-control information alongside those answers. Confirm the implementation boundary instead of assuming that an EMR contains every quality-management workflow.

A useful medical-device incident process preserves connections that are easily lost: the event to the exact equipment, the equipment to its investigation, and the investigation to patient care and external reporting.

Start with a named coordinator, current MvPI resources and one fictional handover exercise. The practical test is whether the clinic can explain what happened, where the device went, what was submitted and what remains unresolved—without guessing or overstating the evidence.