Skip to content
Free previewYou are reading 1 of 36 lessons, in the same interface members use. Everything else unlocks with full access.Get full access · $150

1.1.1 - Case Workflow and Role Boundaries

Case workflow and role boundaries

Drug Safety Foundations | Roles and Controlled Practice

Individual case safety report processing turns incoming safety information into a traceable, assessed record that can support reporting and continuing safety evaluation. Your task is to move information accurately through authorised steps, recognise decisions outside your authority, and preserve evidence of what happened.

What you will learn

  • Map receipt, validation, triage, duplicate screening, entry, assessment, coding, narrative, review, submission, follow-up, and closure to controlled workflow responsibilities. Mapping: Pharmacovigilance foundations → case workflow.
  • Distinguish processor, quality reviewer, medical reviewer, sponsor, marketing authorisation holder, and service-provider responsibilities. Mapping: Pharmacovigilance foundations → role boundaries.
  • Choose a documented escalation or handoff when clinical judgment, product routing, or reportability exceeds assigned authority. Mapping: Pharmacovigilance foundations → controlled practice.
  • Explain how individual cases contribute to signals, aggregate reporting, and risk management without treating one report as proof of causation. Mapping: Pharmacovigilance foundations → downstream safety use.
Estimated time
20–25 minutes.
Blueprint mapping
Pharmacovigilance foundations → accountable case handling and appropriate role boundaries; blueprint anchor bp.d1.t1. A percentage weight is not supplied.
Current-as-of baseline
November 5, 2026, using the supplied course blueprint. This is operational training for an entry-level Drug Safety Associate / ICSR Case Processor.
Prerequisites
None.
Key outputs
Choose recording versus inferring; choose routine processing versus urgent escalation; distinguish assigned operational work from accountable oversight; distinguish a completed handoff from a merely sent message.
WHY

Why it matters

  • A report may pass through several people and organisations. Without clear ownership, an urgent issue can remain visible but unacted on.
  • Accurate processing requires both action and restraint: capture available evidence promptly, but do not invent diagnoses, causality conclusions, or missing facts.
  • The supplied blueprint identifies amended EU requirements for accountable subcontracting, information integrity, and traceable records. Outsourcing makes documented responsibilities especially important.
  • As of the course baseline, the blueprint states that covered FDA postmarketing electronic ICSRs submitted through ESG NextGen have required E2B(R3) since October 1, 2026. Technical submission belongs within the workflow, alongside assessment, review, and receipt confirmation.
Where things stand: The supplied blueprint names Commission Implementing Regulation (EU) No 520/2012, as amended, as a basis for accountable subcontracting and records. It also distinguishes US and EU postmarketing and investigational reporting frameworks. This lesson establishes who handles a decision; the next topic, Regulatory Scope and Current Requirements, develops which framework applies. A job title alone does not establish approval authority.
KEY TERMS

Key Terms & Must-Know Facts

Table 1. Workflow vocabulary and practical meaning
TermOperational meaning
Individual case safety report, or ICSRA structured record of safety information concerning an individual patient and a suspected reaction or event, processed under applicable requirements.
ReceiptArrival of information through a recognised intake channel; preserve evidence of when and how it arrived.
ValidationCheck for the minimum information needed for a valid case: identifiable patient, identifiable reporter, suspected reaction, and suspect product.
TriageInitial prioritisation and routing based on available information, urgency, and the applicable procedure.
Duplicate screeningComparison with existing records to identify information that may concern the same case.
Case processorA person performing assigned operational case tasks within training, access, and delegated authority.
Quality reviewerA person checking specified aspects of case accuracy, completeness, consistency, and procedural compliance.
Medical reviewerAn authorised person addressing medical assessment questions within the organisation's controlled process.
SponsorThe accountable party for relevant investigational safety responsibilities in the clinical-trial context.
Marketing authorisation holder, or MAHThe authorisation holder with applicable post-authorisation pharmacovigilance responsibilities; US requirements use terms such as applicant.
Service providerA contracted organisation performing specified tasks under defined responsibilities and oversight.
ClosureA documented workflow state reached under defined criteria; later relevant information can require further processing.

Must-know facts:

  • The workflow is iterative: new information can change an earlier assessment, narrative, or reporting decision.
  • Validation, seriousness assessment, causality assessment, and reportability assessment answer different questions.
  • Incomplete information still needs documented handling; it is not permission to discard an incoming report.
  • Receipt, handoff, review, transmission, and closure are distinct milestones with different evidence.
  • Assigned work must remain within controlled procedures and documented competence.
  • Potential duplicates require reconciliation; a shared product name alone does not establish duplication.
  • Uncertainty that can affect urgency or routing requires timely escalation under the applicable procedure.
CORE

Core content

1.1.1.1 1. Locate the case in the workflow

A Explanation

Decision conflict: Should you complete all available data entry first, or act on an urgent routing concern while preserving the incoming information? Choose timely, documented triage; reject a rigid sequence that makes completion of every field a prerequisite for escalation.

WHY THIS IS TESTED: Reliable case handling depends on recognising both the next workflow step and work that must proceed in parallel. A tidy database record does not compensate for an unattended urgent issue.

A practical sequence is receipt → validation and triage → duplicate screening and entry → assessment, coding, and narrative → review and applicable submission → follow-up and closure. These are functional stages, not universal job titles or an inflexible order. Duplicate searches can be repeated, follow-up can begin early, and urgent review can occur before a narrative is complete. See Fig 1.

Fig 1. The case lifecycle includes return paths
Exam takeaway: New information can reopen earlier processing steps.
flowchart TD; A[Receipt and source preservation] --> B[Validation and triage]; B --> C[Duplicate screening and entry]; C --> D[Assessment coding and narrative]; D --> E[Review and applicable submission]; E --> F[Follow-up and closure decision]; F -->|New information| B;

At receipt, preserve the source and arrival evidence. At validation, identify whether the minimum case elements are present. At triage, recognise concerns needing priority handling. During entry, coding, and narrative drafting, represent the source faithfully. During review, resolve or explicitly route material discrepancies. During submission, retain evidence of delivery status. At closure, apply the procedure rather than assuming that no recent response means no further work remains.

Incoming information becomes a traceable record
Exam takeaway: Preserve the original source while creating the working case record.
{"prompt":"Educational semi-flat illustration on white background, cool blue and gray with teal accent: a drug safety associate receives a fictional email safety report and creates a case record; show the original email retained in a source folder and an arrow to a separate structured record, with concise labels Source preserved, Receipt recorded, Case created; no real patient identifiers, no decorative objects, generous margins.","caption":"Incoming information becomes a traceable record","size":"1024x1024"}
Validity and urgency are separate checks
Exam takeaway: Missing case information does not remove the need to evaluate an urgent concern.
flowchart TD; A[Incoming safety information] --> B{Minimum case elements present?}; B -->|Yes| C[Proceed as valid case under procedure]; B -->|No| D[Document gaps and seek information]; A --> E{Urgent concern identified?}; E -->|Yes| F[Use urgent escalation route]; E -->|No| G[Continue assigned triage];
Locate and act
Exam takeaway: Recognise the workflow stage and act on urgency without waiting for every field.
1. Preserve receipt evidence
2. Check validity and urgency
3. Locate the current stage
4. Perform or route the next action

B Worked example

A nurse emails a report about a 72-year-old patient with diabetes and chronic kidney disease who was admitted after starting a medicine. The attached laboratory sheet includes mildly elevated glucose. The email says the full discharge summary will arrive next week, and an intake colleague suggests holding the message until then.

  1. Identify the task: Decide how to handle the initial information, not whether the medicine caused the admission.
  2. Extract key facts: There is a reported hospital admission, an initial source, and promised follow-up. The processor must inspect the actual report for the four minimum elements.
  3. Apply the rule: Preserve receipt, perform validation and triage, and route the potentially serious information under the procedure.
  4. Eliminate distractors: The glucose result does not establish the cause; the promised summary does not justify leaving the initial report unprocessed.
  5. Verify: Record the pending document, assigned follow-up action, and any urgent handoff.

C Exam trap

Wrong answer: Wait for the discharge summary before starting intake. Why tempting: A complete document seems easier to process accurately. Single eliminating clue: Safety information has already been received.

D Checkpoint MCQ

A case is awaiting a missing treatment date when new information suggests a potentially urgent safety concern. What is the most appropriate next step?

  1. A. Complete the date field before changing the case priority.
  2. B. Preserve the new information and use the applicable escalation route while continuing authorised processing.
  3. C. Assign a final causality conclusion to establish whether escalation is justified.
  4. D. Close the initial version and wait for a complete replacement report.

Answer: B. A is tempting because complete chronology improves quality, but it creates an inappropriate dependency. B is correct because urgency can require action before completeness. C is tempting because causality may affect later assessment, but final medical judgment is not a prerequisite for routing a concern. D is tempting because version separation appears orderly, but it can sever continuity and leave received information unattended.

If you missed this: Review Locate the case in the workflow — focus on parallel triage and data completion.

1.1.1.2 2. Separate task performance from accountable responsibility

A Explanation

Decision conflict: Does the organisation performing the task automatically become the party accountable for all associated obligations? Choose documented allocation and oversight; reject the assumption that outsourcing transfers every responsibility.

WHY THIS IS TESTED: A processor must know both who does the next action and who owns the unresolved decision. The same workflow can involve a service provider, sponsor or MAH, quality reviewer, and medical reviewer.

The supplied blueprint identifies accountable subcontracting and record integrity under the amended EU pharmacovigilance framework. Operationally, consult the applicable procedure and agreement for responsibilities, review requirements, transfer arrangements, escalation contacts, and evidence of completion. A contract can allocate activities; the presence of a provider does not itself establish that the sponsor's or MAH's applicable responsibilities have disappeared. See Fig 2.

Table 2. Typical roles and limits of inference
RoleTypical contribution within assigned authorityDo not infer from the title alone
Case processorExtract, enter, reconcile, code, draft, follow up, and route case information.Authority to approve every medical or reporting decision.
Quality reviewerCheck specified source alignment, completeness, consistency, and procedural requirements.Authority to replace a required medical review.
Medical reviewerAddress medical interpretation and assessment questions assigned to that role.Ownership of every administrative or transmission task.
SponsorOversee relevant investigational safety responsibilities and delegated activities.That all serious trial events automatically qualify for expedited reporting.
MAH or relevant applicantMeet applicable post-authorisation or postmarketing responsibilities and oversee contracted work.That a provider contract removes applicable accountability.
Service providerPerform contracted activities with traceable outputs and defined handoffs.Unlimited authority beyond the agreement and controlled procedures.
Fig 2. Delegated work remains connected to oversight
Exam takeaway: A service-provider task needs a defined output and an accountable oversight route.
flowchart TD; A[Sponsor or MAH oversight] --> B[Defined agreement and procedure]; B --> C[Provider performs assigned tasks]; C --> D[Traceable outputs and exceptions]; D --> E[Authorised review and decisions]; E --> A;
Handoff with ownership versus handoff by assumption
Exam takeaway: A sent case needs a defined receiving role and completion evidence.
{"prompt":"Two-panel educational comparison for pharmacovigilance operations, white background, blue gray teal palette: left panel labeled Defined handoff shows provider handing a fictional case folder with case ID, pending question, recipient role, and receipt confirmation to sponsor operations; right panel labeled Ownership unclear shows a folder placed in a shared inbox with a question mark and no assigned recipient; use no patient identifiers and no figure numbers.","caption":"Handoff with ownership versus handoff by assumption","size":"1024x1024"}
Confirm responsibility before transfer
Exam takeaway: An assigned task and its review route must both be identifiable.
1. Identify the task
2. Check the assigned role
3. Identify required review
4. Document transfer and ownership

B Worked example

A contracted processor handles a report about a 58-year-old patient with hypertension and asthma. A note mentions a normal oxygen saturation, while the reporter describes an unexpected admission. The provider agreement includes case preparation, but the processor cannot locate authority for the disputed medical assessment. A colleague says, 'We built the case, so we should approve it.'

  1. Identify the task: Resolve ownership of the assessment decision.
  2. Extract key facts: Case preparation is assigned; approval authority for this question is not established.
  3. Apply the rule: Continue authorised preparation and route the unresolved assessment through the defined sponsor or MAH review contact.
  4. Eliminate distractors: Normal oxygen saturation does not settle the admission's interpretation; preparation does not imply approval authority.
  5. Verify: Document the precise question, responsible recipient, urgency, and handoff evidence.

C Exam trap

Wrong answer: Treat the vendor as the sole accountable party because it operates the database. Why tempting: Daily control of the system looks like ownership of the entire process. Single eliminating clue: The task is contracted on behalf of a sponsor or MAH with applicable responsibilities.

D Checkpoint MCQ

A provider drafts a case narrative under contract. Which fact best establishes who may approve a disputed medical interpretation?

  1. A. The organisation that first entered the case.
  2. B. The person who has edited the most case versions.
  3. C. The applicable controlled responsibility and authorisation arrangements.
  4. D. The team with access to the submission gateway.

Answer: C. A is tempting because the first processor knows the source, but entry does not establish approval authority. B is tempting because familiarity supports review, but editing history is not authorisation. C is correct because controlled arrangements determine the authorised decision route. D is tempting because submission access is operationally important, but transmission access does not establish medical authority.

If you missed this: Review Separate task performance from accountable responsibility — focus on documented authority rather than system access.
Quick Recall:
  • Does completing a narrative establish authority to approve its medical conclusions? No.
  • Missing information and urgent concern can coexist: true or false? True.
  • A transfer record should identify the receiving ______. Responsible role or owner.

1.1.1.3 3. Record evidence and route decisions beyond your authority

A Explanation

Decision conflict: Should you fill an uncertain field with a plausible inference or preserve the uncertainty and obtain authorised assessment? Choose source-based documentation and targeted routing. Reject unsupported certainty.

WHY THIS IS TESTED: Entry-level processing involves assessment support, but that does not authorise independent diagnosis, treatment advice, complex clinical adjudication, or unsupported regulatory conclusions.

Separate three layers: what the source states, what structured fields can represent, and what requires an authorised decision. A processor may identify a reported seriousness criterion, prepare reference information, or flag a possible reporting issue according to training. A processor must not turn an ambiguous symptom into a confirmed diagnosis or use an unresolved medical interpretation to suppress or delay appropriate escalation. See Fig 3.

Table 3. Similar-looking actions with different authority requirements
SituationAppropriate operational actionBoundary to recognise
Reporter describes a hospital admission.Capture the statement and assess or route seriousness under the procedure.Do not invent the clinical cause of admission.
Two reports share product and age.Screen and compare available identifiers and chronology.Do not delete a potential duplicate solely from partial similarity.
Source says 'possible allergic reaction'.Preserve the qualification and use supported coding principles.Do not replace uncertainty with a confirmed diagnosis.
Product complaint also mentions a reaction.Use relevant safety and product-quality routing, preserving linkage.Do not assume quality routing replaces safety handling.
Unclear expedited-reporting applicability.Document the uncertainty and seek timely authorised determination.Do not apply one jurisdiction's rule to every case.
Fig 3. Choose supported action over unsupported inference
Exam takeaway: A plausible explanation is not a documented source fact.
flowchart TD; A[Proposed case statement or action] --> B{Supported by source and assigned authority?}; B -->|Yes| C[Record or act under procedure]; B -->|No| D[Preserve source wording and uncertainty]; D --> E[Ask targeted question or escalate]; E --> F[Record authorised resolution];
Reported symptom versus invented diagnosis
Exam takeaway: Keep the source's level of certainty visible.
{"prompt":"Side-by-side pharmacovigilance educational illustration, white background blue gray teal: a fictional reporter note reads Rash after medicine; left panel labeled Preserve evidence shows a processor copying the qualified report into a case and flagging a medical question; right panel labeled Unsupported inference shows a diagnosis stamp beside a question mark, with a restrained caution symbol; no real identifiers, no treatment advice, no figure number.","caption":"Reported symptom versus invented diagnosis","size":"1024x1024"}
One source can require two coordinated routes
Exam takeaway: Product-quality handling and safety handling may both be needed.
{"prompt":"Clean educational diagram illustration for drug safety case processors: a fictional report states Damaged tablet packaging and patient felt unwell; one source document branches to a Safety case folder and a Product quality folder, both retain a shared reference label; show a processor coordinating the two routes, white background cool blue gray teal, no manufacturing investigation details, no figure numbers.","caption":"One source can require two coordinated routes","size":"1024x1024"}
Prepare a useful escalation
Exam takeaway: Escalate a specific question with supporting evidence and an identified recipient.
1. State the unresolved question
2. Attach relevant source evidence
3. Identify urgency and authorised recipient
4. Track the response and action

B Worked example

A 46-year-old patient with migraine and eczema reports a rash after taking a medicine from a damaged blister pack. A recent creatinine value is within the laboratory reference range. The reporter asks whether to stop treatment. A coworker suggests documenting a confirmed allergy because the timing appears persuasive.

  1. Identify the task: Capture and route safety information, a product complaint, and a treatment question.
  2. Extract key facts: The source reports rash and packaging damage; it does not establish a confirmed allergy.
  3. Apply the rule: Preserve the reported wording, use applicable safety and quality routes, and direct the treatment question through the approved clinical-response process.
  4. Eliminate distractors: The normal creatinine does not establish causality; timing alone does not authorise a confirmed diagnosis.
  5. Verify: Keep linked records and document who owns each unresolved question.

C Exam trap

Wrong answer: Replace a vague reported event with the most clinically likely diagnosis. Why tempting: A diagnostic label appears more precise and easier to code. Single eliminating clue: The diagnosis is absent from the source.

D Checkpoint MCQ

A source states 'possible medication-related fainting'; no diagnosis or medical causality assessment is available. What is the best processing approach?

  1. A. Record a confirmed drug-induced diagnosis to avoid ambiguity.
  2. B. Remove the event until a medical reviewer confirms causality.
  3. C. Preserve the reported uncertainty and route assessment questions under the procedure.
  4. D. Record the event as unrelated because the source uses 'possible'.

Answer: C. A is tempting because it creates a definite label, but it exceeds the evidence. B is tempting because confirmation would simplify assessment, but the received event still needs handling. C is correct because source fidelity and authorised assessment can coexist. D is tempting because uncertainty sounds weak, but uncertain attribution does not establish absence of a relationship.

If you missed this: Review Record evidence and route decisions beyond your authority — focus on preserving uncertainty.

1.1.1.4 4. Maintain continuity from review to downstream safety use

A Explanation

Decision conflict: Is a case finished when someone sends it onward, or when the required next state is evidenced and outstanding actions are controlled? Choose verified workflow completion; reject completion by assumption.

WHY THIS IS TESTED: An accurate case can still fail operationally if a review request, transmission rejection, follow-up item, or correction loses its owner.

Review checks and electronic delivery checks serve different purposes. A quality review can verify source alignment without proving gateway acceptance. A technical acknowledgement can establish a transmission outcome without proving that the clinical content is correct. Follow-up must remain linked to the existing case and processed through the applicable version-control process. See Fig 4.

Fig 4. Content review and delivery verification answer different questions
Exam takeaway: A successful transmission does not substitute for case-quality review.
flowchart TD; A[Prepared case] --> B[Required content review]; B --> C[Authorised reporting action]; C --> D[Electronic transmission]; D --> E{Delivery outcome}; E -->|Accepted under applicable rules| F[Record evidence and next actions]; E -->|Rejected or unresolved| G[Assign correction and resubmission]; G --> B;

Individual cases also become inputs to wider safety work. Consistent coding supports retrieval; reliable chronology supports interpretation; traceable follow-up distinguishes evolving information from contradictory records. Authorised teams evaluate accumulated evidence for signals, aggregate reports, and risk management. One case can warrant attention, but an entry-level processor does not independently declare a product safe or unsafe. See Fig 5.

Fig 5. Individual cases support broader safety evaluation
Exam takeaway: Case quality supports downstream evaluation without replacing expert judgment.
flowchart TD; A[Traceable individual cases] --> B[Consistent searchable case data]; B --> C[Signal evaluation]; B --> D[Aggregate reporting]; B --> E[Risk management activities]; C --> F[Authorised evidence assessment]; D --> F; E --> F;
Accepted transmission and unresolved follow-up can coexist
Exam takeaway: Delivery status and case follow-up status are separate workflow facts.
{"prompt":"Educational pharmacovigilance workstation illustration on white background, blue gray teal palette: a fictional case status card has two distinct rows, Transmission accepted with a check symbol and Follow-up pending with a clock symbol; beside it are linked Initial report and Follow-up folders carrying the same fictional case reference; no real identifiers, no interface branding, no figure numbers.","caption":"Accepted transmission and unresolved follow-up can coexist","size":"1024x1024"}
Case evidence feeds authorised safety evaluation
Exam takeaway: A processor prepares dependable evidence for teams evaluating the wider safety picture.
{"prompt":"Professional educational illustration: a drug safety case processor checks three fictional case folders for source links, consistent coding, and version history, then passes a compiled evidence tray to an authorised safety evaluation team; the team has three concise labeled work areas Signal review, Aggregate report, Risk management; white background cool blue gray teal, no numerical risk claims, no figure numbers.","caption":"Case evidence feeds authorised safety evaluation","size":"1024x1024"}
Verify the next state
Exam takeaway: Record the outcome and retain ownership of unresolved work.
1. Confirm required review
2. Perform assigned handoff or transmission
3. Check the outcome evidence
4. Assign unresolved actions
5. Apply closure criteria

B Worked example

A case concerns a 65-year-old patient with heart failure and osteoarthritis. The source includes a stable haemoglobin value. A processor sends an electronic report, then receives a rejection message. A colleague says the case can be closed because the narrative passed quality review and the file was transmitted before the internal target.

  1. Identify the task: Determine the next action after a rejection.
  2. Extract key facts: Content review occurred, but the delivery outcome is unsuccessful or unresolved.
  3. Apply the rule: Retain the rejection, assign correction and resubmission under the procedure, and escalate any timing concern.
  4. Eliminate distractors: Stable haemoglobin is unrelated to delivery status; prior quality review does not reverse a rejection.
  5. Verify: Track the corrected transmission outcome and any remaining follow-up before applying closure criteria.

C Exam trap

Wrong answer: Treat an outgoing timestamp as proof of completed delivery. Why tempting: Sending is a visible milestone that feels final. Single eliminating clue: A rejection or unresolved acknowledgement remains.

D Checkpoint MCQ

Which statement best describes how a case processor contributes to signal evaluation?

  1. A. A processor establishes the signal by coding the event.
  2. B. A processor supplies traceable, consistent case data for authorised evaluation.
  3. C. A processor excludes uncertain reports so downstream reviewers receive only confirmed reactions.
  4. D. A processor substitutes a case narrative for the wider evidence assessment.

Answer: B. A is tempting because coding supports case retrieval, but coding does not establish a signal. B is correct because dependable case evidence supports later evaluation. C is tempting because a cleaner dataset seems easier to interpret, but uncertainty is not a reason to suppress received safety information. D is tempting because a narrative summarises evidence, but it cannot replace evaluation of the broader evidence base.

If you missed this: Review Maintain continuity from review to downstream safety use — focus on evidence preparation versus safety conclusion.
Quick Recall:
  • Does gateway acceptance establish medical correctness? No.
  • What connects a follow-up to earlier information? The controlled case linkage and version history.
  • Who resolves a complex medical interpretation? The authorised reviewer identified by the procedure.
TRAPS

Exam Traps & Differentiators

Common traps & distractors:
  • 'The reviewer will notice it.' Tempting because review is a safety net. Eliminating clue: an urgent issue is already recognised and needs an assigned action.
  • 'The product complaint belongs only to quality.' Tempting because the source emphasises a defect. Eliminating clue: the same source also contains patient safety information.
  • 'A familiar product and matching age prove a duplicate.' Tempting because the overlap is easy to see. Eliminating clue: the available information does not yet establish the same patient and occurrence.
  • 'Closed means permanently finished.' Tempting because closure sounds irreversible. Eliminating clue: relevant new information has arrived.
Table 4. Looks similar but requires a different decision
PairDiscriminating questionPractical consequence
Validation versus reportabilityAre you checking minimum case elements or determining an applicable reporting obligation?A valid case is not automatically reportable through every route.
Quality review versus medical reviewIs the unresolved issue source consistency or clinical interpretation?Use the review role authorised for that question.
Handoff sent versus handoff controlledIs there a defined receiving owner and required transfer evidence?Do not leave unresolved work in an unowned queue.
New case versus follow-upDoes the information concern an existing case after reconciliation?Preserve continuity instead of creating disconnected records.

If the scenario says...

  • 'Full report to follow' → preserve and process what has already arrived.
  • 'Outside my assigned authority' → prepare a specific, timely escalation.
  • 'Vendor handles everything' → inspect the responsibility and oversight arrangements.
  • 'New information after closure' → apply the controlled update process.
  • 'Transmission rejected' → assign correction and verify the next delivery outcome.
Open questions and what comes next: The supplied source pack does not specify employer-specific approval matrices, escalation contacts, or closure criteria. Use your organisation's current controlled documents for these details. No future proposed rule is established by this source pack. Continue with Regulatory Scope and Current Requirements for framework selection, then Personnel Competence and Urgent Escalation for training and urgency arrangements.
Review connection: Return to Separate task performance from accountable responsibility whenever a scenario confuses access, task ownership, and decision authority.
ALGO

Algorithm / Approach

Use this approach whenever a case arrives, changes, or reaches a handoff. It supports workflow decisions; it does not replace the applicable reporting procedure.

1. Preserve: Retain the incoming source, receipt evidence, and existing case reference if available.
2. Locate: Identify validity status, urgency, possible duplication, and current workflow stage.
3. Bound: Separate supported facts from unresolved interpretation; check your assigned authority.
4. Act or route: Perform authorised work and direct urgent or out-of-scope questions to the defined owner.
5. Verify: Record the review, handoff, or delivery outcome and control outstanding follow-up before closure.
QUIZ

Self-check quiz

Choose the single most appropriate answer for each situation.

1. An intake report appears to lack an identifiable reporter but describes a potentially urgent patient event. What should the processor do first within assigned procedures?

  1. A. Delete it because it is not yet a valid ICSR.
  2. B. Preserve it, document the missing element, seek clarification, and route the urgent concern.
  3. C. Enter a presumed reporter identity from a similar case.
  4. D. Mark it reportable in every jurisdiction to compensate for the missing detail.

2. A provider contract assigns data entry and narrative drafting. A disputed clinical interpretation remains. Which next step best respects role boundaries?

  1. A. Let the processor approve it because the provider created the record.
  2. B. Let the submission operator decide because that person sends the report.
  3. C. Route the specific question to the authorised medical assessment role while maintaining processing continuity.
  4. D. Treat the reporter's uncertain wording as a definitive medical conclusion.

3. A postmarketing case has passed quality review, but electronic transmission returns a rejection. Which statement is most accurate?

  1. A. Quality approval establishes successful regulatory delivery.
  2. B. An outgoing timestamp makes the rejection irrelevant.
  3. C. Correction can wait until the next routine aggregate report.
  4. D. Delivery remains unresolved and needs controlled correction, resubmission, and outcome tracking.

4. New outcome information arrives for a previously closed case and appears to concern the same patient and event. What is the best approach?

  1. A. Reconcile linkage and process a controlled update to the existing case.
  2. B. Create an unrelated case because closure prevents further changes.
  3. C. Replace the old source record so only the newest information remains.
  4. D. Retain the message without reassessment because the initial case was completed.

5. Why does careful event coding and source reconciliation matter beyond the individual case?

  1. A. It allows the processor to determine product safety from one complete report.
  2. B. It removes the need for medical assessment if structured fields are complete.
  3. C. It supplies dependable evidence for authorised signal, aggregate, and risk-management work.
  4. D. It converts every temporal association into a confirmed adverse reaction.
ANSWERS

Answer key & explanations

1. B — Preserve, clarify, and route.

  • A: Tempting because the minimum elements determine validity; wrong because incomplete intake still requires documented handling.
  • B: Correct because it addresses the information gap without abandoning an urgent concern.
  • C: Tempting because a similar record may offer a lead; wrong because presumed identity would introduce unsupported information.
  • D: Tempting because broad reporting sounds cautious; wrong because reportability requires the applicable framework and authorised assessment.
If you missed this: Review Locate the case in the workflow — focus on incomplete information versus urgent action.

2. C — Use the authorised assessment route.

  • A: Tempting because the processor knows the record; wrong because preparation authority does not establish medical approval authority.
  • B: Tempting because the operator controls delivery; wrong because technical access does not establish clinical judgment authority.
  • C: Correct because it directs the decision to the assigned role while preserving continuity.
  • D: Tempting because source language should be respected; wrong because respecting uncertainty means preserving it, not upgrading it.
If you missed this: Review Separate task performance from accountable responsibility — focus on the scope of delegated authority.

3. D — Resolve and verify delivery.

  • A: Tempting because review is a major milestone; wrong because content approval and delivery are separate.
  • B: Tempting because the timestamp proves an attempt; wrong because an attempted transmission does not resolve a rejection.
  • C: Tempting because aggregate reporting is another safety output; wrong because it is not the default substitute for resolving an individual delivery failure.
  • D: Correct because the rejection requires assigned action and evidence of the subsequent outcome.
If you missed this: Review Maintain continuity from review to downstream safety use — focus on attempted transmission versus evidenced delivery outcome.

4. A — Reconcile and update.

  • A: Correct because relevant follow-up belongs in a controlled, linked case history after reconciliation.
  • B: Tempting because closed cases appear final; wrong because closure does not prohibit processing later relevant information.
  • C: Tempting because the newest source may be more complete; wrong because replacing history undermines traceability.
  • D: Tempting because retention preserves the message; wrong because passive storage does not address the need for case reassessment or updating.
If you missed this: Review Maintain continuity from review to downstream safety use — focus on linked follow-up and version history.

5. C — Support wider evidence evaluation.

  • A: Tempting because a complete case can be informative; wrong because one report does not establish overall product safety.
  • B: Tempting because complete structured data improve usability; wrong because completeness does not replace authorised medical assessment.
  • C: Correct because dependable individual records support downstream safety activities.
  • D: Tempting because chronology is relevant to assessment; wrong because timing alone does not confirm causation.
If you missed this: Review Record evidence and route decisions beyond your authority — focus on evidence versus conclusion.
RAPID

Rapid review / cheat-sheet

  • Workflow location → ask which action is due now, not merely which field is incomplete.
  • Authority → locate the controlled assignment before approving a disputed decision.
  • Source fidelity → carry qualifications such as 'possible' into the working record.
  • Handoff quality → make the question and receiving owner explicit.
  • Parallel routes → preserve linkage when one source enters safety and quality workflows.
  • Version continuity → retain how the case changed, not only its latest wording.
  • Completion evidence → check the outcome required for the particular workflow milestone.
  • Downstream usefulness → make records retrievable, consistent, and interpretable.

Key points: Preserve evidence; act within authority; make ownership explicit; verify outcomes. These habits apply throughout the remaining course.

Blueprint anchor recap: Pharmacovigilance foundations → case workflow, role boundaries, accountable subcontracting, and contribution of individual cases to wider safety evaluation. Anchor: bp.d1.t1; subject: pharmacovigilance-foundations.

References / further study

The following authoritative instruments are named in the supplied blueprint. They support the operational scope of this lesson; organisation-specific procedures determine local task assignments.

  1. European Commission. Commission Implementing Regulation (EU) No 520/2012. Articles 6 and 11, as amended. Accountable subcontracting and pharmacovigilance records.
  2. United States. Code of Federal Regulations. Title 21, sections 314.80 and 600.80. Approved-drug and biologic postmarketing safety reporting.
  3. United States. Code of Federal Regulations. Title 21, section 312.32. Investigational safety reporting.
End of your free lesson

Keep going with the full Drug Safety and ICSR Case Management Certificate Program

You just studied the way members do, in the same lesson interface. Full access unlocks every lesson, the question bank and flashcards for a full year.

Up next with full access1.1.2 - Regulatory Scope and Current Requirements

One payment per program