Travel Registered Respiratory Therapist - $1,779 per week
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, parse the input:
Job posting:
- Title: "Slate Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Ogden, Utah." (but we don't repeat title)
- Job Description & Requirements
- Specialty: Registered Respiratory Therapist
- Discipline: Allied Health Professional
- Start Date: 11/02/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, days
- Employment Type: Travel
- Description: "As a Travel Respiratory Therapist, you will provide critical respiratory care to patients in a fast-paced hospital setting. Your day will include administering therapies, monitoring patient progress, and collaborating with healthcare teams to ensure optimal patient outcomes. This role offers a unique opportunity to gain diverse experience and make a meaningful impact in patient care during your assignment."
- Highlights:
- Competitive pay with guaranteed hours
- Opportunity to work in a diverse healthcare environment
- 3x12 day shifts for optimal work-life balance
- Requirements:
- EMR System experience
- Current Respiratory Therapist license
- 2 years of experience required
- BLS certification
- Slate Healthcare Job ID #c733217a-b31a-41df-8390-543e1734ba10. (metadata, fold into short p or drop)
- 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. (Pay info, but vague: "tax-free stipend amount to be determined" — not specific, so maybe not create Pay section? The rule says never create Pay section unless posting actually states them. It states pay package based on shifts and hours, but stipend TBD. Could include as a short p in a Schedule or Details section? But we have Schedule info: shift, hours per week, duration. Could create a Schedule section with those details. Pay is mentioned but not concrete. Might include in a "Details" or "Assignment Details" section. However, the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Requirements, we have Description (About the role), we have Highlights (could be Benefits), we have Schedule details (shift, hours, duration). Pay is mentioned but not concrete. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule: 36 hours per week, Shift: 12 hours, days, Duration: 13 weeks. So Schedule section is appropriate. Pay: "Competitive pay with guaranteed hours" and "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 some pay info, but not specific numbers. Could include in a Pay section? The rule says never create Pay section unless posting actually states them. It does state pay package details, albeit with TBD stipend. Might be okay to include a Pay section with that info. But the rule also says never emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Here stipend amount is "to be determined". That's placeholder. So maybe avoid Pay section. Instead, fold pay mention into Schedule or a general Details section? But we must use only allowed headings. Could create a "Schedule" section with shift, hours, duration, and maybe pay details as part of it? But Pay is separate heading. I think we should not create Pay section because the stipend is TBD. The "Competitive pay with guaranteed hours" is a highlight, could be under Benefits. Highlights could be Benefits. Let's see.
Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have:
- Description: "As a Travel Respiratory Therapist..." -> About the role
- Highlights: three bullet points -> could be Benefits
- Requirements: four bullet points -> Requirements
- Schedule details: Start Date, Duration, hours per week, Shift, Employment Type -> Schedule
- Pay details: mentioned but vague -> maybe not create Pay section
- About Slate Healthcare: company description -> could be About the role? Or separate? Not in allowed headings. Could fold into a short p at end or omit? The rule says preserve ALL substantive information. Company info is substantive. But not in allowed headings. Could create a section "About the Company" but not allowed. The allowed headings are fixed. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so maybe we can use other headings? But it says "use for section headings (e.g. ...)" implying those are the typical ones, but not exclusive? However, the rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the example list is given. I think we should stick to those headings. The company description could be part of "About the role" or a separate "About the Company" but not in list. Might be better to include as a short paragraph at the end without heading? But the rule says use for section headings. Could we use About Slate Healthcare
? It's not in the example list, but it's a section heading. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. However, the rule "Prefer a few substantive sections over many thin ones." So we can include a section for company info if it's substantive. But the user might expect only those headings. I'll include it as a section "About the Company" or "About Slate Healthcare". But to be safe, I'll include it as a section with h3.
But the instruction: "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 Job ID should be folded into a short p or dropped. I'll drop it or include in a metadata paragraph.
Now, structure:
1. About the role: description paragraph.
2. Benefits: highlights list.
3. Requirements: requirements list.
4. Schedule: details (start date, duration, hours per week, shift, employment type). Could be a list or paragraphs.
5. Pay: maybe not, because stipend TBD. But "Competitive pay with guaranteed hours" is in highlights. Could include pay info in Benefits? Or create Pay section with the pay package description. The pay package description: "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 about basis but not amount. Could include as a Pay section with that sentence. But the rule says never create Pay section unless posting actually states them. It does state pay package details. However, the stipend is TBD, which is placeholder. The rule says never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here "tax-free stipend amount to be determined" is essentially TBD. So maybe avoid Pay section. I'll omit Pay section.
6. About Slate Healthcare: company description.
Also, there is "Specialty", "Discipline" - these are metadata. Could fold into a short paragraph in About the role or Schedule.
Let's create sections:
- About the role: includes description, maybe specialty, discipline.
- Benefits: highlights list.
- Requirements: requirements list.
- Schedule: start date, duration, hours per week, shift, employment type.
- About Slate Healthcare: company description.
Now, write HTML.
Use
for each section heading.
Use
for prose,
- for lists.
For Schedule, could use a list or paragraphs. Since it's multiple details, a list might be good.
For About the role, the description is prose. Also include specialty and discipline as part of prose or list? Could be a list: Specialty: Registered Respiratory Therapist, Discipline: Allied Health Professional. But they are not duties. Could be a short paragraph.
I'll do:
About the role
As a Travel Respiratory Therapist, you will provide critical respiratory care to patients in a fast-paced hospital setting. Your day will include administering therapies, monitoring patient progress, and collaborating with healthcare teams to ensure optimal patient outcomes. This role offers a unique opportunity to gain diverse experience and make a meaningful impact in patient care during your assignment.
Specialty: Registered Respiratory Therapist; Discipline: Allied Health Professional.
Benefits
- Competitive pay with guaranteed hours
- Opportunity to work in a diverse healthcare environment
- 3x12 day shifts for optimal work-life balance
Requirements
- EMR System experience
- Current Respiratory Therapist license
- 2 years of experience required
- BLS certification
Schedule
- Start date: 11/02/2026
- Duration: 13 weeks
- Hours per week: 36
- Shift: 12 hours, days
- Employment type: Travel
About Slate Healthcare
Slate Healthcare is a premier travel healthcare staffing agency, connecting healthcare professionals with thousands of opportunities at top-tier hospitals and facilities across the country. We’re committed to supporting nurses and allied health professionals in building stable, fulfilling careers—while embracing the freedom and excitement that comes with travel. Our goal is simple: to offer flexibility, competitive pay, and personalized placements that align with each clinician’s lifestyle and career goals. At Slate, we empower our professionals to choose when and where
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, parse the input: Job posting: - Title: "Slate Healthcare is seeking a travel Registered Respiratory Therapist for a travel job in Ogden, Utah." (but we don't repeat title) - Job Description & Requirements - Specialty: Registered Respiratory Therapist - Discipline: Allied Health Professional - Start Date: 11/02/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Description: "As a Travel Respiratory Therapist, you will provide critical respiratory care to patients in a fast-paced hospital setting. Your day will include administering therapies, monitoring patient progress, and collaborating with healthcare teams to ensure optimal patient outcomes. This role offers a unique opportunity to gain diverse experience and make a meaningful impact in patient care during your assignment." - Highlights: - Competitive pay with guaranteed hours - Opportunity to work in a diverse healthcare environment - 3x12 day shifts for optimal work-life balance - Requirements: - EMR System experience - Current Respiratory Therapist license - 2 years of experience required - BLS certification - Slate Healthcare Job ID #c733217a-b31a-41df-8390-543e1734ba10. (metadata, fold into short p or drop) - 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. (Pay info, but vague: "tax-free stipend amount to be determined" — not specific, so maybe not create Pay section? The rule says never create Pay section unless posting actually states them. It states pay package based on shifts and hours, but stipend TBD. Could include as a short p in a Schedule or Details section? But we have Schedule info: shift, hours per week, duration. Could create a Schedule section with those details. Pay is mentioned but not concrete. Might include in a "Details" or "Assignment Details" section. However, the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Requirements, we have Description (About the role), we have Highlights (could be Benefits), we have Schedule details (shift, hours, duration). Pay is mentioned but not concrete. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule: 36 hours per week, Shift: 12 hours, days, Duration: 13 weeks. So Schedule section is appropriate. Pay: "Competitive pay with guaranteed hours" and "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 some pay info, but not specific numbers. Could include in a Pay section? The rule says never create Pay section unless posting actually states them. It does state pay package details, albeit with TBD stipend. Might be okay to include a Pay section with that info. But the rule also says never emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Here stipend amount is "to be determined". That's placeholder. So maybe avoid Pay section. Instead, fold pay mention into Schedule or a general Details section? But we must use only allowed headings. Could create a "Schedule" section with shift, hours, duration, and maybe pay details as part of it? But Pay is separate heading. I think we should not create Pay section because the stipend is TBD. The "Competitive pay with guaranteed hours" is a highlight, could be under Benefits. Highlights could be Benefits. Let's see. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - Description: "As a Travel Respiratory Therapist..." -> About the role - Highlights: three bullet points -> could be Benefits - Requirements: four bullet points -> Requirements - Schedule details: Start Date, Duration, hours per week, Shift, Employment Type -> Schedule - Pay details: mentioned but vague -> maybe not create Pay section - About Slate Healthcare: company description -> could be About the role? Or separate? Not in allowed headings. Could fold into a short p at end or omit? The rule says preserve ALL substantive information. Company info is substantive. But not in allowed headings. Could create a section "About the Company" but not allowed. The allowed headings are fixed. The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so maybe we can use other headings? But it says "use for section headings (e.g. ...)" implying those are the typical ones, but not exclusive? However, the rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the example list is given. I think we should stick to those headings. The company description could be part of "About the role" or a separate "About the Company" but not in list. Might be better to include as a short paragraph at the end without heading? But the rule says use for section headings. Could we use About Slate Healthcare
? It's not in the example list, but it's a section heading. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. However, the rule "Prefer a few substantive sections over many thin ones." So we can include a section for company info if it's substantive. But the user might expect only those headings. I'll include it as a section "About the Company" or "About Slate Healthcare". But to be safe, I'll include it as a section with h3.
But the instruction: "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
for section headings. Could we use About Slate Healthcare
? It's not in the example list, but it's a section heading. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. However, the rule "Prefer a few substantive sections over many thin ones." So we can include a section for company info if it's substantive. But the user might expect only those headings. I'll include it as a section "About the Company" or "About Slate Healthcare". But to be safe, I'll include it as a section with h3.
But the instruction: "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 Job ID should be folded into a short p or dropped. I'll drop it or include in a metadata paragraph. Now, structure: 1. About the role: description paragraph. 2. Benefits: highlights list. 3. Requirements: requirements list. 4. Schedule: details (start date, duration, hours per week, shift, employment type). Could be a list or paragraphs. 5. Pay: maybe not, because stipend TBD. But "Competitive pay with guaranteed hours" is in highlights. Could include pay info in Benefits? Or create Pay section with the pay package description. The pay package description: "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 about basis but not amount. Could include as a Pay section with that sentence. But the rule says never create Pay section unless posting actually states them. It does state pay package details. However, the stipend is TBD, which is placeholder. The rule says never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here "tax-free stipend amount to be determined" is essentially TBD. So maybe avoid Pay section. I'll omit Pay section. 6. About Slate Healthcare: company description. Also, there is "Specialty", "Discipline" - these are metadata. Could fold into a short paragraph in About the role or Schedule. Let's create sections: - About the role: includes description, maybe specialty, discipline. - Benefits: highlights list. - Requirements: requirements list. - Schedule: start date, duration, hours per week, shift, employment type. - About Slate Healthcare: company description. Now, write HTML. Use
for each section heading. Use
for prose,
- for lists.
For Schedule, could use a list or paragraphs. Since it's multiple details, a list might be good.
For About the role, the description is prose. Also include specialty and discipline as part of prose or list? Could be a list: Specialty: Registered Respiratory Therapist, Discipline: Allied Health Professional. But they are not duties. Could be a short paragraph.
I'll do:
About the role
As a Travel Respiratory Therapist, you will provide critical respiratory care to patients in a fast-paced hospital setting. Your day will include administering therapies, monitoring patient progress, and collaborating with healthcare teams to ensure optimal patient outcomes. This role offers a unique opportunity to gain diverse experience and make a meaningful impact in patient care during your assignment.
Specialty: Registered Respiratory Therapist; Discipline: Allied Health Professional.
Benefits
- Competitive pay with guaranteed hours
- Opportunity to work in a diverse healthcare environment
- 3x12 day shifts for optimal work-life balance
Requirements
- EMR System experience
- Current Respiratory Therapist license
- 2 years of experience required
- BLS certification
Schedule
- Start date: 11/02/2026
- Duration: 13 weeks
- Hours per week: 36
- Shift: 12 hours, days
- Employment type: Travel
About Slate Healthcare
Slate Healthcare is a premier travel healthcare staffing agency, connecting healthcare professionals with thousands of opportunities at top-tier hospitals and facilities across the country. We’re committed to supporting nurses and allied health professionals in building stable, fulfilling careers—while embracing the freedom and excitement that comes with travel. Our goal is simple: to offer flexibility, competitive pay, and personalized placements that align with each clinician’s lifestyle and career goals. At Slate, we empower our professionals to choose when and where