Medical Information & Inquiry Handling
Handling enquiries about the product: scientific responses, enquiry management, escalating anything that is actually a safety report, trend signals, content control, and the interfaces to safety and quality. Medical information is a high-volume front door through which adverse events and complaints arrive disguised as questions — and the enquiry pattern itself is a signal, since a spike in questions about administration often precedes reported use errors.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 20 LINKSThe enquiry desk is a safety intake wearing a service uniform: every call is a potential adverse event or product complaint, and whether it is recognised as one depends on people hired to be helpful.
06 · QUALITY MATURITY — MEDICAL INFORMATION & INQUIRY HANDLING, REACTIVE TO ADAPTIVE
Enquiries are answered from product knowledge and experience. Whether any of them were reportable is unknown.
Approved response documents exist and adverse-event referral is in the procedure, but recognition depends on the individual and is not measured.
Every contact is screened against adverse-event and complaint criteria, referral is timed from first contact, and responses stay within approved information.
Enquiry patterns are analysed as a signal source in their own right, so a rise in one question reaches the people who could act on it.
The desk is treated as a listening post: what patients and prescribers ask changes labelling, education and sometimes the product.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 4
Derived from the 4 standards SPEQ maps to this subject, across 4 regulatory bodies: EMA, ICH, FDA, EC.
RECORDS & OBJECTIVE EVIDENCE
- Screening criteria applied to every contact for adverse events and complaints
- Referral records with timing from first contact
- Approved response documents, with their review and approval status
- Training and competence records for enquiry handlers on recognition
- Analysis of enquiry patterns, and where it fed signal detection or labelling
COMMON INSPECTION FINDINGS
- Contacts closed as enquiries that met adverse-event criteria on their face
- Referral timing measured from recognition rather than from first contact
- Responses given outside approved product information
- Enquiry volumes reported without any analysis of what is being asked
- Handlers trained on the product but not on what makes a contact reportable
Every contact is a potential safety report
A caller asking whether a rash is normal has reported an adverse event, whether or not they framed it that way. Pharmacovigilance obligations attach to the information, not to the channel it arrived through, and the clock starts at the point the organisation became aware — which is when the call was answered, not when someone recognised what it was.
This makes recognition training the load-bearing control, and it is training in a specific skill rather than general awareness: identifying the four elements of a valid case in unstructured conversation, and knowing that a possible product quality complaint and a possible adverse event can both be present in the same sentence. Under-recognition is the failure that produces late reporting, and late reporting is one of the most consistently cited pharmacovigilance findings.
Responses bounded by the authorisation
A medical information response is scientific communication and is bounded by the same authorisation that bounds promotion. Answering an unsolicited question about off-label use is permitted in defined circumstances and is a narrow path: the enquiry must be genuinely unsolicited, the response balanced and non-promotional, and the interaction documented so the distinction can be shown later.
The risk is not usually deliberate. It is a well-informed responder answering helpfully and drifting past what the label supports, in a conversation nobody else hears. Approved response documents, controlled and version-managed, exist for exactly this reason — and their value depends on responders using them rather than answering from knowledge.
The enquiry pattern is intelligence nobody reads
Medical information sits on a data stream almost no organisation analyses: what people are confused about, in what volume, changing over time. A rise in questions about reconstitution, a cluster about a particular device step, a new pattern of questions from a specific region — each is early evidence about how the product is being used and where it is being misunderstood.
These precede the outcomes that eventually appear as adverse events, complaints and use errors, often by months. Treating enquiry volume as an operational metric — average handling time, first-contact resolution — and never as a signal source discards the earliest available warning about a product in the market.
SPEQ interpretation — the handoff is where cases are lost
Medical information, pharmacovigilance and quality complaints are usually three systems with three owners, and a single contact can generate obligations in all three. The transfer between them is where cases are delayed or lost — a case forwarded by email and not acknowledged, a complaint noted in the enquiry record but never raised in the quality system, an adverse event captured in a summary rather than as a case.
Reconciliation across the three is the control that finds those losses, and it has to be periodic and two-way: not only whether everything medical information sent was received, but whether everything that should have been sent was. The second direction is the one that finds under-recognition, and it is the one almost never performed.
FREQUENTLY ASKED
When does the pharmacovigilance clock start on a medical information call?
When the organisation became aware — which is when the call was answered, not when someone later recognised it as a case. Obligations attach to the information rather than to the channel, which is why recognition training for responders is the load-bearing control and under-recognition is what produces late reporting.
Can medical information answer an off-label question?
In defined circumstances and along a narrow path: the enquiry must be genuinely unsolicited, the response balanced and non-promotional, and the interaction documented so the distinction can be demonstrated afterwards. The usual risk is not deliberate promotion but a well-informed responder drifting past the label while being helpful.
Why is enquiry volume worth analysing as a signal?
Because it shows what people are confused about, in what volume, and how that is changing — often months before the corresponding adverse events, complaints or use errors appear. A rise in questions about reconstitution or a cluster around a device step is early evidence, and treating enquiry data only as an operational metric discards it.
Where do cases get lost between medical information, safety and quality?
In the handoffs. A case forwarded and not acknowledged, a complaint noted in an enquiry record but never raised in the quality system, an adverse event captured as a summary rather than a case. Two-way periodic reconciliation is the control — and the direction that checks whether everything that should have been sent was sent is the one that finds under-recognition.