An Adverse Event Is Not Always Obvious: A Practical Guide for Australian Listed Medicine Sponsors
For sponsors of listed medicines, pharmacovigilance does not begin when a report reaches the PV team. It begins when someone, somewhere in the organisation, first receives information about a possible adverse reaction.
That information might come through a customer complaint, an email to the sales team, a social media comment, a distributor or a conversation with a healthcare professional. It may not look like a conventional adverse event report, and the person receiving it may not realise that it requires further assessment.
This is where gaps in a sponsor’s pharmacovigilance system can emerge.
For Australian sponsors of listed medicines, including complementary medicines and supplements, having a process for collecting and managing safety information is essential. The challenge is ensuring that relevant information is recognised, documented and escalated, regardless of where it originates.
1. Why Adverse Events Can Be Missed
One of the most common practical challenges in pharmacovigilance is recognising a potential adverse reaction when it is presented as an ordinary customer interaction.
Consider the following examples:
A customer contacts customer service to say that they developed nausea after starting a new supplement.
A consumer leaves a negative online review stating that a product caused a rash.
A sales representative receives a message from a healthcare professional about a patient experiencing dizziness after taking a product.
A distributor forwards a complaint from a customer who experienced palpitations after using a listed medicine.
A customer contacts the company to request a refund because they believe a product caused an unexpected symptom.
These interactions may initially appear to be routine customer service or product quality matters. However, they may also contain information relevant to the safety of the medicine.
The person receiving the information does not need to establish that the product caused the reaction. Nor should they decide independently whether the event is medically significant enough to escalate.
Their role is to recognise the potential safety information, capture it appropriately and follow the sponsor’s established procedure.
The key principle is simple: recognising a potential adverse event is not the same as confirming that an adverse reaction has occurred.
2. Know Where Safety Information Can Originate
A sponsor’s pharmacovigilance system should account for the different ways in which information about a product’s safety may be received.
Relevant sources can include:
Consumers and caregivers
Healthcare professionals
Customer service and complaints teams
Sales and marketing representatives
Distributors, retailers and other commercial partners
Social media, websites and online product reviews
Published scientific and medical literature
Post-marketing activities and other company-sponsored initiatives
Contractors and outsourced service providers
The practical challenge is that these sources are often managed by different departments, each with its own procedures and priorities.
For example, a customer service team may record a complaint in a customer relationship management system, while the PV team maintains a separate safety database. Unless there is a defined process for transferring relevant information between the two, a potential adverse reaction can remain in the customer service system without being assessed by the PV function.
The same risk exists when safety information is received by a third party. A distributor or outsourced call centre may not use the sponsor’s internal procedures, and its employees may not recognise the importance of forwarding the information promptly.
Sponsors should therefore map their information flows and identify every department, external party and communication channel through which potential safety information may be received.
3. What Should Employees Do When They Receive a Potential Adverse Event?
Employees should not be expected to perform a medical assessment or determine causality. Instead, they should follow a clear and straightforward process.
Step 1: Recognise and escalate
If a communication suggests that a person may have experienced an unwanted medical occurrence after using the product, employees should follow the sponsor’s escalation procedure.
They should not dismiss the report because the symptom appears minor, the customer is unsure of the cause, or the information is incomplete.
Step 2: Capture the original information
The original wording used by the reporter can be important. Employees should preserve the communication and document the information available, rather than rewriting it in a way that changes its meaning.
Relevant information may include:
The product name
The symptom or event described
When the product was used and when the event occurred, if known
The date and source of the initial communication
The reporter’s contact details, where available
Any treatment, outcome or other information provided
Employees should record what is actually known and avoid filling gaps with assumptions.
Step 3: Forward the information promptly
The information should be transferred to the designated PV contact or responsible function in accordance with the sponsor’s procedure.
The process should be clear enough that an employee can follow it without needing to determine whether the event meets the criteria for a valid case or requires regulatory reporting.
Step 4: Preserve the audit trail
The sponsor should be able to establish when the information was first received, who received it, when it was escalated and how it was subsequently handled.
This is particularly important when information passes through several departments or external organisations before reaching the PV function.
4. What Makes an Adverse Reaction Report Valid?
A potential report does not need to contain a complete medical history or every detail about the product to warrant attention.
For an individual case safety report, the four minimum elements generally used to establish validity are:
An identifiable reporter
An identifiable patient
A suspect medicine
At least one suspected adverse reaction
These elements establish the minimum information required for a valid case. They do not mean that every report containing all four elements must automatically be submitted to the TGA. The sponsor must also assess the applicable reporting requirements and circumstances.
Conversely, a report should not simply be discarded because one or more elements are initially missing.
For example, a consumer might write:
“I started taking your supplement last week and now I feel dizzy. Could it be related?”
The sponsor may not yet know the consumer’s age, the exact start date of the symptoms or whether the consumer has consulted a healthcare professional. Nevertheless, the communication contains potential safety information that should be documented and assessed.
The PV team can determine what additional information is needed and whether follow-up is appropriate.
Sponsors should also ensure that employees understand the difference between an incomplete report and a report that does not meet the minimum criteria for a valid case. The two should not be treated as interchangeable.
For further detail, refer to the TGA’s pharmacovigilance responsibilities of medicine sponsors.
5. Why the Date of First Receipt Matters
One of the most important operational considerations is the date on which the sponsor first receives the relevant information.
Under the TGA’s pharmacovigilance guidance, serious adverse reaction reports occurring in Australia must be reported as soon as possible and no later than 15 calendar days from first receipt, subject to the applicable requirements.
For this purpose, Day 0 is linked to receipt of the four minimum data elements by any of the sponsor’s personnel, including sales representatives and contractors. Where another company is involved, the arrangements must facilitate timely transfer of information so that the reporting timeframe is met.
This has a practical consequence: the date the PV team receives a report may not be the date on which the reporting clock began.
Example
A customer contacts a sponsor’s customer service team on Monday and reports a suspected serious reaction. The customer service employee records the complaint but forwards it to the PV team on Thursday.
The sponsor should not assume that the reporting clock begins on Thursday simply because that is when the PV team received the information. The original receipt date and the information available at that time must be assessed.
This is why sponsors need defined escalation timelines, clear responsibilities and a process for capturing the date of first receipt.
It is also why training employees to recognise potential adverse events is a compliance control, not merely an administrative exercise.
6. What About Social Media and Online Reviews?
Social media and online reviews can create additional challenges because the information may be brief, informal or difficult to verify.
A comment such as “This product gave me a terrible headache” may warrant further assessment, even if the person has not contacted the sponsor directly.
Sponsors should establish a proportionate process for identifying and handling potential safety information from their digital channels. This should clarify:
Which channels are monitored and by whom
How frequently relevant channels are reviewed
How potential adverse event information is documented
How the information is escalated to the PV function
How attempts to obtain further information are handled, where appropriate
How records of the review and subsequent actions are maintained
The process should reflect the channels the sponsor actually uses, including relevant arrangements managed by digital agencies or other contractors.
Sponsors should also distinguish between identifying a potential report and obtaining enough information to assess it. A brief online comment may not contain sufficient information to establish a valid case, but that does not remove the need to follow the sponsor’s defined process for handling potential safety information.
7. What If the Complaint Also Involves a Product Quality Issue?
A complaint may contain both safety and quality information.
For example, a consumer may report that a supplement had an unusual smell and that they experienced vomiting after taking it.
This may require assessment by both the pharmacovigilance and quality functions. Depending on the circumstances, further investigation could involve the product batch, manufacturing records, storage conditions, distribution arrangements or other quality information.
The two processes should not operate in isolation.
A quality investigation does not replace the assessment of a potential adverse reaction. Equally, the PV team should not overlook relevant quality information that could help explain a safety concern or indicate a broader issue affecting other consumers.
Sponsors should define how the functions communicate, how records are linked and how potentially significant safety or quality issues are escalated for further assessment and regulatory action where required.
8. Training Must Extend Beyond the PV Team
A sponsor may have a well-written PV procedure and an experienced external PV provider, yet still have a significant gap if employees do not know what to do when they receive safety information.
Appropriate training should extend to employees whose roles could bring them into contact with potential adverse events. Depending on the organisation, this may include:
Customer service and complaints teams
Sales and marketing employees
Medical, regulatory and quality personnel
Warehouse and distribution teams
Social media and digital marketing teams
Relevant contractors, distributors and outsourced service providers
Training should be proportionate to each person’s role. Employees do not need to become PV specialists, but they should understand what may constitute a potential adverse event, how to capture information and where to escalate it.
Training should also address practical scenarios rather than relying exclusively on definitions and procedural text.
For example, employees could be asked how they would handle a customer who reports a rash but insists that they are only seeking a refund, or a social media comment that mentions a symptom without providing the customer’s identity.
These scenarios help test whether employees can apply the procedure in realistic situations.
Sponsors should retain training records and periodically assess whether the process is working as intended. Where contractors or distributors are involved, the sponsor should also establish how their understanding of relevant PV requirements is confirmed.
9. A Practical Checklist for Sponsors
Sponsors can use the following checklist to review their current arrangements.
Have all relevant internal departments and external parties been identified as potential sources of safety information?
Is there a documented process for recognising and escalating potential adverse events?
Do employees know where and how to forward safety information?
Is the date of first receipt recorded and traceable?
Are original communications preserved where appropriate?
Are incomplete reports documented and assessed rather than automatically dismissed?
Are serious adverse reactions assessed against the applicable Australian reporting requirements and timeframes?
Are social media and other relevant digital channels addressed in the sponsor’s procedures?
Are potential safety and quality issues communicated between the relevant functions?
Have employees and relevant contractors received appropriate training?
Are transfers of safety information between departments and external providers periodically checked or reconciled?
Can the sponsor demonstrate that information received outside the PV function is captured and handled appropriately?
If several of these questions cannot be answered confidently, the sponsor may need to review its procedures, training arrangements and information flows.
Conclusion
An effective pharmacovigilance system depends on more than having a procedure, a safety database or an external PV provider. It depends on the sponsor’s ability to recognise and manage safety information wherever it originates.
For sponsors of Australian listed medicines, the risk often lies in the gap between the initial receipt of information and its assessment by the responsible PV function.
A customer complaint may appear routine. A social media comment may be brief. A distributor may use a different reporting process. None of these circumstances should create a blind spot in the sponsor’s safety monitoring arrangements.
The objective is to establish a system in which potential adverse events are recognised, documented, escalated and assessed consistently, with clear responsibilities and a traceable record of the actions taken.
PharmaSpectrum supports sponsors with Australian pharmacovigilance requirements, including PV procedures, staff training, case triage and ongoing PV support. If your organisation needs to review how safety information is collected and managed, a practical assessment of your existing processes is a useful place to start.
Regulatory note: This article provides general information and is not a substitute for reviewing the current TGA requirements applicable to your products and circumstances.
