Travel Wound Ostomy RN - $2,412 per week

We need to output HTML fragment with sections: maybe About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Let's parse the posting: - Title: Access Healthcare is seeking a travel nurse RN Wound Care for a travel nursing job in Boston, Massachusetts. - Job Description & Requirements: Specialty: Wound Care Discipline: RN Duration: 13 weeks 40 hours per week Shift: 10 hours, days Employment Type: Travel Required CWOCN or CWON certification Access Healthcare Job ID #5-MGB-29775. Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - About Access Healthcare: paragraph about agency. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to format sections: Use

for section headings. We need to decide which sections have content. Potential sections: - About the role: Could include description of role: travel nurse RN Wound Care in Boston, 13 weeks, 40 hrs/week, 10 hour day shifts, travel employment type, required certification. - Responsibilities: Not explicitly listed. Could be implied but not given. We should not create a section without real specific content. So skip Responsibilities if not present. - Requirements: Could include required CWOCN or CWON certification, RN discipline, wound care specialty, maybe location Boston, duration 13 weeks, shift details. But these are more job details. Could put under "Requirements". However we need to ensure we don't duplicate. - Qualifications: maybe same as requirements. - Skills: Not specified. - Benefits: The posting mentions "competitive pay packages and an unmatched benefits package!" but no specific benefits listed. It says "we offer a true family feel..." but not specific benefits like health insurance, 401k, etc. Since no specific benefits listed, we should not create Benefits section (as per rule: never create Benefits unless posting actually states them). The phrase "unmatched benefits package" is vague, not specific. So skip. - Pay: The posting says "Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's somewhat vague but includes some info: based on 10 hour shifts, 40 hrs/week, tax-free stipend to be determined. It's not a specific number, but it's still some content. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "tax-free stipend amount to be determined" which is TBD-like. Also "subject to confirmation". This might be considered placeholder. The rule says avoid filler/placeholder text. So maybe we should not include Pay section because it's not specific. However we could include the statement as is? It says "Pay package is based on 10 hour shifts and 40 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's not a specific number, but it's still some info. The rule says do not include heading if content is filler/placeholder like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Tax-free stipend amount to be determined" is similar to TBD. So better to skip Pay. - Schedule: The posting says Shift: 10 hours, days; 40 hours per week. That's specific schedule info. So we can include Schedule section. - About Access Healthcare: Could be "About the company" but we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company" heading. However we could put the About Access Healthcare paragraph under "About the role"? Might be misfit. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exhaustive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. The About Access Healthcare paragraph is about the company, not the role. Could we put it under "About the role"? Might be okay but it's not exactly about the role. However we could treat it as "About the role" includes info about the employer? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include a short paragraph about the company under "About the role" or maybe we could create a custom heading? But the instruction says use those headings for section headings. It doesn't forbid other headings, but says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we need to map content to those headings. Thus: - About the role: Could include description: Access Healthcare is seeking a travel nurse RN Wound Care for a travel nursing job in Boston, Massachusetts. Specialty: Wound Care, Discipline: RN, Duration: 13 weeks, 40 hours per week, Shift: 10 hours, days, Employment Type: Travel, Required CWOCN or CWON certification. Also maybe mention Job ID? Should fold minor metadata into a short

or drop it. Job ID is minor metadata; we can include in a short

maybe under About the role. - Requirements: Could list required certification (CWOCN or CWON), RN license, wound care specialty, maybe ability to work 10 hour day shifts, 40 hrs/week, travel. But some of that overlaps with About the role. We need to avoid duplication but can still include specifics. - Schedule: Include shift details: 10 hour days, 40 hours per week. - Pay: Might skip due to vague. - Benefits: skip. - Qualifications: maybe same as Requirements; but we could combine. We need to avoid thin sections. Prefer few substantive sections over many thin ones. So maybe we have About the role, Requirements, Schedule. That's three sections. Let's craft content: About the role: paragraph describing the job: Access Healthcare is seeking a travel nurse RN Wound Care for a travel nursing job in Boston, Massachusetts. Specialty: Wound Care, Discipline: RN, Duration: 13 weeks, 40 hours per week, Shift: 10 hours, days, Employment Type: Travel. Also mention Job ID #5-MGB-29775 as minor metadata maybe in a short

. Requirements: list: Current RN license, CWOCN or CWON certification, experience in wound care, ability to work 10-hour day shifts, 40 hours per week, travel assignment. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot add "experience in wound care" if not stated. The posting says Required CWOCN or CWON certification. It also says Specialty: Wound Care, Discipline: RN. So we can infer that they want RN with wound care specialty. But we should not invent experience. So we can list: RN license, CWOCN or CWON certification, wound care specialty. Also maybe mention location Boston, Massachusetts. But location is part of About the role. Schedule: list: 10-hour day shifts, 40 hours per week. We need to use

• for any list of duties/requirements/benefits. So for Requirements we can use
  • . For Schedule maybe also list? It's not a list of duties but could be a list. Use
    • for any list of duties/requirements/benefits. Schedule is not duties/requirements/benefits but it's a list of schedule items; we could still use
      • but maybe better to use

        . The rule: Use

        • for any list of duties/requirements/benefits, and

          for prose. So schedule is not duties/requirements/benefits, but it's still a list; but we could use

          with commas. Safer to use

          . Thus:

          About the role

          Access Healthcare is seeking a travel nurse RN Wound Care for a travel nursing job in Boston, Massachusetts. Specialty: Wound Care; Discipline: RN; Duration: 13 weeks; 40 hours per week; Shift: 10 hours, days; Employment Type: Travel.

          Job ID: #5-MGB-29775.

          Requirements

          • Active RN license
          • CWOCN or CWON certification
          • Wound care specialty

          Schedule

          10‑hour day shifts, 40 hours per week.

          We should not include Pay/Benefits etc. Check for any other substantive info: The About Access Healthcare paragraph: "Access Healthcare aims to provide superior service to our nursing family by providing around the clock support, competitive pay packages and an unmatched benefits package! Unlike other agencies, we offer a true family feel and work with you to find the placement that is right for you. We offer one of the top leading pay packages in the industry and we are ready to get you the money you deserve! Access Healthcare was founded by two travel nurses, Danielle and Diego, who had a dream and a shared vision of creating an agency which all nurses would want to work with. Our passion has led us to where we are today as one of the top 10 agencies in our home state of New Jersey, with access to contracts in all 50 states! We encourage you to join our team and we cannot wait to get to know you!" This is substantive but not fitting under the prescribed headings. Could we put it under "About the role"? It's about the company, not the role. But maybe we can treat it as "About the role" includes info about employer. However the instruction says "About the role" is an example heading; we could also use "About the company" but not listed. The instruction says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add another heading like "About Access Healthcare". However the examples are just examples; they didn't say you cannot use other headings. But they said "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". This implies those are the expected headings. Safer to stick to those. We could incorporate the About Access Healthcare paragraph into About the role as a second paragraph. That would be okay: it's still about the role (the role at Access Healthcare). So we can add that paragraph after the first. Thus About the role will have two paragraphs: first about job details, second about the agency. Let's craft:

          About the role

          Access Healthcare is seeking a travel nurse RN Wound Care for a travel nursing job in Boston, Massachusetts. Specialty: Wound Care; Discipline: RN; Duration: 13 weeks; 40 hours per week; Shift: 10 hours, days; Employment Type: