Travel Emergency Room RN - $2,382 per week

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also do not repeat job title as heading. Do not put Job ID as heading; fold minor metadata into short

or drop it. We need to parse the posting: Host Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Mayville, North Dakota. Job Description & Requirements Specialty: ED - Emergency Department Discipline: RN Start Date: 10/12/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours, days, nights Employment Type: Travel Host Healthcare Job ID #a1fVX000004742zYAA. Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: RN - Emergency Room About Host Healthcare [paragraphs describing company] Benefits [list of benefits] We need sections: About the role (maybe description of role), Responsibilities (maybe not present), Requirements (maybe not present), Qualifications (maybe not present), Skills (maybe not present), Benefits (present), Pay (present? we have Pay package info), Schedule (present? we have shift and hours). We must only include sections if posting has real specific content. Let's see content: - About the role: The posting includes "Host Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Mayville, North Dakota." plus Job Description & Requirements block with Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift, Employment Type. That could be considered About the role. Could also be considered Responsibilities? Not explicit responsibilities listed. So we can put About the role section with that info. - Responsibilities: Not provided. So skip. - Requirements: Not provided (no list of required certifications, experience). So skip. - Qualifications: Not provided. Skip. - Skills: Not provided. Skip. - Benefits: Provided list. So include Benefits section with

• items. - Pay: Provided: "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's specific enough? It mentions basis but not actual numbers. It says tax-free stipend amount to be determined. It's somewhat vague but it's still content about pay. According to rules: 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". Might be considered placeholder. The instruction: never emit a heading followed by filler/placeholder text. If the content is mostly placeholder, we should not include Pay section. However we also have "Pay package is based on 12 hour shifts and 36.0 hours per week". That's some detail. But the actual amount is not given. The rule 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. It says "unless the posting actually states them." Does stating that pay package is based on 12 hour shifts and 36 hours per week count as stating pay? It states the basis but not the amount. Might be considered stating pay structure. However the rule about filler/placeholder text: "tax-free stipend amount to be determined" is placeholder. The whole sentence includes both basis and TBD stipend. Might be considered partially filler. Safer to omit Pay section because we don't have concrete pay amount or range. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay package is based on... So maybe we should include Pay section with that sentence. But we must avoid filler/placeholder text. The sentence includes "tax-free stipend amount to be determined" which is TBD. That's placeholder. Could we rephrase? We cannot invent or summarize away detail. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we must include that exact sentence? We could include it as is. It contains placeholder but it's the actual text from posting. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The example includes TBD. Our sentence includes "tax-free stipend amount to be determined" which is similar to TBD. So that would be considered filler/placeholder text. Therefore we should not create a Pay section because it would be heading followed by filler/placeholder text. However we could possibly include the part about basis and drop the TBD part? That would be summarizing away detail (removing the TBD stipend). That's not allowed because we must preserve ALL substantive information. The TBD stipend is substantive? It's stating that amount to be determined, which is info. So we must keep it. So including it would violate the rule about filler/placeholder text. So we should omit Pay section. - Schedule: Provided: "36 hours per week", "Shift: 12 hours, days, nights". That's specific. Not placeholder. So we can include Schedule section. Thus sections: About the role, Benefits, Schedule. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We must not include job title heading. Not include Job ID as heading; we can fold minor metadata into a short

    or drop it. The Job ID appears in the sentence: "Host Healthcare Job ID #a1fVX000004742zYAA. Pay package is based..." We decided to omit Pay section, but we still have that sentence includes Job ID and Pay info. Since we are not making a Pay section, we need to decide where to put that info. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can include a short

    containing the Job ID and maybe the pay basis? But we decided to omit Pay section due to placeholder. However we could still include the Job ID in a short

    maybe under About the role? Or as a separate

    before sections. The instruction says fold minor metadata into a short

    or drop it. So we can include a

    with the Job ID and maybe the pay basis? But pay basis is part of Pay section; if we omit Pay, we might still include the pay basis as part of About the role? That would be mixing. Better to just drop the Job ID and the pay sentence entirely? But we must preserve ALL substantive information. The Job ID is minor metadata; we can drop it. The pay sentence includes substantive info about pay basis and TBD stipend. If we drop it, we lose that info. But we already decided to omit Pay section due to placeholder; but we still need to preserve substantive info. The rule says never emit a heading followed by filler/placeholder text. It does not forbid including that info in a

    without a heading. So we could include a

    that contains the pay sentence (including Job ID) as a short paragraph, not under a heading. That would preserve the info without creating a Pay heading. That seems acceptable. Thus we will have:

    Host Healthcare Job ID #a1fVX000004742zYAA. Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

    Then sections:

    About the role

    Host Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Mayville, North Dakota. Specialty: ED - Emergency Department. Discipline: RN. Start Date: 10/12/2026. Duration: 13 weeks. 36 hours per week. Shift: 12 hours, days, nights. Employment Type: Travel.

    But note we already used 36 hours per week and shift info also in Schedule section. To avoid duplication, we should not repeat same info in multiple places. The instruction: Remove duplicated lines. So we should not duplicate the shift/hours info in both About the role and Schedule. We need to decide where to place them. The About the role could contain the generic description: seeking travel nurse RN ED - Emergency Department in Mayville, North Dakota. Specialty, Discipline, Start Date, Duration, Employment Type. The schedule specifics (hours per week, shift) could go under Schedule section. That avoids duplication. Thus About the role paragraph: "Host Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Mayville, North Dakota. Specialty: ED - Emergency Department. Discipline: RN. Start Date: 10/12/2026. Duration: 13 weeks. Employment Type: Travel." Schedule section:

    Schedule

    with

    36 hours per week. Shift: 12 hours, days, nights.

    Or we could use
    • but it's not a list; it's prose. Use

      . Benefits section:

      Benefits

      with
      • items from list. List of benefits: Referral bonus, School loan reimbursement, Vision benefits, Wellness and fitness programs, Company provided housing options, License and certification reimbursement, Life insurance, Medical benefits, Mileage reimbursement, Pet insurance, Discount program, Employee assistance programs, Guaranteed Hours, Health savings account, Holiday Pay, 401k retirement plan, Continuing Education, Dental benefits. We need to preserve all. Use
        • for each. We must not include any boilerplate like EEO etc. Not present. Now ensure we don't create empty sections. Now output only HTML fragment. Let's craft:

          Host Healthcare Job ID #a1fVX000004742zYAA. Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

          About the role

          Host Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Mayville, North Dakota. Specialty: ED - Emergency Department. Discipline: RN. Start Date: 10/12/2026. Duration: 13 weeks. Employment Type: Travel.

          Schedule

          36 hours per week. Shift: 12 hours, days, nights.

          Benefits

          • Referral bonus
          • School loan reimbursement
          • Vision benefits
          • Wellness and fitness programs
          • Company provided housing options
          • License and certification reimbursement
          • Life insurance
          • Medical benefits
          • Mileage reimbursement
          • Pet insurance
          • Discount program
          • Employee assistance programs
          • Guaranteed Hours
          • Health savings account
          • Holiday Pay
          • 401k retirement plan