Travel Med/Surg Tele RN - $2,131 per week
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job posting.
Key info:
- Title: Telemetry - TELE RN - Travel Nurse (but we don't repeat as heading)
- Location: Mayfield Heights, Ohio
- Specialty: Med Surg / Telemetry
- Discipline: RN
- Duration: 13 weeks
- Hours: 36 hours per week
- Shift: 12 hours, nights
- Employment Type: Travel
- Immediate opening
- Required: 1-2 years recent acute care experience (they say 1-2 years, but later Requirements*: BLS, ACLS, 2 years). So requirement: BLS, ACLS, 2 years recent acute care experience.
- Additional certifications may be required before beginning an assignment.
- Job ID #1511888 (metadata, we can drop or put in short p)
- Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. So pay info: based on 12 hour shifts, 36 hrs/week, tax-free stipend TBD. This is somewhat vague; but we have some pay info: "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 not a specific number; it's "subject to confirmation" and stipend TBD. According to rules: do NOT create Pay section unless posting actually states them. It does state pay package based on shifts and hours, but amount TBD. Is that considered real specific content? It says "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 is somewhat vague but still mentions pay structure. However the rule: "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. Also "subject to confirmation". This might be considered placeholder. Safer to omit Pay section because no concrete amount. However we could include a short p with that info under maybe About the role? But they said we should not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated: list of benefits. So Benefits section is appropriate.
Schedule: they gave shift: 12 hours, nights; hours per week: 36 hours. That's schedule info. Should we create Schedule section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state shift and hours, so we can include Schedule section with that info. However we need to avoid filler like "varies". It's specific: 12 hour shifts, nights, 36 hours per week. So we can include Schedule.
Benefits: they list many benefits. So Benefits section.
About the role: we can include a short paragraph describing role: Telemetry RN duties.
Responsibilities: we have list of tasks: Provide basic bedside care; Monitor and adjust specialized equipment; Interpret and record electronic displays; Identify irregular telemetry readings and notify appropriate medical team members; Initiate corrective action whenever information from monitoring equipment shows adverse symptomatology; Stand and walk for long periods; bend, lean, stoop; lift 20 pounds; moving/lifting patients may require up to 50 pounds; vision abilities: close, distance, color, peripheral, depth perception, ability to adjust focus.
Requirements: BLS, ACLS, 2 years recent acute care experience. Additional certifications may be required.
Qualifications: maybe same as requirements? Could combine.
Skills: maybe not explicitly listed; we could infer from responsibilities but better not to invent. So we may omit Skills if no explicit list.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's none.
We need to output only HTML fragment, no /, no markdown.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections: About the role (description), Responsibilities, Requirements, Benefits, Schedule. Possibly also Qualifications? But we can merge Requirements and Qualifications if they are similar. The posting has "Requirements*: BLS, ACLS, 2 years * Additional certifications may be required before beginning an assignment." That's requirements. There's no separate qualifications list. So we can have Requirements section.
We might also include a short paragraph for metadata like Job ID, location, duration, etc. Could be placed in About the role or a separate "Details" but not a heading. Since we shouldn't create headings for minor metadata, we can put them in a
after the heading maybe.
Let's structure:
About the role
TotalMed RN is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Mayfield Heights, Ohio. The position is for 13 weeks, 36 hours per week, 12‑hour night shifts. Employment type is travel.
Responsibilities
- Provide basic bedside care.
- Monitor and adjust specialized equipment used on patients, and interpret and record electronic displays.
- Identify irregular telemetry readings and notify appropriate medical team members.
- Initiate corrective action whenever information from monitoring equipment shows adverse symptomatology.
- Stand and walk for long periods of time, as well as bend, lean and stoop without difficulty.
- Easily lift 20 pounds; moving or lifting patients may require lifting of up to 50 pounds at times.
- Possess specific vision abilities including close vision, distance vision, color vision, peripheral vision, depth perception and ability to adjust focus.
Requirements
- BLS certification.
- ACLS certification.
- Minimum 2 years’ recent acute care experience (1‑2 years’ recent acute care experience preferred).
- Additional certifications may be required before beginning an assignment.
Benefits
- Weekly pay
- Guaranteed Hours
- Continuing Education
- 401k retirement plan
- Sick pay
- Wellness and fitness programs
- Referral bonus
- Employee assistance programs
- Medical benefits
- Dental benefits
- Vision benefits
- Benefits start day 1
Schedule
12‑hour night shifts, 36 hours per week.
We need to ensure we didn't repeat job title as heading. We didn't.
We need to ensure we didn't include Pay section. We omitted.
Check for any duplicated lines: we didn't.
Check for any boilerplate: none.
Check for any placeholders: In Benefits we have "Weekly pay", "Guaranteed Hours", etc. Those are specific benefits listed. Good.
Check for any missing info: we didn't include the Job ID #1511888. Should we include it? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." So we can include it in a short p maybe under About the role or separate p without heading. Let's add a short p after About the role maybe: "
Job ID: #1511888.
" That's minor metadata.
Also we might include location, duration, etc already in About the role.
We need to preserve ALL substantive information. The Job ID is substantive? It's metadata but we can fold into short p. So include.
Also the posting mentions "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." We omitted Pay section because it's vague. But we might include that info in Schedule or About the role? The schedule already mentions 12 hour shifts, 36 hours per week. The pay package info is about pay, but we don't have specific amount. Since we cannot create Pay section due to placeholder, we could mention that pay details are to be confirmed in a short p under About the role or Schedule? But that would be adding info not originally in those sections; but it's still part of posting. However the rule 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." It doesn't forbid adding pay info in a p. However we must not create Pay section unless posting actually states them. It does state pay package based on shifts and hours with stipend TBD. That's still stating something about pay, albeit vague. But the rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we made a Pay heading, the content would be filler/placeholder. So we should not create Pay heading. But we could still include that sentence in a paragraph under About the role or Schedule as minor metadata? The sentence is about pay, not schedule. But we could incorporate it into About the role as a note: "Pay package is based on 12‑hour shifts and 36 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined." That is not a heading, just a p. That seems acceptable because we are not creating a Pay section. The rule only prohibits creating a Pay/Schedule/Benefits section unless posting actually states them. It doesn't prohibit mentioning pay info elsewhere. So we can add that as a p.
Similarly, we might add the shift info already in Schedule; we could also mention that it's nights.
Let's incorporate pay note in About the role.
Thus final HTML:
About the role
TotalMed RN is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Mayfield Heights, Ohio. The position is for 13 weeks, 36 hours per week, 12‑hour night shifts. Employment type is travel. Pay package is based on 12‑hour shifts and 36 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined. Job ID: #1511888.
Then Responsibilities, Requirements, Benefits, Schedule.
Check for any other info: "As a TELE Travel Nurse, you will provide care by connecting patients to machines that measure heart rate, blood pressure, breathing rate, as well as blood-oxygen levels and electrocardiogram information. These machines then send data to computer screens for RNs to monitor. Telemetry RNs read and interpret the data to better determine patient care." That's descriptive; we could incorporate into About the role as well. We missed that. Let's add that description.
Thus About the role p could be longer: include that description.
Let's craft:
TotalMed RN is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Mayfield Heights, Ohio. As
- for any list of duties/requirements/benefits. Use
for prose. We need to decide sections: About the role (description), Responsibilities, Requirements, Benefits, Schedule. Possibly also Qualifications? But we can merge Requirements and Qualifications if they are similar. The posting has "Requirements*: BLS, ACLS, 2 years * Additional certifications may be required before beginning an assignment." That's requirements. There's no separate qualifications list. So we can have Requirements section. We might also include a short paragraph for metadata like Job ID, location, duration, etc. Could be placed in About the role or a separate "Details" but not a heading. Since we shouldn't create headings for minor metadata, we can put them in a
after the heading maybe. Let's structure:
About the role
TotalMed RN is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Mayfield Heights, Ohio. The position is for 13 weeks, 36 hours per week, 12‑hour night shifts. Employment type is travel.
Responsibilities
- Provide basic bedside care.
- Monitor and adjust specialized equipment used on patients, and interpret and record electronic displays.
- Identify irregular telemetry readings and notify appropriate medical team members.
- Initiate corrective action whenever information from monitoring equipment shows adverse symptomatology.
- Stand and walk for long periods of time, as well as bend, lean and stoop without difficulty.
- Easily lift 20 pounds; moving or lifting patients may require lifting of up to 50 pounds at times.
- Possess specific vision abilities including close vision, distance vision, color vision, peripheral vision, depth perception and ability to adjust focus.
Requirements
- BLS certification.
- ACLS certification.
- Minimum 2 years’ recent acute care experience (1‑2 years’ recent acute care experience preferred).
- Additional certifications may be required before beginning an assignment.
Benefits
- Weekly pay
- Guaranteed Hours
- Continuing Education
- 401k retirement plan
- Sick pay
- Wellness and fitness programs
- Referral bonus
- Employee assistance programs
- Medical benefits
- Dental benefits
- Vision benefits
- Benefits start day 1
Schedule
12‑hour night shifts, 36 hours per week.
We need to ensure we didn't repeat job title as heading. We didn't. We need to ensure we didn't include Pay section. We omitted. Check for any duplicated lines: we didn't. Check for any boilerplate: none. Check for any placeholders: In Benefits we have "Weekly pay", "Guaranteed Hours", etc. Those are specific benefits listed. Good. Check for any missing info: we didn't include the Job ID #1511888. Should we include it? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So we can include it in a short p maybe under About the role or separate p without heading. Let's add a short p after About the role maybe: "
Job ID: #1511888.
" That's minor metadata. Also we might include location, duration, etc already in About the role. We need to preserve ALL substantive information. The Job ID is substantive? It's metadata but we can fold into short p. So include. Also the posting mentions "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." We omitted Pay section because it's vague. But we might include that info in Schedule or About the role? The schedule already mentions 12 hour shifts, 36 hours per week. The pay package info is about pay, but we don't have specific amount. Since we cannot create Pay section due to placeholder, we could mention that pay details are to be confirmed in a short p under About the role or Schedule? But that would be adding info not originally in those sections; but it's still part of posting. However the rule 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 shortor drop it." It doesn't forbid adding pay info in a p. However we must not create Pay section unless posting actually states them. It does state pay package based on shifts and hours with stipend TBD. That's still stating something about pay, albeit vague. But the rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we made a Pay heading, the content would be filler/placeholder. So we should not create Pay heading. But we could still include that sentence in a paragraph under About the role or Schedule as minor metadata? The sentence is about pay, not schedule. But we could incorporate it into About the role as a note: "Pay package is based on 12‑hour shifts and 36 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined." That is not a heading, just a p. That seems acceptable because we are not creating a Pay section. The rule only prohibits creating a Pay/Schedule/Benefits section unless posting actually states them. It doesn't prohibit mentioning pay info elsewhere. So we can add that as a p. Similarly, we might add the shift info already in Schedule; we could also mention that it's nights. Let's incorporate pay note in About the role. Thus final HTML:
About the role
TotalMed RN is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Mayfield Heights, Ohio. The position is for 13 weeks, 36 hours per week, 12‑hour night shifts. Employment type is travel. Pay package is based on 12‑hour shifts and 36 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined. Job ID: #1511888.
Then Responsibilities, Requirements, Benefits, Schedule. Check for any other info: "As a TELE Travel Nurse, you will provide care by connecting patients to machines that measure heart rate, blood pressure, breathing rate, as well as blood-oxygen levels and electrocardiogram information. These machines then send data to computer screens for RNs to monitor. Telemetry RNs read and interpret the data to better determine patient care." That's descriptive; we could incorporate into About the role as well. We missed that. Let's add that description. Thus About the role p could be longer: include that description. Let's craft:TotalMed RN is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Mayfield Heights, Ohio. As