Specialist, Pharmacovigilance

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about company mission. That could be "About the role" or maybe "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and decide sections. Content: Intro: "Being on medication is tough enough. We want to make getting it the easy part. Getting prescriptions to patients has become increasingly complex. When things get messy along the prescription journey, pharmaceutical manufacturers rely on us to untangle the process and create a clear path—allowing patients to build trusting relationships with their medication brands. We’re not only committed to taking the pain out of the prescription process, but we’re also devoted to bringing the brightest minds together under one roof. We bring together diverse voices—engineers, pharmacists, customer service veterans, developers, program strategists and more—all with one vision. Each perspective and experience makes ConnectiveRx better than the sum of its parts." That's about company mission. Could be "About the role" or maybe "About ConnectiveRx". Since they said use headings like About the role, Responsibilities, etc. We'll use "About the role" for this intro. Then: "Under direct supervision of the department manager or supervisor, the Specialist, Pharmacovigilance is focused on meeting ConnectiveRx’s obligations for Drug Safety Monitoring and Reporting as required by the pharmaceutical manufacturers we support. The Specialist ensures that ConnectiveRx operates in a constant state of compliance with Pharmacovigilance activities." That's also part of role description; could be part of About the role. Then "Responsibilities" heading with bullet list. Responsibilities list: - Reviews written Adverse Event and Product Quality Complaint reports submitted to the drug manufacturer. - Ensures timely and accurate transcription of data into the ConnectiveRx Quality Management System and that reports meet company and manufacturer requirements and standards. - Conducts quality checks and ensures reports are submitted to the manufacturer as required. - Monitors and audits potential sources of safety information under the guidance of the Manager, Pharmacovigilance. Sources may include recorded calls, claims, faxes, text messages, chat logs, and other records. - Ensures all safety data identified is captured, recorded, and reported in compliance with company SOPs. - Assists Pharmacovigilance teammates with tasks such as periodic reconciliation, records inspection, and internal audit activities. - Supports internal audits and preparation for third-party audits under the supervision of the Manager. - Performs other duties as assigned. We'll put these as

  • . Then "Qualifications" heading with subparts: Education/Degree Requirements, Experience, Knowledge. We can treat Qualifications as a section with bullet list for each subpoint? The instruction: Use
    • for any list of duties/requirements/benefits. So we can list each qualification as bullet. Qualifications content: - Education/Degree Requirements: Associate degree or professional diploma in healthcare, pharmacy, or a medical-related field, or four years of equivalent relevant experience. - Experience: Two to four years of experience in a medical, pharmacy, or healthcare environment (preferably in a call center or claims processing). Medical call center or medical claims experience preferred. Quality Control or Quality Assurance experience is a plus. - Knowledge: Strong reading and verbal comprehension. Proficiency in English required; Spanish or other languages are a plus. Highly proficient in Microsoft Office applications including Word, PowerPoint, SharePoint, and Excel. Ability to clearly and concisely articulate medical and clinical information to manufacturer representatives. We'll put these as bullet list. Then "Skills" heading with bullet list. Skills content: - Strong problem-solving skills with the ability to resolve issues independently or escalate when needed. - Ability to organize and prioritize work across multiple systems to meet reporting deadlines. - Ability to learn and successfully utilize Quality System software. - Accurate transcription of text or audio information. - Effective communication of ideas and concepts. - Responsive, attentive, patient, respectful, and professional with colleagues, leadership, and manufacturer contacts. - Strong analytical skills, results orientation, and attention to detail. Then "Competencies" maybe? The posting includes "Competencies" with sub-bullets: Process Knowledge, Decision Quality, Service Orientation, Consultation Communication. Should we include a Competencies section? The instruction list of possible headings didn't include Competencies, but we can include if there is real content. It says "Prefer a few substantive sections over many thin ones." Could combine Competencies into Skills or Qualifications? But they are distinct. However we could include a Competencies section as

      Competencies

      with bullet list. The instruction didn't forbid other headings; they gave examples but not exclusive. It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical but not exclusive. We'll include Competencies. Then "Compliance Requirements" maybe as a section? Could be part of Qualifications or separate. It's substantive. Could be a section "Compliance". But we might combine into Qualifications? Better to have a separate section "Compliance Requirements". The instruction didn't list Compliance but we can include if real content. Then "Compensation & Benefits" heading with bullet list. Compensation & Benefits content: - This position offers opportunities for a bonus (or commissions), with total compensation varying based on factors such as location, relevant skills, experience, and capabilities. - Employees at ConnectiveRx can access comprehensive benefits, including medical, dental, vision, life, and disability insurance. - The company regularly reviews and updates its health, welfare, and fringe benefit policies to ensure competitive offerings. - Employees may also participate in the company’s 401(k) plan, with employer contributions where applicable. Then "Time-Off & Holidays" heading with bullet list. Time-Off & Holidays content: - ConnectiveRx provides a flexible paid time off (PTO) policy for exempt employees, covering sick days, personal days, and vacations. PTO is determined based on an employee’s first year of service. - Employees also receive eight standard company holidays and three floating holidays annually, with prorations applied in the first year. - The company remains committed to providing competitive benefits and reserves the right to modify employee offerings, including PTO, STO, and holiday policies, in accordance with applicable laws and regulations. Then "Posted Salary Range" maybe as a Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary range: "Posted Salary Range USD $19.51 - USD $25.85 /Hr." So we should include a Pay section with that info. Could be

      Pay

      with

      Posted Salary Range USD $19.51 - USD $25.85 /Hr.

      Schedule: not mentioned, so omit. Travel Or Physical Requirements: "None". That's filler/placeholder? It's a statement "None". According to instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "None" could be considered placeholder? It's a specific answer: Travel Or Physical Requirements None. It's not filler like "not specified". It's a definite answer. Should we include a section? The instruction list didn't include Travel, but we could include a section "Travel Or Physical Requirements". However they said prefer a few substantive sections over many thin ones. This is a thin section. Might be better to omit or fold into a short paragraph under Qualifications? But it's a separate category. Since it's just "None", maybe we can drop it as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. Travel Or Physical Requirements could be considered minor metadata. We'll drop it. Now we need to output HTML fragment only. We'll structure:

      About the role

      Being on medication is tough enough. We want to make getting it the easy part. Getting prescriptions to patients has become increasingly complex. When things get messy along the prescription journey, pharmaceutical manufacturers rely on us to untangle the process and create a clear path—allowing patients to build trusting relationships with their medication brands. We’re not only committed to taking the pain out of the prescription process, but we’re also devoted to bringing the brightest minds together under one roof. We bring together diverse voices—engineers, pharmacists, customer service veterans, developers, program strategists and more—all with one vision. Each perspective and experience makes ConnectiveRx better than the sum of its parts. Under direct supervision of the department manager or supervisor, the Specialist, Pharmacovigilance is focused on meeting ConnectiveRx’s obligations for Drug Safety Monitoring and Reporting as required by the pharmaceutical manufacturers we support. The Specialist ensures that ConnectiveRx operates in a constant state of compliance with Pharmacovigilance activities.

      Responsibilities

      • Reviews written Adverse Event and Product Quality Complaint reports submitted to the drug manufacturer.
      • Ensures timely and accurate transcription of data into the ConnectiveRx Quality Management System and that reports meet company and manufacturer requirements and standards.
      • Conducts quality checks and ensures reports are submitted to the manufacturer as required.
      • Monitors and audits potential sources of safety information under the guidance of the Manager, Pharmacovigilance. Sources may include recorded calls, claims, faxes, text messages, chat logs, and other records.
      • Ensures all safety data identified is captured, recorded, and reported in compliance with company SOPs.
      • Assists Pharmacovigilance teammates with tasks such as periodic reconciliation, records inspection, and internal audit activities.
      • Supports internal audits and preparation for third-party audits under the supervision of the Manager.
      • Performs other duties as assigned.

      Qualifications

      • Education/Degree Requirements: Associate degree or professional diploma in healthcare, pharmacy, or a medical-related field, or four years of equivalent relevant experience.
      • Experience: Two to four years of experience in a medical, pharmacy, or healthcare environment (preferably in a call center or claims processing). Medical call center or medical claims experience preferred. Quality Control or Quality Assurance experience is a plus.
      • Knowledge: Strong reading and verbal comprehension. Proficiency in English required; Spanish or other languages are a plus. Highly proficient in Microsoft Office applications including Word, PowerPoint, SharePoint, and Excel. Ability to clearly and concisely articulate medical and clinical information to manufacturer representatives.

      Skills

      • Strong problem-solving skills with the ability to resolve issues independently