Specialist, Population Health
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. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit 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 posting actually states them.
We need to parse the posting.
Content:
- Primary Location South Campus Department Population Health Shift Day (United States of America) Schedule Full time Weekly Hours 40 FTE 1 Employee Status Regular Expected Starting Pay Range $53,705.60 - $67,142.40 Starting pay is based on experience, skills, and equity; exceptions may apply for highly qualified candidates. Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply. Annual pay may vary based on FTE status.
- Job Responsibilities: multiple bullet-like paragraphs.
- Job Qualifications: High school diploma or equivalent and 5+ years of work experience OR Bachelor's degree and 2+ years of work experience OR Master's Degree and 0+ years of work experience
- About Us: description of Cincinnati Children's.
- Additional sections: "Comprehensive Job Description Provided Upon Request." (maybe not needed). Then EEO boilerplate to remove.
We need to decide sections.
We have:
- About the role? Could be a short description of role? Not explicitly given. The posting includes "Primary Location ..." etc. Could be considered "About the role" maybe? But we have "Primary Location ..." and schedule details. Could treat as "About the role" with location, schedule, etc. However we must not create sections with filler. The location, schedule, shift, weekly hours, FTE, employee status are substantive. Could be placed under a heading like "About the role" or maybe "Details". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content.
We have Pay info: Expected Starting Pay Range $53,705.60 - $67,142.40, plus notes about starting pay based on experience, etc., additional pay, benefits may apply, annual pay may vary based on FTE status. So we have Pay section content.
We have Schedule: "Schedule Full time Weekly Hours 40 FTE 1 Employee Status Regular". Also "Shift Day". So we have schedule info.
We have Benefits: The posting mentions "Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply." That's vague; does not list specific benefits. It says benefits may apply but not specific. According to rule: never create Benefits section unless posting actually states them. It states "benefits may apply" but not specific benefits. That's vague; maybe we should not create Benefits section because no specific benefits listed. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, we need actual benefits listed (like health insurance, retirement, etc.). Since not listed, we should omit Benefits section.
We have Responsibilities: detailed list.
We have Requirements/Qualifications: The posting has "Job Qualifications" with education/experience alternatives. Also maybe "Requirements" could be same as qualifications. We could have a "Qualifications" section with those alternatives. Could also have "Requirements" but we need to avoid duplication. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include Qualifications (since we have that). Could also include Requirements if we have separate content; but we don't have separate requirements besides qualifications. So we can just have Qualifications.
We have Skills: Not explicitly listed; but responsibilities mention skills like project management, data analysis, communication, etc. However not a explicit skills list. We could create a Skills section if we can extract from responsibilities? But rule: only include section when posting has real, specific content for it. The responsibilities contain skill-like statements but not a dedicated skills section. Might be better to not create Skills section unless we have explicit list. Safer to omit.
We have About the role: Could include location, shift, schedule, FTE, employee status. But we already have Schedule section for schedule details. Could put location and department under About the role. Let's see: The posting starts: "Primary Location South Campus Department Population Health Shift Day (United States of America) Schedule Full time Weekly Hours 40 FTE 1 Employee Status Regular Expected Starting Pay Range ..." So we could parse:
- About the role: Primary Location, Department, Shift, maybe Employee Status? But Employee Status could be part of schedule? Actually schedule includes Full time, Weekly Hours 40, FTE 1, Employee Status Regular. So we could put those under Schedule.
Thus About the role could include Primary Location, Department, Shift Day (United States of America). That's substantive.
We also have "About Us" describing the organization. That could be under "About the role"? No, that's about the employer. Could be a separate section like "About the organization" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Us". So we might incorporate the About Us description into About the role? Or maybe we can omit it because it's not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About Us text somewhere. Since there is no heading for About Us, we could put it under a
without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having prose outside headings. It says use for section headings, - for any list, and
for prose. So we can have a
for About Us without a heading. However we need to decide if we want to add a heading like "About the role" for location/department/shift, and then have a
for About Us after that. That seems okay.
But we must not repeat the job title as heading. Not an issue.
We need to remove boilerplate: EEO/Veteran/Disability, Equal Opportunity Employer, etc. Also "Comprehensive Job Description Provided Upon Request." maybe not needed? It's substantive? It's a statement that full description provided upon request; could be considered boilerplate. Might be considered filler. I'd remove it.
Also remove duplicated lines.
Now structure:
About the role
Primary Location: South Campus, Department: Population Health, Shift: Day (United States of America).
Schedule
Schedule: Full time, Weekly Hours: 40, FTE: 1, Employee Status: Regular.
Pay
Expected Starting Pay Range: $53,705.60 - $67,142.40. Starting pay is based on experience, skills, and equity; exceptions may apply for highly qualified candidates. Additional pay (e.g., shift, on‑call, or weekend differentials) may apply. Annual pay may vary based on FTE status.
Responsibilities
- Departmental Support - Create and execute on deliverables, both independently and under the direction of team members, that contributes to improved outcomes. Provides operational support and analyses for project and program initiatives in pursuit of health equity; supports and contributes to quality improvement initiatives. Assists in the development of reports, documents and presentations for cross-sector equity initiatives. Acts as a liaison to Center leadership to identify successes, challenges, and resource needs for individual equity initiatives.
- Administrative Support - Set up and manage call schedules and/or coordinate meetings with other departments/divisions, community partners, and local, national, or international experts. Coordinates and schedules all logistics related to the assigned projects/programs, i.e., meetings, conferences, conference calls, and other appointments. May take and transcribe meeting minutes and distribute them accordingly. Places orders for materials as needed and monitors budget for funded projects/programs. May liaise between clinical, operations, research staff, and community partners. Adapts to scheduling and communication needs of various community and internal stakeholders as needed.
- Program/Project Coordination - Coordinates assigned projects including collaboration on project and program plans, budgets, and resource requirements. Defines and uses appropriate project and program management tools and concepts (charters, scope management, budget management, risk/ issue management, and communications management). Contributes to the strategic planning and development processes, identifies areas of opportunities, and focuses on translating segments of plans into well-elaborated projects and programs with w/timelines and deliverables. Determines priorities for responsibilities and assignments based on importance and urgency. Responsible for tracking the progress of initiatives and preparing internal reports. Prepares and distributes communication about the work initiatives to internal and external stakeholders. Supports the research inventory and cross-department engagement to build new grant mechanisms. May assist in assessing, prioritizing, and allocating resources to support equity research - including data, grant review processes, and grant writing support. Understands and meets expectations for deliverable quality and timeliness.
- Data Analysis/ Reporting - Perform primary and secondary data collection (e.g., literature reviews), summarize findings, and effectively communicate results to team. Coordinate collection of data. Conduct/ support qualitative and quantitative analysis of project data. Support and execute regulatory/ reporting activities related to projects (e.g., IRB, updates/ reports to funding agencies, etc.).
- Collaboration & Adaptability - Ability to pursue interdisciplinary collaboration. Comfortable and willing to engage with community members and organizations. Demonstrates emphasis on relationship building / relational work, flexibility, and adaptability to change. Open to continuous learning and capable of taking a systems-learning view.
Qualifications
High school diploma or equivalent and 5+ years of work experience OR Bachelor's degree and 2+ years of work experience OR Master's Degree and 0+ years of work experience.
About the organization
Not allowed heading. But we have About Us text. Could we put it under a without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but it suggests we should use those headings for sections. It might be okay to have a
for About Us without a heading. However, we might consider adding a heading "About the role" and include the About Us inside that? But that would mix location and employer description. Might be okay but could be confusing.
Better: Keep About Us as a
after Qualifications, without a heading. The instruction says use
for prose. So we can have a
for About Us.
Thus final HTML:
About the role
Primary Location: South Campus, Department: Population Health, Shift: Day (United States of America).
Schedule
Schedule: Full time, Weekly Hours: 40, FTE: 1, Employee Status: Regular.
Pay
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit 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 posting actually states them. We need to parse the posting. Content: - Primary Location South Campus Department Population Health Shift Day (United States of America) Schedule Full time Weekly Hours 40 FTE 1 Employee Status Regular Expected Starting Pay Range $53,705.60 - $67,142.40 Starting pay is based on experience, skills, and equity; exceptions may apply for highly qualified candidates. Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply. Annual pay may vary based on FTE status. - Job Responsibilities: multiple bullet-like paragraphs. - Job Qualifications: High school diploma or equivalent and 5+ years of work experience OR Bachelor's degree and 2+ years of work experience OR Master's Degree and 0+ years of work experience - About Us: description of Cincinnati Children's. - Additional sections: "Comprehensive Job Description Provided Upon Request." (maybe not needed). Then EEO boilerplate to remove. We need to decide sections. We have: - About the role? Could be a short description of role? Not explicitly given. The posting includes "Primary Location ..." etc. Could be considered "About the role" maybe? But we have "Primary Location ..." and schedule details. Could treat as "About the role" with location, schedule, etc. However we must not create sections with filler. The location, schedule, shift, weekly hours, FTE, employee status are substantive. Could be placed under a heading like "About the role" or maybe "Details". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have Pay info: Expected Starting Pay Range $53,705.60 - $67,142.40, plus notes about starting pay based on experience, etc., additional pay, benefits may apply, annual pay may vary based on FTE status. So we have Pay section content. We have Schedule: "Schedule Full time Weekly Hours 40 FTE 1 Employee Status Regular". Also "Shift Day". So we have schedule info. We have Benefits: The posting mentions "Additional pay (e.g., shift, on‑call, or weekend differentials) and benefits may apply." That's vague; does not list specific benefits. It says benefits may apply but not specific. According to rule: never create Benefits section unless posting actually states them. It states "benefits may apply" but not specific benefits. That's vague; maybe we should not create Benefits section because no specific benefits listed. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, we need actual benefits listed (like health insurance, retirement, etc.). Since not listed, we should omit Benefits section. We have Responsibilities: detailed list. We have Requirements/Qualifications: The posting has "Job Qualifications" with education/experience alternatives. Also maybe "Requirements" could be same as qualifications. We could have a "Qualifications" section with those alternatives. Could also have "Requirements" but we need to avoid duplication. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include Qualifications (since we have that). Could also include Requirements if we have separate content; but we don't have separate requirements besides qualifications. So we can just have Qualifications. We have Skills: Not explicitly listed; but responsibilities mention skills like project management, data analysis, communication, etc. However not a explicit skills list. We could create a Skills section if we can extract from responsibilities? But rule: only include section when posting has real, specific content for it. The responsibilities contain skill-like statements but not a dedicated skills section. Might be better to not create Skills section unless we have explicit list. Safer to omit. We have About the role: Could include location, shift, schedule, FTE, employee status. But we already have Schedule section for schedule details. Could put location and department under About the role. Let's see: The posting starts: "Primary Location South Campus Department Population Health Shift Day (United States of America) Schedule Full time Weekly Hours 40 FTE 1 Employee Status Regular Expected Starting Pay Range ..." So we could parse: - About the role: Primary Location, Department, Shift, maybe Employee Status? But Employee Status could be part of schedule? Actually schedule includes Full time, Weekly Hours 40, FTE 1, Employee Status Regular. So we could put those under Schedule. Thus About the role could include Primary Location, Department, Shift Day (United States of America). That's substantive. We also have "About Us" describing the organization. That could be under "About the role"? No, that's about the employer. Could be a separate section like "About the organization" but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Us". So we might incorporate the About Us description into About the role? Or maybe we can omit it because it's not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About Us text somewhere. Since there is no heading for About Us, we could put it under a
without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having prose outside headings. It says use for section headings, - for any list, and
for prose. So we can have a
for About Us without a heading. However we need to decide if we want to add a heading like "About the role" for location/department/shift, and then have a
for About Us after that. That seems okay.
But we must not repeat the job title as heading. Not an issue.
We need to remove boilerplate: EEO/Veteran/Disability, Equal Opportunity Employer, etc. Also "Comprehensive Job Description Provided Upon Request." maybe not needed? It's substantive? It's a statement that full description provided upon request; could be considered boilerplate. Might be considered filler. I'd remove it.
Also remove duplicated lines.
Now structure:
About the role
Primary Location: South Campus, Department: Population Health, Shift: Day (United States of America).
Schedule
Schedule: Full time, Weekly Hours: 40, FTE: 1, Employee Status: Regular.
Pay
Expected Starting Pay Range: $53,705.60 - $67,142.40. Starting pay is based on experience, skills, and equity; exceptions may apply for highly qualified candidates. Additional pay (e.g., shift, on‑call, or weekend differentials) may apply. Annual pay may vary based on FTE status.
Responsibilities
- Departmental Support - Create and execute on deliverables, both independently and under the direction of team members, that contributes to improved outcomes. Provides operational support and analyses for project and program initiatives in pursuit of health equity; supports and contributes to quality improvement initiatives. Assists in the development of reports, documents and presentations for cross-sector equity initiatives. Acts as a liaison to Center leadership to identify successes, challenges, and resource needs for individual equity initiatives.
- Administrative Support - Set up and manage call schedules and/or coordinate meetings with other departments/divisions, community partners, and local, national, or international experts. Coordinates and schedules all logistics related to the assigned projects/programs, i.e., meetings, conferences, conference calls, and other appointments. May take and transcribe meeting minutes and distribute them accordingly. Places orders for materials as needed and monitors budget for funded projects/programs. May liaise between clinical, operations, research staff, and community partners. Adapts to scheduling and communication needs of various community and internal stakeholders as needed.
- Program/Project Coordination - Coordinates assigned projects including collaboration on project and program plans, budgets, and resource requirements. Defines and uses appropriate project and program management tools and concepts (charters, scope management, budget management, risk/ issue management, and communications management). Contributes to the strategic planning and development processes, identifies areas of opportunities, and focuses on translating segments of plans into well-elaborated projects and programs with w/timelines and deliverables. Determines priorities for responsibilities and assignments based on importance and urgency. Responsible for tracking the progress of initiatives and preparing internal reports. Prepares and distributes communication about the work initiatives to internal and external stakeholders. Supports the research inventory and cross-department engagement to build new grant mechanisms. May assist in assessing, prioritizing, and allocating resources to support equity research - including data, grant review processes, and grant writing support. Understands and meets expectations for deliverable quality and timeliness.
- Data Analysis/ Reporting - Perform primary and secondary data collection (e.g., literature reviews), summarize findings, and effectively communicate results to team. Coordinate collection of data. Conduct/ support qualitative and quantitative analysis of project data. Support and execute regulatory/ reporting activities related to projects (e.g., IRB, updates/ reports to funding agencies, etc.).
- Collaboration & Adaptability - Ability to pursue interdisciplinary collaboration. Comfortable and willing to engage with community members and organizations. Demonstrates emphasis on relationship building / relational work, flexibility, and adaptability to change. Open to continuous learning and capable of taking a systems-learning view.
Qualifications
High school diploma or equivalent and 5+ years of work experience OR Bachelor's degree and 2+ years of work experience OR Master's Degree and 0+ years of work experience.
About the organization
Not allowed heading. But we have About Us text. Could we put it under a without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but it suggests we should use those headings for sections. It might be okay to have a
for About Us without a heading. However, we might consider adding a heading "About the role" and include the About Us inside that? But that would mix location and employer description. Might be okay but could be confusing.
Better: Keep About Us as a
after Qualifications, without a heading. The instruction says use
for prose. So we can have a
for About Us.
Thus final HTML:
About the role
Primary Location: South Campus, Department: Population Health, Shift: Day (United States of America).
Schedule
Schedule: Full time, Weekly Hours: 40, FTE: 1, Employee Status: Regular.
Pay
- for any list, and
for prose. So we can have a
for About Us without a heading. However we need to decide if we want to add a heading like "About the role" for location/department/shift, and then have a
for About Us after that. That seems okay. But we must not repeat the job title as heading. Not an issue. We need to remove boilerplate: EEO/Veteran/Disability, Equal Opportunity Employer, etc. Also "Comprehensive Job Description Provided Upon Request." maybe not needed? It's substantive? It's a statement that full description provided upon request; could be considered boilerplate. Might be considered filler. I'd remove it. Also remove duplicated lines. Now structure:
About the role
Primary Location: South Campus, Department: Population Health, Shift: Day (United States of America).
Schedule
Schedule: Full time, Weekly Hours: 40, FTE: 1, Employee Status: Regular.
Pay
Expected Starting Pay Range: $53,705.60 - $67,142.40. Starting pay is based on experience, skills, and equity; exceptions may apply for highly qualified candidates. Additional pay (e.g., shift, on‑call, or weekend differentials) may apply. Annual pay may vary based on FTE status.
Responsibilities
- Departmental Support - Create and execute on deliverables, both independently and under the direction of team members, that contributes to improved outcomes. Provides operational support and analyses for project and program initiatives in pursuit of health equity; supports and contributes to quality improvement initiatives. Assists in the development of reports, documents and presentations for cross-sector equity initiatives. Acts as a liaison to Center leadership to identify successes, challenges, and resource needs for individual equity initiatives.
- Administrative Support - Set up and manage call schedules and/or coordinate meetings with other departments/divisions, community partners, and local, national, or international experts. Coordinates and schedules all logistics related to the assigned projects/programs, i.e., meetings, conferences, conference calls, and other appointments. May take and transcribe meeting minutes and distribute them accordingly. Places orders for materials as needed and monitors budget for funded projects/programs. May liaise between clinical, operations, research staff, and community partners. Adapts to scheduling and communication needs of various community and internal stakeholders as needed.
- Program/Project Coordination - Coordinates assigned projects including collaboration on project and program plans, budgets, and resource requirements. Defines and uses appropriate project and program management tools and concepts (charters, scope management, budget management, risk/ issue management, and communications management). Contributes to the strategic planning and development processes, identifies areas of opportunities, and focuses on translating segments of plans into well-elaborated projects and programs with w/timelines and deliverables. Determines priorities for responsibilities and assignments based on importance and urgency. Responsible for tracking the progress of initiatives and preparing internal reports. Prepares and distributes communication about the work initiatives to internal and external stakeholders. Supports the research inventory and cross-department engagement to build new grant mechanisms. May assist in assessing, prioritizing, and allocating resources to support equity research - including data, grant review processes, and grant writing support. Understands and meets expectations for deliverable quality and timeliness.
- Data Analysis/ Reporting - Perform primary and secondary data collection (e.g., literature reviews), summarize findings, and effectively communicate results to team. Coordinate collection of data. Conduct/ support qualitative and quantitative analysis of project data. Support and execute regulatory/ reporting activities related to projects (e.g., IRB, updates/ reports to funding agencies, etc.).
- Collaboration & Adaptability - Ability to pursue interdisciplinary collaboration. Comfortable and willing to engage with community members and organizations. Demonstrates emphasis on relationship building / relational work, flexibility, and adaptability to change. Open to continuous learning and capable of taking a systems-learning view.
Qualifications
High school diploma or equivalent and 5+ years of work experience OR Bachelor's degree and 2+ years of work experience OR Master's Degree and 0+ years of work experience.
About the organization
Not allowed heading. But we have About Us text. Could we put it under awithout heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but it suggests we should use those headings for sections. It might be okay to have a
for About Us without a heading. However, we might consider adding a heading "About the role" and include the About Us inside that? But that would mix location and employer description. Might be okay but could be confusing. Better: Keep About Us as a
after Qualifications, without a heading. The instruction says use
for prose. So we can have a
for About Us. Thus final HTML:
About the role
Primary Location: South Campus, Department: Population Health, Shift: Day (United States of America).
Schedule
Schedule: Full time, Weekly Hours: 40, FTE: 1, Employee Status: Regular.
Pay