Clinical Programs Specialist
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
4. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
5. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
6. Never create Pay/Schedule/Benefits sections unless the posting actually states them
7. Prefer a few substantive sections over many thin ones
8. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting:
- Company description: "About Judi Health" - this is company background, could be "About the company" or similar
- Position Summary: describes the role
- Position Responsibilities: broken into subsections (Vendor Clinical Program Administration, Program Coordination & Workflow Management, Clinical Vendor & Stakeholder Support, Quality, Compliance & Operational Excellence)
- Required Qualifications: list
- Preferred Qualifications: list
- Salary Range: $65,000 - $75,000 USD, Remote, US
- Boilerplate at the end: Code of Conduct, flexibility statement, EEO, privacy policy - these should be removed
I need to structure this into sections. The rules mention specific section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I should map:
- Position Summary → "About the role"
- Position Responsibilities → "Responsibilities"
- Required Qualifications → "Requirements" (or "Qualifications")
- Preferred Qualifications → could be part of "Qualifications" or separate
- Salary Range → "Pay"
- Remote, US → "Schedule" (since it mentions remote)
But the rules say: "include a section ONLY when the posting has real, specific content for it". The posting has specific content for all these.
I should not create a "Benefits" section because none are listed.
I need to use
for headings. Use - for lists. Use
for prose.
Let me draft:
About the role
...position summary...
Responsibilities
- Vendor Clinical Program Administration: ...
... but the responsibilities have subsections. Should I keep subsections as nested lists or separate headings? The rules say use for section headings. The subsections are part of responsibilities. I could make them but the rules only mention . However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels, but to be safe, I'll keep the subsections as list items with bold labels or as separate list items.
Better: For each responsibility area, create a list item with the area as a strong label, then sub-bullets? But the rules say use - for any list of duties. The duties are bullet points under each subsection. I could flatten them into a single list, but that loses structure. Alternatively, I could use nested lists: outer list for each responsibility area, inner list for specific duties.
Let me see the content:
Vendor Clinical Program Administration:
- Supports administration and operational activities for assigned clinical programs involving clinical vendor partners.
- Supports the maintenance of program workflows, standard operating procedures, job aids, process maps, reference materials, and other operational documentation.
- Monitor shared inboxes, work queues, pending activities, recurring deliverables, and escalations to support timely follow-up and continuity of program operations.
- Document vendor program activities, decisions, issues, interventions, and follow-up actions in applicable systems and tracking tools.
Program Coordination & Workflow Management:
- Apply established workflows and assist with updates when processes, systems, client requirements, or regulatory guidance change.
- Identify and support resolution of workflow gaps, document operational risks, and escalate recommendations to the Clinical Partnerships Lead.
- Balance multiple work-streams, prioritize time-sensitive activities, and meet established deadlines with minimal oversight.
- Maintain clinical program resources, including drug lists, through routine reviews, scheduled updates, and ad hoc changes.
Clinical Vendor & Stakeholder Support:
- Support the monitoring of vendor service-level commitments, reporting schedules, and required deliverables; escalate delays or performance concerns.
- Coordinate resolution of program inquiries and escalations while promoting a positive stakeholder and member experience.
- Support operations including vendor invoicing and reporting, custom client implementation requests, reporting requirements, claims monitoring, issue resolution, member communication proofs, and ongoing vendor program maintenance.
- Collaborate with internal and external stakeholders to ensure effective communication, coordination, a satisfactory client experience, and continuity of member care.
- Support the Clinical Programs Business Development needs, including client contracting, vendor management, preparation of opportunity analyses, and program sales support.
Quality, Compliance & Operational Excellence:
- Maintain compliance with all applicable federal, state, local, and organizational regulations, policies, and guidelines.
- Adhere to HIPAA requirements, internal SOPs, and company policies in the performance of daily responsibilities.
- Remain current on organizational communications, clinical updates, and process changes and apply them appropriately to daily work activities.
- Uphold general business needs and operations as required
I'll create a
for responsibilities, with each top-level item being a responsibility area, and nested for the specific duties.
Similarly for Required Qualifications and Preferred Qualifications: they are lists.
Salary Range: specific numbers, so include Pay section.
Remote, US: include Schedule section.
Company description: "About Judi Health" - could be "About the company" but the rules don't list that as a standard heading. The rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the company" is not listed, but it's substantive content. I could include it as "About the company" with . Or fold into "About the role"? The position summary is about the role. The company description is separate. I'll include a section "About the company" with since it's real content.
But the rules: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. So I can add "About the company".
However, the user said: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Clinical Programs Specialist". Not in the text provided? Actually the text starts with "About Judi Health" then "Position Summary". The job title might be implied. I'll not include a heading for the job title.
Now, I need to remove boilerplate: "All employees are responsible for adherence to the Judi Health Code of Conduct...", "This position description is designed to be flexible...", "We provide equal employment opportunities...", "By submitting an application, you agree to the retention of your personal data...", "More details about Judi Health's privacy practices...". These are boilerplate, remove.
Also remove "This range represents the low and high end of the anticipated base salary range. The actual base salary will depend on several factors such as: experience, knowledge, skills, and location of the job." That's part of salary description, but it's substantive? It's a disclaimer. I'll keep the salary range but maybe include the disclaimer as a paragraph.
The rules: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the salary disclaimer.
But also: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The disclaimer is not filler, it's context. I'll include it.
Now, structure:
About the company
Judi Health is a health technology company providing benefit administration solutions to employers, unions, health plans, and government entities. Judi Health replaces fragmented, outdated systems with the industry's first Unified Claims Processing™ architecture, seamlessly consolidating pharmacy and medical benefit administration on a single, secure platform. By delivering true price transparency, eliminating unnecessary middleman fees, and leveraging advanced AI-powered care delivery, Judi Health helps clients achieve unprecedented operational efficiency and service levels. At Judi Health, we're deploying the infrastructure our country needs to deliver the healthcare we all deserve. We are the intelligence platform powering benefits plans for millions of Americans and proudly leading the next generation of care. To learn more, visit www.judi.health.
About the role
The Clinical Programs Specialist provides operational and administrative support for the day-to-day management of clinical programs and clinical vendor partnerships under the direction of the Clinical Programs Specialists Manager. This role coordinates program reporting, vendor invoices, and drug list maintenance. This role also maintains program workflows and documentation, supports program implementations, monitors recurring deliverables, supports stakeholder communications, and tracks issues through resolution. The Specialist helps ensure established program processes are executed consistently, accurately, and in accordance with contractual, regulatory, and organizational requirements. This role helps ensure programs are executed effectively and efficiently; stakeholders remain informed, and both clients and members receive timely, high-quality support involving clinical programs involving clinical vendor partners.
Responsibilities
- Vendor Clinical Program Administration
- Supports administration and operational activities for assigned clinical programs involving clinical vendor partners.
- Supports the maintenance of program workflows, standard operating procedures, job aids, process maps, reference materials, and other operational documentation.
- Monitor shared inboxes, work queues, pending activities, recurring deliverables, and escalations to support timely follow-up and continuity of program operations.
- Document vendor program activities, decisions, issues, interventions, and follow-up actions in applicable systems and tracking tools.
- Program Coordination & Workflow Management
- Apply established workflows and assist with updates when processes, systems, client requirements, or regulatory guidance change.
- Identify and support resolution of workflow gaps, document operational risks, and escalate recommendations to the Clinical Partnerships Lead.
- Balance multiple work-streams, prioritize time-sensitive activities, and meet established deadlines with minimal oversight.
- Maintain clinical program resources, including drug lists, through routine reviews, scheduled updates, and ad hoc changes.
- Clinical Vendor & Stakeholder Support
- Support the monitoring of vendor service-level commitments, reporting schedules, and required deliverables; escalate delays or performance concerns.
- Coordinate resolution of program inquiries and escalations while promoting a positive stakeholder and member experience.
- Support operations including vendor invoicing and reporting, custom client implementation requests, reporting requirements, claims monitoring, issue resolution, member communication proofs, and ongoing vendor program maintenance.
- Collaborate with internal and external stakeholders to ensure effective communication, coordination, a satisfactory client experience, and continuity of member care.
- Support the Clinical Programs Business Development needs, including client contracting, vendor management, preparation of opportunity analyses, and program sales support.
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 4. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 5. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 6. Never create Pay/Schedule/Benefits sections unless the posting actually states them 7. Prefer a few substantive sections over many thin ones 8. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: - Company description: "About Judi Health" - this is company background, could be "About the company" or similar - Position Summary: describes the role - Position Responsibilities: broken into subsections (Vendor Clinical Program Administration, Program Coordination & Workflow Management, Clinical Vendor & Stakeholder Support, Quality, Compliance & Operational Excellence) - Required Qualifications: list - Preferred Qualifications: list - Salary Range: $65,000 - $75,000 USD, Remote, US - Boilerplate at the end: Code of Conduct, flexibility statement, EEO, privacy policy - these should be removed I need to structure this into sections. The rules mention specific section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should map: - Position Summary → "About the role" - Position Responsibilities → "Responsibilities" - Required Qualifications → "Requirements" (or "Qualifications") - Preferred Qualifications → could be part of "Qualifications" or separate - Salary Range → "Pay" - Remote, US → "Schedule" (since it mentions remote) But the rules say: "include a section ONLY when the posting has real, specific content for it". The posting has specific content for all these. I should not create a "Benefits" section because none are listed. I need to use
for headings. Use - for lists. Use
for prose.
Let me draft:
About the role
...position summary...
Responsibilities
- Vendor Clinical Program Administration: ...
... but the responsibilities have subsections. Should I keep subsections as nested lists or separate headings? The rules say use for section headings. The subsections are part of responsibilities. I could make them but the rules only mention . However, the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other heading levels, but to be safe, I'll keep the subsections as list items with bold labels or as separate list items.
Better: For each responsibility area, create a list item with the area as a strong label, then sub-bullets? But the rules say use - for any list of duties. The duties are bullet points under each subsection. I could flatten them into a single list, but that loses structure. Alternatively, I could use nested lists: outer list for each responsibility area, inner list for specific duties.
Let me see the content:
Vendor Clinical Program Administration:
- Supports administration and operational activities for assigned clinical programs involving clinical vendor partners.
- Supports the maintenance of program workflows, standard operating procedures, job aids, process maps, reference materials, and other operational documentation.
- Monitor shared inboxes, work queues, pending activities, recurring deliverables, and escalations to support timely follow-up and continuity of program operations.
- Document vendor program activities, decisions, issues, interventions, and follow-up actions in applicable systems and tracking tools.
Program Coordination & Workflow Management:
- Apply established workflows and assist with updates when processes, systems, client requirements, or regulatory guidance change.
- Identify and support resolution of workflow gaps, document operational risks, and escalate recommendations to the Clinical Partnerships Lead.
- Balance multiple work-streams, prioritize time-sensitive activities, and meet established deadlines with minimal oversight.
- Maintain clinical program resources, including drug lists, through routine reviews, scheduled updates, and ad hoc changes.
Clinical Vendor & Stakeholder Support:
- Support the monitoring of vendor service-level commitments, reporting schedules, and required deliverables; escalate delays or performance concerns.
- Coordinate resolution of program inquiries and escalations while promoting a positive stakeholder and member experience.
- Support operations including vendor invoicing and reporting, custom client implementation requests, reporting requirements, claims monitoring, issue resolution, member communication proofs, and ongoing vendor program maintenance.
- Collaborate with internal and external stakeholders to ensure effective communication, coordination, a satisfactory client experience, and continuity of member care.
- Support the Clinical Programs Business Development needs, including client contracting, vendor management, preparation of opportunity analyses, and program sales support.
Quality, Compliance & Operational Excellence:
- Maintain compliance with all applicable federal, state, local, and organizational regulations, policies, and guidelines.
- Adhere to HIPAA requirements, internal SOPs, and company policies in the performance of daily responsibilities.
- Remain current on organizational communications, clinical updates, and process changes and apply them appropriately to daily work activities.
- Uphold general business needs and operations as required
I'll create a
for responsibilities, with each top-level item being a responsibility area, and nested for the specific duties.
Similarly for Required Qualifications and Preferred Qualifications: they are lists.
Salary Range: specific numbers, so include Pay section.
Remote, US: include Schedule section.
Company description: "About Judi Health" - could be "About the company" but the rules don't list that as a standard heading. The rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the company" is not listed, but it's substantive content. I could include it as "About the company" with . Or fold into "About the role"? The position summary is about the role. The company description is separate. I'll include a section "About the company" with since it's real content.
But the rules: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. So I can add "About the company".
However, the user said: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Clinical Programs Specialist". Not in the text provided? Actually the text starts with "About Judi Health" then "Position Summary". The job title might be implied. I'll not include a heading for the job title.
Now, I need to remove boilerplate: "All employees are responsible for adherence to the Judi Health Code of Conduct...", "This position description is designed to be flexible...", "We provide equal employment opportunities...", "By submitting an application, you agree to the retention of your personal data...", "More details about Judi Health's privacy practices...". These are boilerplate, remove.
Also remove "This range represents the low and high end of the anticipated base salary range. The actual base salary will depend on several factors such as: experience, knowledge, skills, and location of the job." That's part of salary description, but it's substantive? It's a disclaimer. I'll keep the salary range but maybe include the disclaimer as a paragraph.
The rules: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the salary disclaimer.
But also: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The disclaimer is not filler, it's context. I'll include it.
Now, structure:
About the company
Judi Health is a health technology company providing benefit administration solutions to employers, unions, health plans, and government entities. Judi Health replaces fragmented, outdated systems with the industry's first Unified Claims Processing™ architecture, seamlessly consolidating pharmacy and medical benefit administration on a single, secure platform. By delivering true price transparency, eliminating unnecessary middleman fees, and leveraging advanced AI-powered care delivery, Judi Health helps clients achieve unprecedented operational efficiency and service levels. At Judi Health, we're deploying the infrastructure our country needs to deliver the healthcare we all deserve. We are the intelligence platform powering benefits plans for millions of Americans and proudly leading the next generation of care. To learn more, visit www.judi.health.
About the role
The Clinical Programs Specialist provides operational and administrative support for the day-to-day management of clinical programs and clinical vendor partnerships under the direction of the Clinical Programs Specialists Manager. This role coordinates program reporting, vendor invoices, and drug list maintenance. This role also maintains program workflows and documentation, supports program implementations, monitors recurring deliverables, supports stakeholder communications, and tracks issues through resolution. The Specialist helps ensure established program processes are executed consistently, accurately, and in accordance with contractual, regulatory, and organizational requirements. This role helps ensure programs are executed effectively and efficiently; stakeholders remain informed, and both clients and members receive timely, high-quality support involving clinical programs involving clinical vendor partners.
Responsibilities
- Vendor Clinical Program Administration
- Supports administration and operational activities for assigned clinical programs involving clinical vendor partners.
- Supports the maintenance of program workflows, standard operating procedures, job aids, process maps, reference materials, and other operational documentation.
- Monitor shared inboxes, work queues, pending activities, recurring deliverables, and escalations to support timely follow-up and continuity of program operations.
- Document vendor program activities, decisions, issues, interventions, and follow-up actions in applicable systems and tracking tools.
- Program Coordination & Workflow Management
- Apply established workflows and assist with updates when processes, systems, client requirements, or regulatory guidance change.
- Identify and support resolution of workflow gaps, document operational risks, and escalate recommendations to the Clinical Partnerships Lead.
- Balance multiple work-streams, prioritize time-sensitive activities, and meet established deadlines with minimal oversight.
- Maintain clinical program resources, including drug lists, through routine reviews, scheduled updates, and ad hoc changes.
- Clinical Vendor & Stakeholder Support
- Support the monitoring of vendor service-level commitments, reporting schedules, and required deliverables; escalate delays or performance concerns.
- Coordinate resolution of program inquiries and escalations while promoting a positive stakeholder and member experience.
- Support operations including vendor invoicing and reporting, custom client implementation requests, reporting requirements, claims monitoring, issue resolution, member communication proofs, and ongoing vendor program maintenance.
- Collaborate with internal and external stakeholders to ensure effective communication, coordination, a satisfactory client experience, and continuity of member care.
- Support the Clinical Programs Business Development needs, including client contracting, vendor management, preparation of opportunity analyses, and program sales support.
for prose. Let me draft:
About the role
...position summary...
Responsibilities
- Vendor Clinical Program Administration: ... ... but the responsibilities have subsections. Should I keep subsections as nested lists or separate headings? The rules say use
- for any list of duties. The duties are bullet points under each subsection. I could flatten them into a single list, but that loses structure. Alternatively, I could use nested lists: outer list for each responsibility area, inner list for specific duties.
Let me see the content:
Vendor Clinical Program Administration:
- Supports administration and operational activities for assigned clinical programs involving clinical vendor partners.
- Supports the maintenance of program workflows, standard operating procedures, job aids, process maps, reference materials, and other operational documentation.
- Monitor shared inboxes, work queues, pending activities, recurring deliverables, and escalations to support timely follow-up and continuity of program operations.
- Document vendor program activities, decisions, issues, interventions, and follow-up actions in applicable systems and tracking tools.
Program Coordination & Workflow Management:
- Apply established workflows and assist with updates when processes, systems, client requirements, or regulatory guidance change.
- Identify and support resolution of workflow gaps, document operational risks, and escalate recommendations to the Clinical Partnerships Lead.
- Balance multiple work-streams, prioritize time-sensitive activities, and meet established deadlines with minimal oversight.
- Maintain clinical program resources, including drug lists, through routine reviews, scheduled updates, and ad hoc changes.
Clinical Vendor & Stakeholder Support:
- Support the monitoring of vendor service-level commitments, reporting schedules, and required deliverables; escalate delays or performance concerns.
- Coordinate resolution of program inquiries and escalations while promoting a positive stakeholder and member experience.
- Support operations including vendor invoicing and reporting, custom client implementation requests, reporting requirements, claims monitoring, issue resolution, member communication proofs, and ongoing vendor program maintenance.
- Collaborate with internal and external stakeholders to ensure effective communication, coordination, a satisfactory client experience, and continuity of member care.
- Support the Clinical Programs Business Development needs, including client contracting, vendor management, preparation of opportunity analyses, and program sales support.
Quality, Compliance & Operational Excellence:
- Maintain compliance with all applicable federal, state, local, and organizational regulations, policies, and guidelines.
- Adhere to HIPAA requirements, internal SOPs, and company policies in the performance of daily responsibilities.
- Remain current on organizational communications, clinical updates, and process changes and apply them appropriately to daily work activities.
- Uphold general business needs and operations as required
I'll create a
- for responsibilities, with each top-level item being a responsibility area, and nested
- Vendor Clinical Program Administration
- Supports administration and operational activities for assigned clinical programs involving clinical vendor partners.
- Supports the maintenance of program workflows, standard operating procedures, job aids, process maps, reference materials, and other operational documentation.
- Monitor shared inboxes, work queues, pending activities, recurring deliverables, and escalations to support timely follow-up and continuity of program operations.
- Document vendor program activities, decisions, issues, interventions, and follow-up actions in applicable systems and tracking tools.
- Program Coordination & Workflow Management
- Apply established workflows and assist with updates when processes, systems, client requirements, or regulatory guidance change.
- Identify and support resolution of workflow gaps, document operational risks, and escalate recommendations to the Clinical Partnerships Lead.
- Balance multiple work-streams, prioritize time-sensitive activities, and meet established deadlines with minimal oversight.
- Maintain clinical program resources, including drug lists, through routine reviews, scheduled updates, and ad hoc changes.
- Clinical Vendor & Stakeholder Support
- Support the monitoring of vendor service-level commitments, reporting schedules, and required deliverables; escalate delays or performance concerns.
- Coordinate resolution of program inquiries and escalations while promoting a positive stakeholder and member experience.
- Support operations including vendor invoicing and reporting, custom client implementation requests, reporting requirements, claims monitoring, issue resolution, member communication proofs, and ongoing vendor program maintenance.
- Collaborate with internal and external stakeholders to ensure effective communication, coordination, a satisfactory client experience, and continuity of member care.
- Support the Clinical Programs Business Development needs, including client contracting, vendor management, preparation of opportunity analyses, and program sales support.
- for the specific duties.
Similarly for Required Qualifications and Preferred Qualifications: they are lists.
Salary Range: specific numbers, so include Pay section.
Remote, US: include Schedule section.
Company description: "About Judi Health" - could be "About the company" but the rules don't list that as a standard heading. The rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the company" is not listed, but it's substantive content. I could include it as "About the company" with
. Or fold into "About the role"? The position summary is about the role. The company description is separate. I'll include a section "About the company" with
since it's real content. But the rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. So I can add "About the company". However, the user said: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Clinical Programs Specialist". Not in the text provided? Actually the text starts with "About Judi Health" then "Position Summary". The job title might be implied. I'll not include a heading for the job title. Now, I need to remove boilerplate: "All employees are responsible for adherence to the Judi Health Code of Conduct...", "This position description is designed to be flexible...", "We provide equal employment opportunities...", "By submitting an application, you agree to the retention of your personal data...", "More details about Judi Health's privacy practices...". These are boilerplate, remove. Also remove "This range represents the low and high end of the anticipated base salary range. The actual base salary will depend on several factors such as: experience, knowledge, skills, and location of the job." That's part of salary description, but it's substantive? It's a disclaimer. I'll keep the salary range but maybe include the disclaimer as a paragraph. The rules: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the salary disclaimer. But also: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The disclaimer is not filler, it's context. I'll include it. Now, structure:
About the company
Judi Health is a health technology company providing benefit administration solutions to employers, unions, health plans, and government entities. Judi Health replaces fragmented, outdated systems with the industry's first Unified Claims Processing™ architecture, seamlessly consolidating pharmacy and medical benefit administration on a single, secure platform. By delivering true price transparency, eliminating unnecessary middleman fees, and leveraging advanced AI-powered care delivery, Judi Health helps clients achieve unprecedented operational efficiency and service levels. At Judi Health, we're deploying the infrastructure our country needs to deliver the healthcare we all deserve. We are the intelligence platform powering benefits plans for millions of Americans and proudly leading the next generation of care. To learn more, visit www.judi.health.
About the role
The Clinical Programs Specialist provides operational and administrative support for the day-to-day management of clinical programs and clinical vendor partnerships under the direction of the Clinical Programs Specialists Manager. This role coordinates program reporting, vendor invoices, and drug list maintenance. This role also maintains program workflows and documentation, supports program implementations, monitors recurring deliverables, supports stakeholder communications, and tracks issues through resolution. The Specialist helps ensure established program processes are executed consistently, accurately, and in accordance with contractual, regulatory, and organizational requirements. This role helps ensure programs are executed effectively and efficiently; stakeholders remain informed, and both clients and members receive timely, high-quality support involving clinical programs involving clinical vendor partners.
Responsibilities
- Vendor Clinical Program Administration