Travel Registered Respiratory Therapist - $1,873 per week

We need to output HTML fragment with sections for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading; fold minor metadata into short

  or drop it. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Remove duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". So we need to extract substantive content. Let's parse the posting: Host Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Akron, Ohio. Job Description & Requirements Specialty: Registered Respiratory Therapist Discipline: Allied Health Professional Start Date: 10/11/2026 Duration: 5 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel Host Healthcare Job ID #a1fVX0000046C10YAE. 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: Respiratory Therapist About Host Healthcare [Paragraph about company] During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare. Benefits [list of benefits] We need to decide which sections to include. We have: - About the role: maybe we can include description of role: travel Registered Respiratory Therapist in Akron, Ohio; specialty, discipline, start date, duration, hours, shift, employment type. That's substantive. - Responsibilities: Not explicitly listed. The posting does not list duties/responsibilities. So we should not create a Responsibilities section. - Requirements: Not explicitly listed beyond specialty and discipline. Could treat "Registered Respiratory Therapist" as requirement. But we need to see if there is any specific requirement like license, certification etc. Not given. So maybe we skip Requirements or combine into About the role. - Qualifications: Not given. - Skills: Not given. - Benefits: Yes, there is a Benefits list. So we should include Benefits section with

  • list. - Pay: There's mention: "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 vague; it says tax-free stipend amount to be determined. This is not a specific pay figure. According to instruction: 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. So we should not create a Pay section because it's not specific. However we could include the info about pay package being based on 12 hour shifts and 36 hours per week, but that's still not a number. The instruction says avoid filler/placeholder text. So better to omit Pay section. - Schedule: We have shift: 12 hours, nights; 36 hours per week. That's specific schedule info. So we can create a Schedule section with details. - About Host Healthcare: That's about the company, not the role. Could be placed under a section like "About the Company" but not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create a section for About Host Healthcare unless we map it to About the role? The About the role heading is for role description. The company description could be considered part of About the role? Possibly we can include a brief paragraph about the employer under About the role? But 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? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should only use those headings. So we need to fit content into those sections. Thus we need to decide which sections have substantive content: - About the role: we can include description of the role: travel Registered Respiratory Therapist in Akron, Ohio; specialty, discipline, start date, duration, hours, shift, employment type. Also maybe mention job location. - Responsibilities: none. - Requirements: maybe we can include that candidate must be a Registered Respiratory Therapist (license). But that's basically same as specialty. Could be considered requirement. However we need to avoid filler. If we put a requirement list with just "Registered Respiratory Therapist license" maybe okay. But we need to see if there is any explicit requirement like "must have active RRT license". Not given. The posting only says Specialty: Registered Respiratory Therapist. That could be considered a requirement. But we need to decide if we want to create a Requirements section. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine About the role and Requirements into one? But we must follow headings. Could we put both under About the role? Probably yes. The About the role can include description and requirements. That would be substantive. - Qualifications: none. - Skills: none. - Benefits: we have list. - Pay: not specific, skip. - Schedule: we have shift and hours. Thus we will output sections: About the role, Benefits, Schedule. We need to use

    for each heading. Use

    • for any list of duties/requirements/benefits. For Benefits we have a list; we should output
      • items. For About the role we can use

        for prose. For Schedule we can use

        or maybe

        • if we list items. But schedule info is short; we can use

          . We must preserve all substantive information. Let's extract: About the role: - Host Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Akron, Ohio. - Specialty: Registered Respiratory Therapist - Discipline: Allied Health Professional - Start Date: 10/11/2026 - Duration: 5 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Posted job title: Respiratory Therapist (maybe not needed) - Job ID: a1fVX0000046C10YAE (maybe minor metadata, we can drop or put in short p). The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it. So we could include it in a short p within About the role or maybe drop it. Since it's minor, we could drop it. But we need to preserve ALL substantive information; is Job ID substantive? Probably not; it's metadata. So we can drop it. Also note: 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. This is pay info but not specific; we decided to skip Pay section. However we might still include that info in About the role or Schedule? It's about pay, but it's vague. The instruction says never emit a heading followed by filler/placeholder text. Including that sentence in a paragraph might be okay as it's not a heading. It's not filler? It says "tax-free stipend amount to be determined" which is TBD. That's placeholder. Should we include it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we drop that sentence, we are summarizing away detail (the mention of pay package). But it's not substantive because it's not specific. However it's still detail. The instruction says "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". It doesn't forbid including such text in a paragraph; it's about headings. So we could include that sentence in a paragraph under About the role or maybe under a separate Pay section? But we decided not to create Pay heading because it would be followed by filler text. So we can include the pay sentence in About the role paragraph as prose. That seems acceptable. Similarly, we have "Posted job title: Respiratory Therapist" which is basically same as role; we can include. Now Benefits list: The posting shows a list: 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 output each as

        • . Schedule: we have Shift: 12 hours, nights; 36 hours per week. Also maybe mention duration 5 weeks? That's more about assignment length; could be in About the role. But schedule section could include shift and weekly hours. We'll include both. Now we need to output HTML fragment only, no /, no markdown. Thus:

          About the role

          Host Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Akron, Ohio. Specialty: Registered Respiratory Therapist; Discipline: Allied Health Professional; Start Date: 10/11/2026; Duration: 5 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel. 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.

          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

          Schedule

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

          We might also include the duration 5 weeks in Schedule? But it's more about assignment length. Could be included in About the role already. Check for any duplicated lines: we have not included boilerplate like "During your assignment, get access to premium benefits..." That's actually part of benefits description; we already captured benefits list. The prose about premium benefits could be included in About the role or Benefits section as a paragraph before list. The instruction: Use

          for