Travel Nurse RN - PCU - Progressive Care Unit - $1,979 per week
On-siteInternship
We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes description, responsibilities, requirements, benefits, pay, schedule? Let's parse.
We have:
- Job description includes responsibilities: tasks list.
- Requirements: ACLS, BLS, 2 Years (maybe 2 years recent acute care experience). Also mention "Additional certifications may be required before beginning an assignment."
- Benefits: list of benefits.
- Pay: "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 vague; we should not create Pay section if it's not specific (no actual numbers). The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. For Pay, they state "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 not a specific amount; it's vague. Should we include? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package, but it's not a concrete figure. However it's still stating pay package basis. Might be considered stating pay, but it's not a specific amount. The rule also says: 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." That's placeholder. So we should not create a Pay section because it would be filler. Similarly Schedule: they mention shift: 12 hours, nights; duration: 13 weeks; 36 hours per week. That's specific schedule info. So we can include a Schedule section with those details.
Benefits: they list specific benefits, so include Benefits section.
About the role: we could have a section "About the role" with prose summarizing role? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real, specific content. We have responsibilities (list of tasks). We have requirements (certifications, experience). We have benefits. We have schedule. We could also have "About the role" maybe a brief description paragraph before responsibilities. The posting includes a paragraph describing what PCU RN does. That could go under About the role or Responsibilities. But we already have Responsibilities as a list of tasks. The paragraph before the list is more description of role. Could be placed under About the role. However we must not repeat job title as heading. So we can have:
About the role
... description ...
Responsibilities
Requirements
- ... ACLS, BLS, 2 years recent acute care experience ...
- Additional certifications may be required before beginning an assignment.
Benefits
Schedule
Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights.
We must not include Pay section. Also we should not include Job ID etc. Remove boilerplate.
Check for any duplicated lines: The benefits list appears twice? In the posting, benefits list appears once after "Benefits". It's a list. We'll output each benefit as
.
Now ensure we preserve all substantive information: The description about PCU RN tasks, the requirement of 1-2 years recent acute care experience (the text says "The right RN should have 1-2 years recent acute care experience.") Also "Requirements*: ACLS, BLS, 2 Years". So we need to capture both: 1-2 years recent acute care experience, plus ACLS, BLS. Also mention "Additional certifications may be required before beginning an assignment."
We should include that in Requirements list.
Now about the role paragraph: The posting includes: "We're looking for Progressive Care Unit RNs for an immediate travel nurse opening in Helena, MT. The right RN should have 1-2 years recent acute care experience. Read below for more requirements. As a PCU Travel Nurse, you will care for patients who require close monitoring and frequent assessment, but aren't unstable enough to need ICU care. Progressive Care Unit RNs will utilize computer equipment to monitor cardiac and other vital information, detecting any changes and thereby enabling intervention of life-threatening or emergency situations. Close observation is necessary as many PCU patients receive a significant amount of complex medications, sometimes through an intravenous line that may need to be adjusted or titrated. The PCU RN is sometimes also called a step-down nurse, and the PCU is also known as cardiac stepdown, medical stepdown, neuro stepdown, surgical stepdown and ER holding. As a PCU Travel Nurse, you should be prepared to perform the following tasks:" Then list tasks.
We can combine the introductory sentences into About the role paragraph, maybe up to before "As a PCU Travel Nurse, you should be prepared to perform the following tasks:" That paragraph includes the description of role and the 1-2 years experience. But we already have experience in Requirements; we could keep it in About the role as well but not duplicate? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. If we put it in About the role, we still need to keep experience info somewhere else? It's okay to have it in both places? Might be duplication but not invented. However we should avoid unnecessary duplication? The instruction didn't forbid duplication, but we should preserve all info; duplication is okay as long as we don't lose info. However better to keep experience in Requirements only, and About the role can focus on role description without repeating experience. But we must preserve the experience info; if we omit it from About the role but keep it in Requirements, it's still preserved. So fine.
Thus About the role paragraph: "We're looking for Progressive Care Unit RNs for an immediate travel nurse opening in Helena, MT. As a PCU Travel Nurse, you will care for patients who require close monitoring and frequent assessment, but aren't unstable enough to need ICU care. Progressive Care Unit RNs will utilize computer equipment to monitor cardiac and other vital information, detecting any changes and thereby enabling intervention of life-threatening or emergency situations. Close observation is necessary as many PCU patients receive a significant amount of complex medications, sometimes through an intravenous line that may need to be adjusted or titrated. The PCU RN is sometimes also called a step-down nurse, and the PCU is also known as cardiac stepdown, medical stepdown, neuro stepdown, surgical stepdown and ER holding."
That captures the role description.
Now Responsibilities list: The tasks after "As a PCU Travel Nurse, you should be prepared to perform the following tasks:" Provide list:
- Provide basic bedside care; stabilize critical cardiac patients.
- Change dressings, insert catheters and start IVs.
- Prepare, administer and record prescribed medication, reporting any adverse reactions to treatment.
- Monitor and adjust specialized equipment used on patients, and interpret and record electronic displays.
- Initiate corrective action whenever information from monitoring equipment shows adverse symptomatology.
- PCU 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, Progressive Care Unit RNs must possess good skills for coping with stress and be able to relate to people of all ages and backgrounds.
We need to split into items. Some sentences contain multiple tasks separated by semicolons; we could keep as one each bullet. That's fine.
Now Requirements list:
- ACLS
- BLS
- 1-2 years recent acute care experience (or 2 Years? We'll include both: 1-2 years recent acute care experience)
- Additional certifications may be required before beginning an assignment.
We could combine as separate .
Now Benefits list: The posting lists:
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 output each as . Note "Benefits start day 1" is a benefit statement; include as .
Now Schedule section: Provide details:
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, nights
We can put in a or
. The instruction: Use - for any list of duties/requirements/benefits, and
for prose. Schedule is not a list but could be prose. We'll use
with the details.
Now ensure we don't include any boilerplate like "TotalMed RN Job ID #1502005." Remove.
Also remove "Posted job title: Progressive Care Unit - PCU RN - Travel Nurse". Remove.
Also remove "About TotalMed RN" section? That's boilerplate about the agency; it's not part of the job posting specifics; it's organization description. According to rule: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TotalMed RN" is not exactly boilerplate but it's about the agency; might be considered not substantive to the job? The instruction says preserve ALL substantive information; does that include agency description? It's not about the job itself; but it's still part of the posting. However typical job postings include company overview; but the instruction didn't explicitly say to remove company description. It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About TotalMed RN" is not those; it's more like company description. I'd keep it? But we have limited sections; we could include an "About the company" section? Not in the allowed headings list; but we could use
About TotalMed RN
if we want. However the allowed headings list includes only those examples; but we could still use other headings? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. However they say "include a section ONLY when the posting has real, specific content for it". The company description is specific content. So we could include a section like "About TotalMed RN". However the heading examples didn't include that; but it's not prohibited. Safer to include it as a section maybe "About TotalMed RN". However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical sections; but we can still use other headings if needed. I'd include a section "About TotalMed RN" with the paragraph describing the agency.
But we must ensure we don't create filler. The paragraph is substantive.
Thus final HTML:
About the role
...
Responsibilities
- Provide basic bedside care; stabilize critical cardiac patients.
- Change dressings, insert catheters and start IVs.
- Prepare, administer and record prescribed medication, reporting any adverse reactions to treatment.
- Monitor and adjust specialized equipment used