Travel Nurse RN - Med Surg - $3,594 per week

We need to output HTML fragment with sections for the job posting. The posting includes two jobs? Actually the text starts with "NuWest Travel Nursing is seeking a travel nurse RN Med Surg for a travel nursing job in Hammond, Indiana." Then there is a job description & requirements for Med Surg RN. Then after that, there is a second job: "Nurse Practitioner – Occupational Health". The user likely wants to reformat the job posting (maybe the second one?) The instruction: "You reformat a job posting into clean, well-structured semantic HTML." The provided text includes both jobs. Should we output both? Likely we need to output the whole posting, preserving all substantive info. We need to include sections only when there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. The page already shows it, so we don't add heading for job title. We need to include metadata like Job ID etc folded into short

or drop it. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to decide which job to format. The text includes two separate job postings. The first: travel nurse RN Med Surg. The second: Nurse Practitioner – Occupational Health. Likely they want the second one because they included details like responsibilities, requirements, benefits, etc. The first is brief: just specialty, discipline, duration, hours, shift, employment type. Not much else. Might still need to include. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine? However they are distinct jobs; mixing would be confusing. Probably they want to format the second posting (NP Occupational Health) because it has sections: Responsibilities, Requirements, Why NuWest? (Benefits), Pay package info, etc. The first is just a short line; maybe we can ignore as it's not substantive? But we must preserve ALL substantive information; do not invent or summarize away detail. So we must include the Med Surg RN info as well. Could treat as separate job postings within same HTML fragment, each with its own sections. But we cannot repeat job title as heading; we could use

for sections inside each job. But we need a way to separate jobs. Could use or but not required. The instruction only mentions using

for section headings,

• for lists,

  for prose. It doesn't forbid other tags like or . But to be safe, we can just output sequential sections for each job, using headings for sections within each job. However we need to avoid duplicate headings like "Responsibilities" for each job; that's okay as they are under different contexts. We need to include Pay and Schedule sections only if posting actually states them. For Med Surg RN: we have Duration: 11 weeks, 40 hours per week, Shift: 10 hours, days, Employment Type: Travel. That's schedule info. Pay not mentioned. So we can include Schedule section with those details. For NP Occupational Health: we have Schedule: Tuesdays - Friday (Mondays Off), Shift: 4x10, Days. Also Pay package based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. So we have Pay info (though stipend TBD). The instruction says: 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. For Pay, we have "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That includes TBD for stipend amount, but we still have some pay info (based on 10 hour shifts and 40 hours per week). Is that considered filler? It's not exactly TBD for the whole pay; it's stating the basis but stipend amount TBD. Might be okay to include Pay section with that sentence. However we must avoid placeholder like "TBD". The sentence includes "tax-free stipend amount to be determined." That's placeholder. Might be considered filler. Safer to omit Pay section? But we have some concrete info: based on 10 hour shifts and 40 hours per week. Could we include that as part of Schedule? Actually schedule already includes shift and hours. Pay could be omitted. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay package is based on... So we can include Pay section with that sentence, but we need to avoid filler like "to be determined". Could we rephrase? We cannot invent or summarize away detail. We must preserve ALL substantive information. So we must include that sentence exactly. It includes "to be determined". That's part of the posting. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "to be determined" is similar to TBD. So including that might violate. However the instruction is about headings followed by filler/placeholder text. If we put the Pay heading and then the sentence that includes "to be determined", is that considered filler? The sentence is not just filler; it contains substantive info plus placeholder. Hard to interpret. Safer to include Pay section but note that the sentence includes TBD; maybe it's acceptable because it's not solely filler. I'd include it. Benefits: The posting lists NuWest Benefits may include: Competitive weekly pay, Medical, dental, and vision insurance options, 401(k) retirement savings plan, Direct deposit, Referral bonuses, Personalized support, Credentialing and compliance support, Housing and travel assistance, Exclusive healthcare job opportunities nationwide, 24/7 support. So we have Benefits section. Schedule: we have Shift: 4x10, Days; Schedule: Tuesdays - Friday (Mondays Off). So we can include Schedule section. Responsibilities: list. Requirements: list. About the role: maybe we can include a short paragraph summarizing the role from the initial description: "NuWest Travel Nursing & Allied Health is seeking an experienced Nurse Practitioner (NP)/Physician Assistant (PA) to join a healthcare team in an Occupational Health setting. This is an excellent opportunity for a provider who enjoys a collaborative environment, preventative care, employee wellness, and treating work-related injuries and illnesses." That's prose. We also have Position Details: Specialty: Occupational Health, Profession: Nurse Practitioner, Setting: Occupational / Employee Health, Start Date: ASAP. Could be part of About the role or separate section like "Position Details". But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Qualifications could be used for licensure/certification etc. Requirements could be for experience. We need to map. We have Requirements: Active NP license, National Board Certification, Current BLS, Occupational Health experience preferred, Strong assessment etc. That's requirements. Qualifications could be for education? Not given. Could omit Qualifications if no content. Skills: maybe we can include strong assessment, communication, clinical decision-making skills etc. But those are already in Requirements. Better to put them under Requirements. We need to avoid creating sections with no content. So we will include: About the role (prose from Position Details and intro), Responsibilities (ul), Requirements (ul), Benefits (ul), Pay (p), Schedule (p). Possibly also include Job ID etc folded into short p. We must not repeat job title as heading. So no heading for "Nurse Practitioner (NP) / Physician Assistant (PA) – Occupational Health". We'll start with About the role. We need to remove boilerplate: "Why NuWest?" is basically Benefits; we already have Benefits. The "Why NuWest?" heading is not in allowed list, but we can treat its content as Benefits. We'll not include heading "Why NuWest?". We need to remove duplicated lines, application instructions, cookie/navigation/legal/EEO etc. There's none. We need to include Job ID etc folded into short p or drop it. We'll include a short p at end: "Job ID #289113." Now for Med Surg RN job: we have minimal info. Could we include a separate section for that job? The instruction says "Prefer a few substantive sections over many thin ones." The Med Surg RN job has very little content; maybe we can omit it because it's not substantive? But we must preserve ALL substantive information. The Med Surg RN posting includes: Specialty: Med Surg, Discipline: RN, Duration: 11 weeks, 40 hours per week, Shift: 10 hours, days, Employment Type: Travel. That's substantive. We could include a short About the role paragraph and Schedule section. But we already have sections for the NP job; adding another job's sections would duplicate headings (About the role, Schedule). That could be confusing but permissible if we separate with maybe or . However the instruction didn't forbid multiple jobs; just said reformat a job posting. The text includes two job postings; maybe they expect us to format both. Let's do both, each within its own (or ) to keep them distinct. Use

  for section headings inside each. We must not repeat job title as heading; we can rely on the context that each section belongs to a job implied by preceding paragraph? Could add a for job title? Not allowed. The instruction says do NOT repeat the job title as a heading (the page already shows it). So we should not add any heading for job title. So we need to convey which job each section belongs to without a heading. Could we rely on ordering? The first chunk is Med Surg RN, second is NP Occupational Health. We'll just output sections sequentially; the reader can infer. Thus output:

  NuWest Travel Nursing is seeking a travel nurse RN Med Surg for a travel nursing job in Hammond, Indiana.

  Specialty: Med Surg
  Discipline: RN
  Duration: 11 weeks
  40 hours per week
  Shift: 10 hours, days
  Employment Type: Travel

  Job ID #289113.

  But we need to use

  • for any list of duties/requirements/benefits. The above is not a list; it's key-value pairs. Could we turn them into
    • ? The instruction: Use
      • for any list of duties/requirements/benefits. For other prose, use

        . The specialty etc is not a list of duties/requirements/benefits, it's metadata. Could be presented as

        with line breaks (
        ) or separate

        sentences. We'll keep as

        . Now for NP job:

        NuWest Travel Nursing & Allied Health is seeking an experienced Nurse Practitioner (NP)/Physician Assistant (PA) to join a healthcare team in an Occupational Health setting. This is an excellent opportunity for a provider who enjoys a collaborative environment, preventative care, employee wellness, and treating work-related injuries and illnesses.

        Position Details: Specialty: Occupational Health; Profession: Nurse Practitioner; Setting: Occupational / Employee Health; Start Date: ASAP.

        Responsibilities

        • Provide comprehensive occupational health services to employees and/or patients.
        • Evaluate and treat work-related injuries and illnesses.
        • Perform physical examinations, health assessments, and follow-up