Tech Purchasing

We need to output HTML fragment with sections: About the role? The description includes a paragraph about UNC Health etc. That could be "About the role" or maybe "Summary". 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. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. We need to parse the posting. Content: Description: "Your passion belongs at UNC Health. Join more than 56,000 teammates working together to improve the health and well-being of the communities we serve across North Carolina. UNC Health Nash, an affiliated member of the UNC Health system, invites passionate healthcare professionals to join our esteemed team. Governed locally, we proudly serve a diverse patient base, spanning Nash, Edgecombe, Halifax, Wilson Counties, and beyond. With a steadfast commitment to elevating community health through exceptional care, we prioritize excellence, compassion, and innovation, ensuring every individual receives the highest standard of support. Joining our team means becoming an integral part of our dedication to wellness, where we constantly strive to redefine excellence in healthcare through state-of-the-art facilities and pioneering programs. Join us in this transformative journey, where your contributions will make a lasting impact on our community's health and wellbeing." That's about the organization, could be "About the role" or maybe "About UNC Health". The instruction says use headings like About the role, Responsibilities, etc. So we can use "About the role" heading for that paragraph. Then "Summary Places orders for stock and non-stock hospital supplies, and prepares associated purchase orders." That's a summary sentence. Could be part of "Summary" section? The instruction list includes "Summary" not explicitly but they gave examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Summary but we could treat it as part of About the role or maybe a separate "Summary". However they said "include a section ONLY when the posting has real, specific content for it". There is a summary sentence. Could we put it under "About the role"? Might be okay. But we could also create a "Summary" heading if we think it's appropriate. The examples didn't include Summary but they said "e.g." meaning examples, not exhaustive. So we could add a Summary section. But we need to avoid thin sections. The summary is just one sentence; maybe combine with About the role. Responsibilities: list bullet points: - Places orders for new stock and non-stock items, and performs associated documentation and file maintenance. - Communicates and coordinates with vendors, sales representatives and hospital management personnel to facilitate the purchasing process. - Performs a variety of secretarial, clerical and operational support functions for the department. - Acquires age-specific knowledge necessary to provide appropriate level of service and communications. - Participates in maintaining designated equipment and work areas. - Performs other duties as needed. - Takes an active role in self development. These are duties; we can put under

  Responsibilities

  with
  • . Other Information: Education Requirements: High school graduate or GED. Licensure/Certification Requirements None Professional Experience Requirements 1 year of experience in Operations - Procurement - Operations-Procurement General or related position. Purchasing experience in a health system. Above plus proficient in the use of word processing software. Knowledge of purchasing procedures, medical and surgical products and basic accounting procedures preferred. Proficient in the use of keyboard and basis computer applications. Proficient in use of calculator. We need to decide sections: Requirements, Qualifications, Skills. The instruction gave examples: Requirements, Qualifications, Skills. We need to map content. Education Requirements -> could be under Requirements or Qualifications. Licensure/Certification Requirements None -> maybe we should not include a section if it's None (no content). Since it's None, we should not create a section for it because it's filler. So we omit. Professional Experience Requirements -> could be under Requirements. "Above plus proficient in the use of word processing software." That's a skill. "Knowledge of purchasing procedures, medical and surgical products and basic accounting procedures preferred." That's a qualification/skill. "Proficient in the use of keyboard and basis computer applications." Skill. "Proficient in use of calculator." Skill. We could combine into a Skills section (list). Or we could have Requirements (education + experience) and Skills (software, knowledge, etc.). Qualifications maybe similar to Requirements. But we need to avoid thin sections. Let's see. We have education: high school graduate or GED. Experience: 1 year of experience in Operations - Procurement - Operations-Procurement General or related position. Purchasing experience in a health system. That's two bullet points. Skills: proficient in word processing software; knowledge of purchasing procedures, medical and surgical products and basic accounting procedures preferred; proficient in keyboard and basic computer applications; proficient in use of calculator. We could make a Skills section with those bullet points. We could also have a Requirements section that includes education and experience. Qualifications maybe not needed separately. We also have Job Details: Legal Employer: Nash Hospitals Entity: Nash UNC Health Care Organization Unit: NGH Purchasing Work Type: Full Time Standard Hours Per Week: 40.00 Work Assignment Type: Onsite Work Schedule: Day Job Location of Job: NASH HC Exempt From Overtime: Exempt: No We need to decide if we include Pay, Schedule, Benefits sections. The posting includes Work Schedule: Day, Standard Hours Per Week: 40.00, Work Type: Full Time, Work Assignment Type: Onsite. That's schedule info. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule (Day, 40 hours/week, Full Time, Onsite). So we could include a Schedule section. However we need to avoid filler like "not specified". This is specific. We could include Schedule section with those details as a

    or

    . The instruction: Use
    • for any list of duties/requirements/benefits, and

      for prose. Schedule is not a list but could be prose. We'll put

      . Similarly, Benefits: not mentioned. So we omit Benefits. Pay: not mentioned. Omit Pay. We also have "Exempt From Overtime: Exempt: No". That's also schedule/employment detail; could be included in Schedule section. Job Location: NASH HC. Could be included in Schedule or maybe a separate "Location" but not in examples. Could fold into Schedule or About the role? Probably better to include in Schedule section as part of details. Legal Employer etc. Could be minor metadata; we could fold into a short

      under About the role or maybe a separate "About the role" already includes organization description; we could add a short paragraph with those details. But we must not repeat job title as heading; we don't have job title. We need to remove EEO boilerplate: "Qualified applicants will be considered without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, genetic information, disability, status as a protected veteran or political affiliation." That's EEO; remove. Also remove duplicated lines. Now produce HTML fragment. Structure:

      About the role

      Your passion belongs at UNC Health. Join more than 56,000 teammates working together to improve the health and well-being of the communities we serve across North Carolina. UNC Health Nash, an affiliated member of the UNC Health system, invites passionate healthcare professionals to join our esteemed team. Governed locally, we proudly serve a diverse patient base, spanning Nash, Edgecombe, Halifax, Wilson Counties, and beyond. With a steadfast commitment to elevating community health through exceptional care, we prioritize excellence, compassion, and innovation, ensuring every individual receives the highest standard of support. Joining our team means becoming an integral part of our dedication to wellness, where we constantly strive to redefine excellence in healthcare through state-of-the-art facilities and pioneering programs. Join us in this transformative journey, where your contributions will make a lasting impact on our community's health and wellbeing.

      Maybe also include summary sentence: "Places orders for stock and non-stock hospital supplies, and prepares associated purchase orders." Could be added to About the role or separate Summary. Let's add a short paragraph after the about. Alternatively, we could create a Summary section with that sentence. Since it's specific, we can do that. But we need to avoid thin sections; a one-sentence Summary is thin but still specific. The instruction says prefer a few substantive sections over many thin ones. So maybe combine summary into About the role. Thus About the role paragraph will include the summary sentence at end. Now Responsibilities.

      Responsibilities

      • Places orders for new stock and non-stock items, and performs associated documentation and file maintenance.
      • Communicates and coordinates with vendors, sales representatives and hospital management personnel to facilitate the purchasing process.
      • Performs a variety of secretarial, clerical and operational support functions for the department.
      • Acquires age-specific knowledge necessary to provide appropriate level of service and communications.
      • Participates in maintaining designated equipment and work areas.
      • Performs other duties as needed.
      • Takes an active role in self development.
      Now Requirements (education + experience). Could be

      Requirements

      with
      .
      • High school graduate or GED.
      • 1 year of experience in Operations - Procurement - Operations-Procurement General or related position.
      • Purchasing experience in a health system.
      That's three. Now Skills.

      Skills

      • Proficient in the use of word processing software.
      • Knowledge of purchasing procedures, medical and surgical products and basic accounting procedures preferred.
      • Proficient in the use of keyboard and basic computer applications.
      • Proficient in use of calculator.
      Now Schedule.

      Schedule

      Full-time position (40 hours per week), day shift, onsite work at NASH HC. Not exempt from overtime.

      We could also include Legal Employer etc. Could be added as a short paragraph under About the role or maybe a separate "Details" but not needed. We should preserve all substantive information: we have included education, experience, skills, responsibilities, schedule. We omitted Licensure/Certification Requirements None (since it's None). We omitted EEO. We omitted duplicated lines. We omitted "Job Details" like Legal Employer, Entity, Organization Unit, Work Type, Standard Hours Per Week, Work Assignment Type, Work Schedule, Job Location, Exempt From Overtime. We captured many of those in Schedule paragraph but we missed Legal Employer, Entity, Organization Unit. Are those substantive? They are metadata about the employer. The instruction says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop