Sourcing and Contracts Specialist

We need to output HTML fragment with headings

for sections: 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. Must preserve all substantive info, no invented details. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not include sections with filler like "commensurate with experience". Must only include sections if posting has real specific content. We need to parse the posting. Content: - Who We Are: description of JPS Health Network, Acclaim Multispecialty Group, mission, values. This could be "About the role"? Actually "About the role" is about the job, not the organization. But we have "Who We Are" which is about the organization. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if appropriate. "About the role" could be used for a summary of the job. The posting includes "Job Summary:" which is about the role. So we can put that under

About the role

. - Responsibilities: The "Essential Job Functions & Accountabilities" list is responsibilities. So we can put under

Responsibilities

with

• items. - Requirements: There's "Required Qualifications:" and "Preferred Qualifications:" which are qualifications. Could be under

  Qualifications

  . Also there is "Location Address:" maybe not needed as heading; could be in a

  under Qualifications or separate? The instruction says we can include sections only when posting has real specific content. Location is specific but not one of the listed headings; we could embed in a

  maybe under Qualifications or as a separate

  not under a heading. The instruction says use headings for those categories; we can also have

  for prose. So we can include location in a

  after qualifications. - Skills: Not explicitly listed; maybe we can infer from responsibilities but not explicit. Should not create a Skills section unless posting actually states them. The posting does not have a separate "Skills" bullet list. So we should not include Skills section. - Benefits, Pay, Schedule: The posting mentions "Compensation Type Salaried", "Hours Worked 8:00AM - 5:00PM", "Hybrid Location", "Shift Worked Day". That gives some info about schedule and pay type but not specific salary amount. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". For Pay, we have "Compensation Type Salaried" which is specific (salaried). That is actual content. For Schedule, we have "Hours Worked 8:00AM - 5:00PM", "Hybrid Location", "Shift Worked Day". That's specific schedule info. Benefits: not mentioned. So we can include Pay and Schedule sections if they have real specific content. Benefits: no mention, so omit. Thus we will have sections: About the role, Responsibilities, Qualifications, Pay, Schedule. Possibly also include a short paragraph for location under Qualifications or as its own

  not under heading. But we could also include location under Qualifications as a

  . 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." So we can have

    for prose like location. We must not repeat the job title as heading. The job title is "Sourcing and Contracts Specialist". We must not put that as heading. We must not put Job ID/requisition numbers as headings; we can drop them. We must remove boilerplate: "Who We Are" etc we keep as content but not as heading? Actually "Who We Are" is a heading in the original but we are not to use that as a heading unless it matches one of the allowed headings. It doesn't match exactly; we could incorporate that prose into About the role or maybe a separate

    but not as a heading. The instruction says to use those headings for sections; we can still have other headings? It says 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; we could also have other headings but better to stick to those. So we can transform "Who We Are" content into a

    under About the role or maybe a separate

    not under heading. But we need to preserve all substantive information. So we can include that description in a

    under About the role (maybe after job summary). Or we could have a separate

    not under heading but that's okay. Let's structure:

    About the role

    Job Summary: The Sourcing and Contracts Specialist leads procurement optimization by sourcing high-quality products and services at competitive prices while ensuring compliance with healthcare regulations and organizational policies. This position is responsible for managing the entire contract life cycle to include vendor relationships, negotiating contracts, and supporting strategic sourcing initiatives to enhance cost efficiency and operational effectiveness across the health system.

    Who We Are: JPS Health Network is a $950 million, tax-supported healthcare system in North Texas. Licensed for 582 beds, the network features over 25 locations across Tarrant County, with John Peter Smith Hospital a Level I Trauma Center, Tarrant County's only psychiatric emergency center, and the largest hospital-based family medical residency program in the nation. The health network employs more than 7,200 people. Acclaim Multispecialty Group is the medical practice group featuring over 300 providers serving JPS Health Network. Specialties range from primary care to general surgery and trauma. The Acclaim Multispecialty Group formed around a common set of incentives and expectations supporting the operational, financial, and clinical performance outcomes of the network. Our goal is to provide high quality, compassionate clinical care for every patient, every time. Why JPS? We're More Than a Hospital. We're 7,200 Of The Most Dedicated People You Could Ever Meet. Our Goal Is To Make Sure The People Of Our Community Get The Care They Need And Deserve. As Community Stewards, We Abide By Three Rules Of The Road Own it. Everyone who wears the JPS badge contributes to our journey to excellence. Seek joy. Every day, every shift, we celebrate our patients, smile, and emphasize positivity. Don't be a jerk. Everyone is treated with courtesy and respect. Smiling, laughter, compassion - key components of our everyday experience at JPS. When working here, you're surrounded by passion, diversity, and dedication. We look forward to meeting you! For more information, visit www.jpshealthnet.org . To view all job vacancies, visit www.jpshealthnet.org , www.jpshealthnet.org/careers , or www.teamacclaim.org .

    But we need to remove application instructions and duplicated lines. The "For more information, visit ..." and "To view all job vacancies..." are likely application instructions/boilerplate; we should remove them. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should cut out those lines. So we keep the Who We Are description but not the "For more information..." lines. Thus About the role section will have job summary paragraph and then a paragraph about the organization (without the application lines). We'll need to ensure we removed duplicated lines: there is duplicate "www.jpshealthnet.org" appears twice; we can keep one mention? But it's part of the application instruction; better to remove entirely. Thus About the role: two

    elements: one for Job Summary, one for Who We Are (without the visit lines). Let's extract Who We Are content up to "We look forward to meeting you!" and stop before "For more information". The original: "Who We Are JPS Health Network is a $950 million, tax-supported healthcare system in North Texas. Licensed for 582 beds, the network features over 25 locations across Tarrant County, with John Peter Smith Hospital a Level I Trauma Center, Tarrant County's only psychiatric emergency center, and the largest hospital-based family medical residency program in the nation. The health network employs more than 7,200 people. Acclaim Multispecialty Group is the medical practice group featuring over 300 providers serving JPS Health Network. Specialties range from primary care to general surgery and trauma. The Acclaim Multispecialty Group formed around a common set of incentives and expectations supporting the operational, financial, and clinical performance outcomes of the network. Our goal is to provide high quality, compassionate clinical care for every patient, every time. Why JPS? We're More Than a Hospital. We're 7,200 Of The Most Dedicated People You Could Ever Meet. Our Goal Is To Make Sure The People Of Our Community Get The Care They Need And Deserve. As Community Stewards, We Abide By Three Rules Of The Road Own it. Everyone who wears the JPS badge contributes to our journey to excellence. Seek joy. Every day, every shift, we celebrate our patients, smile, and emphasize positivity. Don't be a jerk. Everyone is treated with courtesy and respect. Smiling, laughter, compassion - key components of our everyday experience at JPS. When working here, you're surrounded by passion, diversity, and dedication. We look forward to meeting you!" We'll keep that as a paragraph. Now Responsibilities: list of essential job functions. We'll convert each bullet to

  • . We need to ensure we don't include the line "Job description is not an all-inclusive list of duties and may be subject to change with or without notice. Staff are expected to perform other duties as assigned." That's boilerplate; we should remove it. Thus Responsibilities
    with items from the list. Now Qualifications: we have Required Qualifications and Preferred Qualifications. We'll combine into a
    maybe separate

    for required and preferred? The instruction says use

    • for any list of duties/requirements/benefits. So we can make a
      for qualifications. Could separate required and preferred with headings? Not allowed; we can just list all qualifications as
      • items, maybe marking required vs preferred in text. But we need to preserve all substantive information; we can include both required and preferred as separate

        paragraphs with

        inside? Simpler: have a

        for Required Qualifications: then

        list; then a

        for Preferred Qualifications: then

        list. That's okay because headings are not required for those; we can use

        for prose. We also have Location Address: we can include as a

        after qualifications. Now Pay: we have "Compensation Type Salaried". Also maybe "Employment Type Full Time". That's about pay type. We'll put in a

        under Pay section: "Compensation Type: Salaried. Employment Type: Full Time." Schedule: we have "Hours Worked 8:00AM - 5:00PM", "Hybrid Location: John Peter Smith Hospital", "Shift Worked Day". We'll put in a

        under Schedule: "Hours Worked: 8:00AM - 5:00PM. Hybrid Location: John Peter Smith Hospital