Family Medicine Nurse Practitioner (CNP/APRN) or Physician Assistant (PA)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, accommodation, etc. Must preserve all substantive info. We need to parse the description. Content: - "What We're Looking For" paragraph: description of role, ideal candidate traits. Could be "About the role" maybe. - "Essential Job Duties": list of duties. - "What We Offer": bullet list of benefits etc. - Then "Protecting Your Future": list of benefits (medical, dental, vision insurance, 403(b) retirement plan, employer-paid life insurance, employer-paid long-term disability). This is also benefits. - Then "Third Street is an equal opportunity employer..." boilerplate to remove. - Then "If you require reasonable accommodation..." remove. - Then "Requirements Qualifications Required": list of required qualifications. - Then "Preferred": list of preferred qualifications. - Then "About Us": description of organization. - Then "Organizational Information": details. - Then "Mission": statement. We need to decide sections. Possible sections: - About the role (maybe from "What We're Looking For"). - Responsibilities (Essential Job Duties). - Qualifications (Required and Preferred). Could split into Requirements and Qualifications? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Requirements and Qualifications? Probably separate: Requirements (required qualifications) and Qualifications (preferred?). But they said "Requirements, Qualifications". Might treat Requirements as required, Qualifications as preferred or skills. Also Skills could be separate if there are skill items. We have "Bilingual or multilingual skills, particularly Spanish, preferred." That's a skill. We also have "Experience with electronic health records (EHRs) and documentation in a high-volume primary care environment." That's a skill/experience. We could put skills under Skills section. Benefits: we have "What We Offer" and "Protecting Your Future". Combine into Benefits. Pay: Not mentioned explicitly except "Competitive Market Value Compensation." That's pay info. So we can include Pay section with that line. Schedule: Not mentioned. So omit. We must not create sections with filler like "not specified". So only include sections with real content. Thus sections: - About the role (from "What We're Looking For"). - Responsibilities (Essential Job Duties). - Requirements (Required qualifications). - Qualifications (Preferred qualifications). - Skills (maybe bilingual, EHR experience). Could also include under Qualifications but we have separate Skills heading allowed. We'll put relevant skill items. - Benefits (What We Offer + Protecting Your Future). - Pay (Competitive Market Value Compensation). We must not repeat job title. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate: EEO, accommodation request, etc. Also remove duplicated lines? Not seeing duplicates. We must not include navigation, legal, etc. Now craft HTML. First, About the role: prose from "What We're Looking For". Let's extract: "What We're Looking For Are you a proactive problem-solver who takes pride in delivering meaningful work that makes a lasting impact? We're looking for a driven and detail-oriented professional to join our team as a Family Medicine Nurse Practitioner (CNP/APRN) or Physician Assistant (PA). In this role, you'll play a vital part in providing expert medical care to patients of all ages with a range of potential illnesses, injuries, or disabilities, helping us move forward with purpose and precision. The ideal candidate values continuous learning, leads with a welcoming spirit, takes ownership of their work, and is passionate about supporting people and building stronger communities." We need to keep that as prose in

  . Next Responsibilities: list of duties from "Essential Job Duties". Each bullet. List: - Provide comprehensive primary care services to patients of all ages, including diagnosing and treating acute and chronic illnesses, managing chronic conditions, and promoting preventive health. - Conduct thorough medical assessments, including taking detailed medical histories, performing physician examinations, ordering, and interpreting laboratory tests and diagnostic imaging, and making accurate diagnoses. - Develop and implement evidence-based treatment plans for patients, including prescribing medications, providing counseling on lifestyle modifications, and coordinating referrals to specialists when needed. - Collaborate with interdisciplinary teams, including nurses, physicians, behavioral health providers, and other healthcare professionals to ensure comprehensive and coordinated care for patients. - Provide culturally sensitive care to diverse patient populations, respecting their cultural, religious, and social beliefs, and addressing health disparities. - Serve as an advocate for patients, promoting their rights and assisting them in navigating the healthcare system, including obtaining insurance coverage and accessing community resources. - Be a positive role model for all health center staff. We'll put each as

• . Next Requirements (Required qualifications): list: - Current, unrestricted Ohio licensure as a Certified Nurse Practitioner (CNP/APRN) or Physician Assistant (PA). - Board Certified or eligible for board certification, with expectation of obtaining certification within one year. - Valid Driver’s License. We'll put as
  . Next Qualifications (Preferred): list: - Previous experience providing primary care in a Federally Qualified Health Center (FQHC), community health center, or other safety-net healthcare setting. - Experience providing comprehensive primary care to patients across the lifespan. - Experience caring for medically underserved and diverse patient populations. - Familiarity with integrated, team-based care and collaboration with physicians, nursing, behavioral health, dental, pharmacy, and other care team members. - Experience managing chronic health conditions, preventive care, and routine acute-care needs in a primary care setting. - Familiarity with quality measures, population health, and value-based care. - Experience with electronic health records (EHRs) and documentation in a high-volume primary care environment. - Bilingual or multilingual skills, particularly Spanish, preferred. We could split skills: bilingual/multilingual skills and EHR experience maybe go to Skills section. But we already have them in preferred list. Could keep them under Qualifications. However we have a Skills heading allowed; we could move those two items to Skills. But we must not lose any info. Let's decide: We'll keep Qualifications for experience/familiarity items, and Skills for bilingual/multilingual and EHR experience. However EHR experience is also a qualification/experience; but we can treat as skill. Let's parse: Preferred list includes many items; we can separate: Qualifications (Preferred experience/familiarity): - Previous experience providing primary care in a Federally Qualified Health Center (FQHC), community health center, or other safety-net healthcare setting. - Experience providing comprehensive primary care to patients across the lifespan. - Experience caring for medically underserved and diverse patient populations. - Familiarity with integrated, team-based care and collaboration with physicians, nursing, behavioral health, dental, pharmacy, and other care team members. - Experience managing chronic health conditions, preventive care, and routine acute-care needs in a primary care setting. - Familiarity with quality measures, population health, and value-based care. Skills: - Experience with electronic health records (EHRs) and documentation in a high-volume primary care environment. - Bilingual or multilingual skills, particularly Spanish, preferred. That seems reasonable. Now Benefits: combine "What We Offer" and "Protecting Your Future". What We Offer list: - Attending to your needs today: Your ideas, input, and contributions are valued and recognized. - Excellent clinical, administrative, and management support. - Forward-thinking, collaborative, transparent, and inclusive company culture. - Employee Assistance Program. - Competitive Medical, Dental, and Vision plans. - Competitive Market Value Compensation. (But we will move compensation to Pay section; maybe keep here? Better to move to Pay.) - Generous Paid Time Off. - Tuition assistance. Protecting Your Future list: - Medical, dental and vision insurance - 403(b) retirement plan - Employer-paid life insurance - Employer-paid long-term disability Note there is overlap: Competitive Medical, Dental, and Vision plans vs Medical, dental and vision insurance. Might be duplicate but we should preserve all substantive info; we can keep both but maybe combine to avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we combine, we might lose nuance. Safer to keep both as separate items even if similar. However we should avoid duplicated lines? The instruction says remove duplicated lines. So if they are essentially same, we should deduplicate. "Competitive Medical, Dental, and Vision plans." vs "Medical, dental and vision insurance". They are similar but not identical wording; one says competitive plans, the other says insurance. Could be considered duplicate in meaning. Might be safer to keep both? The instruction says remove duplicated lines. I'd interpret that as exact duplicate lines. These are not exact duplicates. So we can keep both. But we also have "Competitive Market Value Compensation." which we will move to Pay. Thus Benefits list items: - Attending to your needs today: Your ideas, input, and contributions are valued and recognized. - Excellent clinical, administrative, and management support. - Forward-thinking, collaborative, transparent, and inclusive company culture. - Employee Assistance Program. - Competitive Medical, Dental, and Vision plans. - Generous Paid Time Off. - Tuition assistance. - Medical, dental and vision insurance - 403(b) retirement plan - Employer-paid life insurance - Employer-paid long-term disability Now Pay section: "Competitive Market Value Compensation." We could also include maybe nothing else. Now About Us etc: Should we include About Us as a section? The allowed headings list does not include About Us, but we could put under About the role? However we have substantive info about organization: "About Us", "Organizational Information", "Mission". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not list About Us or Organizational Information. But we could incorporate that info under About the role? However About the role is supposed to be about the role, not the organization. The instruction says "Prefer a few substantive sections over many thin ones." It also says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list; we could add other headings if needed? But they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; maybe we shouldn't invent other headings. However we have organization info that is substantive; we could incorporate into About the role or maybe under a heading like "About the Organization" but that's not in the list. Safer to incorporate into About the role? But that might be mixing. Alternatively we could create a section "About the Organization" using

  even though not listed; risk of violating instruction? The instruction says use those headings for section headings (e.g...). It doesn't forbid other headings, but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings; but they also say "Prefer a few substantive sections over many thin ones." So we could combine organization info into About the role or maybe under a heading "About Us" but that's not in list; risk. Better to follow