Housekeeper

We need to output HTML fragment with sections as per content. The posting includes summary, job summary/purpose, department description, experience/education/qualifications, knowledge/skills/abilities, physical demands. No explicit pay, schedule, benefits. So we include sections: About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to appropriate headings. The posting includes job summary/purpose (could be About the role). Department description maybe part of About the role or Responsibilities? Experience/education/qualifications -> Requirements or Qualifications. Knowledge/skills/abilities -> Skills. Physical demands maybe part of Requirements? Could be separate but not listed as standard heading; we could include under Requirements or maybe a separate section like Physical Demands but not in list; but instruction says prefer few substantive sections over many thin ones. Could combine Physical demands into Requirements or Qualifications. However we must preserve all substantive info; we can include a subsection within a

or

. Probably best to have sections: About the role (summary + department description), Responsibilities (maybe from job summary/purpose?), Requirements (experience/education/qualifications), Skills (knowledge/skills/abilities), Physical Demands (maybe as part of Requirements but we could add a separate heading if content exists; but instruction says only include section when posting has real specific content for it. Physical demands is specific content, so we could include a section Physical Demands. However the allowed headings list didn't include Physical Demands but they gave examples; we can still use

for any heading; they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should stick to those headings; but we could also use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use those headings. It doesn't forbid other headings, but to be safe we map content to those headings. Physical demands could go under Requirements or Qualifications. Let's put under Requirements. Thus sections: About the role (job summary/purpose + department description). Responsibilities? The job summary/purpose includes cleaning, moving furniture etc. That's responsibilities. Could combine with About the role. But we need to avoid duplication. Perhaps About the role includes summary; Responsibilities includes duties. Let's split: About the role: brief overview of role purpose. Responsibilities: cleaning and sanitizing, moving furniture etc. Requirements: experience/education/qualifications + physical demands. Skills: knowledge/skills/abilities. We must not repeat job title as heading. No Job ID etc. We need to remove boilerplate: cookie/navigation/legal/EEO etc none present. We need to preserve all substantive info. Let's extract text. Summary: "Occasionally JOB SUMMARY/PURPOSECleans and sanitizes hospital and clinic building areas following established policies and procedures to maintain the environment in an orderly and sanitary condition. Moves furniture, equipment and supplies in and around hospital departments/buildings." Probably the "Occasionally" is stray; but we keep the sentences. Department description: "Environmental Services provides a professional, clean, safe, and sanitary environment for Samaritan Health Services in support of the health care mission. Services including cleaning and floor/carpet care, repairs, loans of tables/chairs and equipment, custodial services, linen distribution and waste removal." Experience/education/qualifications: "High school diploma or equivalent preferred. Minimum of one (1) year experience in a hospital / long term care setting / medical office preferred. Current valid Oregon driver's license preferred, but not required for all applicants.Note: Some work areas require the use of the employee's personal automobile. Employee must have a valid driver's license and auto liability/property damage insurance as required by law and must maintain their vehicle in good working order. If the employee is driving SHS vehicles, then successful completion of Drivers Privileges for SHS Vehicles application process required." Knowledge/skills/abilities: list of items each starting with a bold heading? We need to capture each bullet. List: Customer Service - Knowledge of principles and processes for providing customer service. This includes customer needs assessment, meeting quality standards for services and evaluation of customer satisfaction. Team Building - Ability to work, function and communicate on a multi-disciplinary team. Possess the knowledge and skills to develop constructive and cooperative working relationships with others and maintain them over time. Problem Solving - Ability to identify complex problems, review related information, employ creativity and alternative thinking to develop and evaluate options and implement solutions. Time Management - Ability to organize, plan and prioritize work to complete within required time frames and to follow-up on pending issues. Ability to perform multiple tasks simultaneously and thrive in dynamic fast-paced environments and under pressure. Confidentiality - Knowledge of State and Federal (HIPAA) laws pertaining to confidentiality of protected health information. Ability to comply with laws and maintain confidentiality of patient information. Stress Tolerance and Self Control - Ability to maintain patience and composure, control emotions, set clear boundaries and moderate high stress, difficult situations. Ability to respond quickly and appropriately and to adjust actions as needed to best meet the needs of the department and facility. Physical Demands: a table with categories and weight ranges. We need to preserve all that info. It's a bit messy with repeated lines. We need to extract the meaningful data: It lists various activities with frequency categories and weight ranges. We could present as a

with each line summarizing. But we must not invent or summarize away detail. We need to preserve all substantive information; we can list each item as
• with the description. Let's parse the physical demands section: It starts: "PHYSICAL DEMANDSRarely (1 - 10% of the time) (11 - 33% of the time) Frequently (34 - 66% of the time) Continually (67 - 100% of the time) LIFT (Floor to Waist: 0"-36") 40 - 60 Lbs LIFT (Overhead: 54" and above) 20 - 40 Lbs KNEEL (on knees) SIT CLIMB - STAIRS CLIMB - LADDER LIFT (Floor to Waist: 0"-36") 20 - 40 Lbs LIFT (Knee to chest: 24"-54") 0 - 20 Lbs CARRY 2-handed, 0 - 20 pounds SQUAT Static (hold >30 sec) SQUAT Repetitive ROTATE TRUNK Sitting ENTER & EXIT VEHICLE/MACHINERY STAND WALK - INCLINE LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs LIFT (Knee to chest: 24"-54") 40 - 60 Lbs LIFT (Overhead: 54" and above) 0 - 20 Lbs CARRY 1-handed, 0 - 20 pounds BEND FORWARD at waist REACH - Forward REACH - Upward PINCH Fingers GRASP Hand/Fist PUSH (40 - 60 pounds force) PULL (40 - 60 pounds force) WALK - LEVEL SURFACE ROTATE TRUNK Standing MANUAL DEXTERITY Hands/wrists FINGER DEXTERITY PUSH (0 - 20 pounds force) PULL (0 - 20 pounds force)" It seems like a list of activities with associated weight or frequency. The formatting is messed. We need to preserve all substantive info; we can output each distinct item as a
• . Let's try to split by capitalized words maybe. Better approach: keep the raw text as a

  preserving line breaks? But we need to use

  • for any list of duties/requirements/benefits. Physical demands is a list; we can use
    • . We'll need to parse items. Let's manually list items: - LIFT (Floor to Waist: 0"-36") 40 - 60 Lbs - LIFT (Overhead: 54" and above) 20 - 40 Lbs - KNEEL (on knees) - SIT - CLIMB - STAIRS - CLIMB - LADDER - LIFT (Floor to Waist: 0"-36") 20 - 40 Lbs - LIFT (Knee to chest: 24"-54") 0 - 20 Lbs - CARRY 2-handed, 0 - 20 pounds - SQUAT Static (hold >30 sec) - SQUAT Repetitive - ROTATE TRUNK Sitting - ENTER & EXIT VEHICLE/MACHINERY - STAND - WALK - INCLINE - LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs - LIFT (Knee to chest: 24"-54") 40 - 60 Lbs - LIFT (Overhead: 54" and above) 0 - 20 Lbs - CARRY 1-handed, 0 - 20 pounds - BEND FORWARD at waist - REACH - Forward - REACH - Upward - PINCH Fingers - GRASP Hand/Fist - PUSH (40 - 60 pounds force) - PULL (40 - 60 pounds force) - WALK - LEVEL SURFACE - ROTATE TRUNK Standing - MANUAL DEXTERITY Hands/wrists - FINGER DEXTERITY - PUSH (0 - 20 pounds force) - PULL (0 - 20 pounds force) Also there were frequency categories at start: Rarely (1 - 10% of the time) (11 - 33% of the time) Frequently (34 - 66% of the time) Continually (67 - 100% of the time). Those seem to be headers for frequency but not attached to specific items. Might be generic. We could include them as a

      preceding list. Thus physical demands section: a

      describing frequency categories, then

      list of items. Now compile HTML. We'll have:

      About the role

      Cleans and sanitizes hospital and clinic building areas following established policies and procedures to maintain the environment in an orderly and sanitary condition. Moves furniture, equipment and supplies in and around hospital departments/buildings. Environmental Services provides a professional, clean, safe, and sanitary environment for Samaritan Health Services in support of the health care mission. Services including cleaning and floor/carpet care, repairs, loans of tables/chairs and equipment, custodial services, linen distribution and waste removal.

      Responsibilities

      Cleans and sanitizes hospital and clinic building areas following established policies and procedures to maintain the environment in an orderly and sanitary condition. Moves furniture, equipment and supplies in and around hospital departments/buildings.

      But that duplicates About the role content. Better to combine: About the role includes summary and department description; Responsibilities maybe not needed. However we need to avoid thin sections. Could just have About the role and Responsibilities combined? But we need to follow instruction: use headings for sections when posting has real specific content. The posting has job summary/purpose and department description; we could treat job summary/purpose as About the role, department description as About the role as well. Respons