JPA-PHMG Program Coordinator - Hybrid - 141094

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into 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. We need to parse the posting. Key details: - Payroll Title: TCHL PROJECT MGT PROFL 3 - Department: PHSO - IS - Hiring Pay Scale: $98,198 - $148,080 / Year - Worksite: Towne Centre Drive - Appointment Type: Career Appointment - Appointment Percent: 100% - Union: Uncovered - Total Openings: 1 - Work Schedule: Days, 8 hrs/day, Monday-Friday - #141094 JPA-PHMG Program Coordinator - Hybrid - Filing Deadline: Mon 10/5/2026 - Apply Now (application instructions) – we need to remove application instructions. - UC San Diego values... (boilerplate) – remove. - UCSD Layoff from Career Appointment: Apply by 09/23/26 for consideration with preference for rehire. All layoff applicants should contact their Employment Advisor. Reassignment Applicants: Eligible Reassignment clients should contact their Disability Counselor for assistance. (These are application instructions? Might be considered boilerplate; but they are specific to layoff/reassignment. Likely considered boilerplate and should be removed as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove these lines. - This position will work a hybrid schedule which includes a combination of working both onsite at Towne Centre Drive (San Diego, CA) and remote. - Description: The Program Coordinator will support the setup and ongoing administration of the program support structure for all JPA entities transitioning to Epic — establishing and tracking software and services contracts, coordinating billing to the JPA, and ensuring the contractual and financial framework is in place to support each entity through implementation and into steady-state support. Applies skills as a seasoned, experienced technical project management professional with a full understanding of project management frameworks and methods, relevant policies and procedures to resolve a wide range of issues. Demonstrates competency in selecting methods and techniques to obtain solutions. Manages projects of diverse scope, size, impact, budget and / or project team size. - Minimum Qualifications: Seven (7) years of related experience, education/training, OR a Bachelor’s degree in related area plus three (3) years of related experience/training. Related experience: accounting and finance management in a healthcare setting, contract management with Epic and third party vendors, draft technical project's statement of work. Requires effective communication and organization skills. Requires basic knowledge of project management principles, theories, and concepts. Requires ability to assess campus, medical center or Office of the President needs for information technology products and design services to meet those needs. Working knowledge of technology-related initiatives and an understanding of impact to the organization of such initiatives. Demonstrated capacity to anticipate obstacles and plan for contingencies. Demonstrated attention to detail. Demonstrated ability to determine relevance and prioritize tasks. Demonstrated advanced organization and project management skills. Demonstrated effective writing skills. Demonstrated competency in selecting and implementing project management methods and techniques. Broad knowledge of technology-related initiatives and an understanding of impact to the organization of such initiatives. Knowledge of most aspects of computing and communications including hardware infrastructure, networking, software, operations and disaster recovery. Proven leadership ability. Effective problem solving skills. Demonstrated ability to put forth persuasive arguments. Effective skill at tracking effort and project progress. - Preferred Qualifications: Strong background and experience in accounting practices and understanding of financial concepts. Strong background in contract management with Epic and third party vendors. Skills to independently draft technical project's statement of work with scope, timeline, cost, labor and success criteria. - SPECIAL CONDITIONS: Ability to travel to affiliate sites in San Diego on a monthly basis without departmental financial support except for mileage reimbursements. Must be able to work various hours and locations based on business needs. Employment is subject to a criminal background check and pre-employment physical. - Pay Transparency Act Annual Full Pay Range: $100,100 - $187,500 (will be prorated if the appointment percentage is less than 100%) Hourly Equivalent: $47.94 - $89.80. Factors in determining the appropriate compensation for a role include experience, skills, knowledge, abilities, education, licensure and certifications, and other business and organizational needs. The Hiring Pay Scale referenced in the job posting is the budgeted salary or hourly range that the University reasonably expects to pay for this position. The Annual Full Pay Range may be broader than what the University anticipates to pay for this position, based on internal equity, budget, and collective bargaining agreements (when applicable). - Apply Now (again) – remove. - If employed by the University of California, you will be required to comply with our Policy on Vaccination Programs... (boilerplate) – remove. - Federal, state, or local public health directives may impose additional requirements. If applicable, life-support certifications (BLS, NRP, ACLS, etc.) must include hands-on practice and in-person skills assessment; online-only certification is not acceptable. (boilerplate? Might be considered specific but still about requirements; but it's about certifications; maybe keep? It's about life-support certifications; not directly relevant to job? Might be considered boilerplate health requirement; but it's not EEO; but it's a condition. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories; but it's about vaccination and health requirements; could be considered legal boilerplate. Safer to remove. - UC San Diego Health is the only academic health system... (boilerplate) – remove. - Our facilities include... (boilerplate) – remove. - We invite you to join our team! (boilerplate) – remove. - Applications/Resumes are accepted for current job openings only... (application instructions) – remove. - To foster the best possible working and learning environment... (boilerplate) – remove. - For more information, please visit UC San Diego Principles of Community. (boilerplate) – remove. - The University of California is an Equal Opportunity Employer... (EEO boilerplate) – remove. - For the University of California’s Anti-Discrimination Policy, please visit: ... (EEO) – remove. - UC San Diego is a smoke and tobacco free environment... (boilerplate) – remove. - Please visit smokefree.ucsd.edu for more information. (boilerplate) – remove. - UC San Diego Health maintains a marijuana and drug free environment. Employees may be subject to drug screening. (boilerplate) – remove. - Misconduct Disclosure Requirement: As a condition of employment, the final candidate who accepts an offer of employment will be required to disclose if they have been subject to any final administrative or judicial decisions within the last seven years determining that they committed any misconduct; or have filed an appeal of a finding of substantiated misconduct with a previous employer. "Misconduct" means any violation of the policies governing employee conduct at the applicant’s previous place of employment, including, but not limited to, violations of policies prohibiting sexual harassment, sexual assault, or other forms of harassment, or discrimination, as defined by the employer. For reference, below are UC’s policies addressing some forms of misconduct: UC Sexual Violence and Sexual Harassment Policy UC Anti-Discrimination Policy Abusive Conduct in the Workplace (boilerplate/legal) – remove. Thus we keep substantive content: job details (title, department, hiring pay scale, worksite, appointment type, percent, union, openings, work schedule, hybrid schedule note), description, minimum qualifications, preferred qualifications, special conditions, pay transparency act info (annual full pay range, hourly equivalent). Also maybe include filing deadline? That's metadata; could be included in a short

  but not as heading. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include filing deadline in a paragraph. We need sections: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should decide which sections to include based on content. We have: - About the role: could include description and hybrid schedule note. - Responsibilities: could be derived from description (setup and ongoing administration, establishing and tracking contracts, coordinating billing, ensuring framework, etc.) Might be better to put responsibilities as a list. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe combine from requirements? But we can have Skills section if we have specific skills list; we have many skill statements in minimum qualifications; could be placed under Skills. - Benefits: Not explicitly stated; no benefits info besides maybe mileage reimbursements? That's under special conditions. Not benefits like health, retirement. So we should not create Benefits section unless posting actually states them. It does not list benefits like health insurance, etc. So omit Benefits. - Pay: we have Hiring Pay Scale and Annual Full Pay Range and Hourly Equivalent. So we can create Pay section. - Schedule: we have Work Schedule Days, 8 hrs/day, Monday-Friday and hybrid schedule note. So we can create Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the kept sections. We need to use

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

    for prose. Thus for each section we can have either prose or list. We need to output only HTML fragment. Let's structure:

    About the role

    ... description plus hybrid schedule note?

    But description includes responsibilities; maybe better to separate. Option: About the role: brief overview of position and hybrid schedule. Responsibilities: list of duties from description. Requirements: list of minimum qualifications. Qualifications: list of preferred qualifications. Skills: maybe list of skills from minimum qualifications (communication, organization, project management, etc.) but that could be redundant with Requirements. However we can still include Skills if we have distinct list; but we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section? But they ask to use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include them if we have content. We have content for Requirements (minimum qualifications). We have content for Qualifications (preferred qualifications). We have content for Skills (many skill statements). We have content for Pay. We have content for Schedule. Thus we can have sections: About the role (maybe short), Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. We need to ensure we don't create empty sections