Jobs · Rhode Island

Travel Nurse RN - PACU - Post Anesthesia Care - $2,558 per week

TotalMed · Warwick, RI · 1 mo ago
On-siteInternship
We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We need to parse the posting. Job description includes: Specialty: PACU - Post Anesthesia Care, Discipline: RN, Duration: 13 weeks, 40 hours per week, Shift: 8 hours, rotating, Employment Type: Travel. Then description: "We're looking for Post Anesthesia Care Unit RNs for an immediate travel nurse opening in [citSt]. The right RN should have 1-2 years recent acute care experience. Read below for more requirements. As a PACU RN, you'll provide observation and care for post-op patients as they recover from surgical anesthesia. PACU Travel Nurses offer a crucial care step between surgery and recovery, and ensure that patients are monitored for any adverse reactions. As a PACU Travel Nurse, you should be prepared to perform the following tasks: Handle a broad range of patients from pediatrics to adults. Develop individualized care plans based on each patient's condition. Monitor critical patients for condition changes and report to the physician. Be responsible for determining when patients are recovered and ready to move to a room. PACU Travel Nurses should be able to stand and walk for long periods of time, as well as bend, lean and stoop without difficulty. RNs should be able to easily lift 20 pounds. Moving or lifting of patients may require lifting of up to 50 pounds at times. Because of the fast-paced environment, Post Anesthesia Care Unit RNs must possess good skills for coping with stress and be able to relate to people of all ages and backgrounds." Then "Requirements*: ACLS, BLS, 2 Years * Additional certifications may be required before beginning an assignment." Then "TotalMed RN Job ID #1506483. Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." Then "Posted job title: Post-Anesthesia Care Unit - PACU RN - Travel Nurse" Then "About TotalMed RN" description. Then "Benefits" list: 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. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. So no heading for job title. We need to not put Job ID as heading; fold minor metadata into short p or drop it. So we can include Job ID in a p maybe. We need to include sections only when posting has real specific content. We have content for: - About the role: maybe the description paragraph about role. Could be "About the role" heading. - Responsibilities: list of tasks (Handle a broad range..., Develop..., Monitor..., Be responsible..., etc). That's responsibilities. - Requirements: ACLS, BLS, 2 Years (maybe also 1-2 years recent acute care experience). Also maybe "Additional certifications may be required". So we can list. - Qualifications: maybe not separate; but we could combine with Requirements. But we can have Requirements heading. - Skills: maybe not explicit; but we could infer skills like coping with stress, relating to people, etc. Might be considered skills. However we need real specific content; we have "good skills for coping with stress and be able to relate to people of all ages and backgrounds." That's a skill. Also "stand and walk for long periods, bend, lean, stoop, lift 20 lbs, up to 50 lbs." Those are physical requirements, could be under Requirements or Skills. We'll decide. - Benefits: list given. - Pay: mention "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's somewhat vague but it's specific about basis. It says tax-free stipend amount to be determined (not specific). The rule: do NOT include Pay section unless posting actually states them. It does state pay package based on 8 hour shifts and 40 hours per week, but stipend amount TBD. Is that enough? It says "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's somewhat vague but still mentions pay structure. I'd include Pay section with that sentence. - Schedule: we have Shift: 8 hours, rotating; Duration: 13 weeks; 40 hours per week. That's schedule info. So we can include Schedule section. We need to avoid filler like "commensurate with experience", "not specified", etc. Pay section includes "tax-free stipend amount to be determined" which is TBD; that might be considered filler. The rule: 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. The phrase "tax-free stipend amount to be determined" is TBD. That's placeholder. So maybe we should not include Pay section because it includes TBD. However we could still include Pay section if we only include the concrete part: "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation)". That's still somewhat vague but not TBD. The stipend amount TBD is extra. We could omit that part? But we must preserve ALL substantive information; we cannot invent or summarize away detail. We can include the sentence as is, but it contains TBD. The rule says never emit a heading followed by filler/placeholder text. If the section contains placeholder text, is that disallowed? It says "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That suggests if the section's content is just filler, don't create it. But if the section includes some real info plus placeholder, maybe still okay? Safer to avoid Pay section if it includes TBD. However we could rephrase to exclude the TBD part? But we must preserve ALL substantive information; we cannot remove the stipend amount to be determined because it's part of the posting. However we could include it as a note within the section; still includes TBD. The rule might be interpreted as: don't create a section if the only content is placeholder. If there is real info, it's okay to have placeholder as part of it. I'd include Pay section with the full sentence. Schedule: we have concrete: 13 weeks duration, 40 hours per week, shift 8 hours rotating. That's substantive. Benefits: list is concrete. Now structure:

About the role

... (the descriptive paragraph about role)

Responsibilities

  • Handle a broad range of patients from pediatrics to adults.
  • Develop individualized care plans based on each patient's condition.
  • Monitor critical patients for condition changes and report to the physician.
  • Be responsible for determining when patients are recovered and ready to move to a room.
  • PACU Travel Nurses should be able to stand and walk for long periods of time, as well as bend, lean and stoop without difficulty.
  • RNs should be able to easily lift 20 pounds. Moving or lifting of patients may require lifting of up to 50 pounds at times.
  • Because of the fast-paced environment, Post Anesthesia Care Unit RNs must possess good skills for coping with stress and be able to relate to people of all ages and backgrounds.
But note some of those are also skills/requirements. Might duplicate. However we can keep them as responsibilities.

Requirements

  • ACLS certification
  • BLS certification
  • 2 years recent acute care experience (1-2 years)
  • Additional certifications may be required before beginning an assignment
We could also include "1-2 years recent acute care experience" as separate.

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

Pay

Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined.

Schedule

Duration: 13 weeks; 40 hours per week; Shift: 8 hours, rotating.

We also need to include maybe "About TotalMed RN" as a section? Could be "About the company" but not in list of allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings. The "About TotalMed RN" description is company info; maybe we can fold into About the role? But it's not about the role. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exhaustive? It says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely only those headings allowed. So we should not create a heading for About TotalMed RN. We could incorporate that info into a paragraph under About the role? But that would be mixing. Better to drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot drop the TotalMed description. But we cannot create a heading not in the list. However we could put it as a

without a heading? The instruction says use h3 for section headings (list). It doesn't forbid other headings, but says use h3 for section headings (e.g. ...). It might be okay to have other headings but they'd be non-standard. Safer to stick to allowed headings and place the TotalMed description under a generic heading like "About the role"? Not accurate. Perhaps we can treat "About TotalMed RN" as part of "About the role" but it's not about role. However we could add a

without a heading after the sections; that would preserve info. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose." It doesn't say we cannot have

    without heading. So we can add a

    for the TotalMed description after the sections, without a heading. That would preserve info. Similarly, we have the line "Posted job title: Post-Anesthesia Care Unit - PACU RN - Travel Nurse" which we should not repeat as heading; we can drop it as it's redundant with job title already shown. So we can drop. We also have "TotalMed RN Job ID #1506483." We can include that in a

Similar jobs