RN- Med Surg Tele - 2 East (36/D/E)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job posting.
Content:
- Opening: "When you join the growing BILH team, you're not just taking a job, you’re making a difference in people’s lives. 36hpw; 7a-7:30p, every other weekend and holiday rotation"
That's schedule info: 36 hours per week; 7am-7:30pm, every other weekend and holiday rotation.
- "Job Description UNIT DESCRIPTION: 2 East is a 49bed general medical/surgical telemetry unit that provides care to adult and geriatric patients. The staff cares for patients with a wide variety of acute conditions and patients with multiple comorbidities."
That's about the unit/role.
- "Preference will be given, by seniority, to those qualified nurses who were serially displaced within the 18 months following his/her displacement according toMNAcontract section 9.4 (f)(1)." That's a preference note.
- Minimum Requirements list: Current Massachusetts RN License; Evidence of Continuing Education; Prior experience working as a RN required, Med Surg experience preferred; Current Telemetry experience or able to pass Telemetry Competency Exam within 90 days of beginning position; Current AHA BLS Certification; Utilizes appropriate time management skills; Communicates effectively.
- Recommended Requirements: Documented Professional Developmental activities; Knowledge of Critical Paths; Charge Nurse experience preferred; BSN Preferred; AHA ACLS Preferred.
- "As with all job assignments, staff may be floated to areas where they are needed"
- Application Instructions (to be removed)
- Pay Range $37.14 - $82.22
- This position is covered by a collective bargaining agreement... (pay details). We need to include Pay section if posting actually states them. Yes, pay range is given. So we can include Pay section with that info.
- Benefits: Not mentioned explicitly. There's mention of influenza vaccination requirement, but not benefits. No explicit benefits like health insurance, retirement, etc. So we should not create Benefits section unless posting actually states them. There's no explicit benefits. So skip Benefits.
- Schedule: we have schedule info: 36hpw; 7a-7:30p, every other weekend and holiday rotation. So we can include Schedule section.
- About the role: we have unit description and maybe overview. Could be About the role.
- Responsibilities: Not explicitly listed; maybe implied but not specific duties. The posting doesn't list responsibilities like "administer medications", etc. So we should not create Responsibilities unless there is specific content. There's no list of duties. So skip Responsibilities.
- Requirements: we have Minimum Requirements and Recommended Requirements. Could combine into Requirements section (maybe split into Minimum and Preferred). But we need to use - for any list of duties/requirements/benefits. So we can have a Requirements section with subheadings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings inside, but we should follow. We could have Requirements as Requirements
then maybe - for each item. Could separate Minimum and Preferred using or separate paragraphs? Probably just list all items.
- Qualifications: Could be similar to Requirements. But we should not duplicate. The instruction says prefer a few substantive sections over many thin ones. So we can combine Minimum and Preferred into Requirements. Qualifications maybe not needed.
- Skills: Could extract skills like time management, communication, etc. But those are already in Requirements. Could create Skills section for those soft skills. However we need to avoid thin sections. Might be better to include them in Requirements.
Thus sections: About the role (unit description), Requirements (minimum + recommended), Pay, Schedule.
Check if any other specific content: "Preference will be given, by seniority, to those qualified nurses who were serially displaced within the 18 months following his/her displacement according toMNAcontract section 9.4 (f)(1)." That's a preference note; could be included in Requirements or About the role? It's a hiring preference. Could be placed in Requirements as a note.
Also "As with all job assignments, staff may be floated to areas where they are needed" - could be a responsibility or note. Could be included in About the role or Requirements.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include that preference note and floating statement.
We need to avoid boilerplate: remove EEO, equal opportunity, scam warning, application instructions, navigation, cookie, legal. The posting includes "Equal Opportunity Employer/Veterans/Disabled" at end - remove.
Also "As a health care organization, we have a responsibility to do everything in our power to care for and protect our patients, our colleagues and our communities. Beth Israel Lahey Health requires that all staff be vaccinated against influenza (flu) as a condition of employment. More than 35,000 people working together. Nurses, doctors, technicians, therapists, researchers, teachers and more, making a difference in patients' lives. Your skill and compassion can make us even stronger." This is somewhat boilerplate but maybe considered organizational description. It's not a standard EEO but could be considered generic marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph is not exactly EEO but could be considered generic fluff. However it's substantive? It mentions influenza vaccination requirement - that is a specific requirement (must be vaccinated). That's a substantive requirement (condition of employment). So we should keep that as a requirement (maybe under Requirements). The rest about 35,000 people etc is fluff; could be considered boilerplate. But we need to preserve ALL substantive information; we can drop non-substantive fluff. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove generic marketing fluff, but we should keep substantive info. The influenza vaccination requirement is substantive; we can keep that. The rest about 35,000 people etc may be considered filler; but not explicitly listed as boilerplate to remove. Safer to keep it? Might be considered non-substantive but not prohibited. However we want to avoid filler/placeholder text. The instruction: "Prefer a few substantive sections over many thin ones." So we could include a short paragraph about the organization under About the role maybe. But we need to decide.
I think we can include a brief "About the organization" paragraph under About the role or as a separate section? But we only have headings list; we could add a paragraph under About the role after unit description.
Thus About the role: includes unit description and maybe the organization statement about making a difference, vaccination requirement, etc.
But we need to avoid duplication.
Let's extract substantive pieces:
- Intro: "When you join the growing BILH team, you're not just taking a job, you’re making a difference in people’s lives." That's motivational; could be part of About the role.
- Schedule: "36hpw; 7a-7:30p, every other weekend and holiday rotation"
- Unit Description: "2 East is a 49bed general medical/surgical telemetry unit that provides care to adult and geriatric patients. The staff cares for patients with a wide variety of acute conditions and patients with multiple comorbidities."
- Preference note: "Preference will be given, by seniority, to those qualified nurses who were serially displaced within the 18 months following his/her displacement according toMNAcontract section 9.4 (f)(1)."
- Minimum Requirements list (as above)
- Recommended Requirements list (as above)
- Floating statement: "As with all job assignments, staff may be floated to areas where they are needed"
- Pay range: "$37.14 - $82.22" plus description about collective bargaining agreement.
- Influenza vaccination requirement: "Beth Israel Lahey Health requires that all staff be vaccinated against influenza (flu) as a condition of employment."
- Organization size/mission: "More than 35,000 people working together. Nurses, doctors, technicians, therapists, researchers, teachers and more, making a difference in patients' lives. Your skill and compassion can make us even stronger." This is fluff but maybe okay.
We need to output HTML fragment only.
We'll create sections:
About the role
When you join the growing BILH team, you're not just taking a job, you’re making a difference in people’s lives. 2 East is a 49‑bed general medical/surgical telemetry unit that provides care to adult and geriatric patients. The staff cares for patients with a wide variety of acute conditions and patients with multiple comorbidities. As with all job assignments, staff may be floated to areas where they are needed. Beth Israel Lahey Health requires that all staff be vaccinated against influenza (flu) as a condition of employment. More than 35,000 people working together. Nurses, doctors, technicians, therapists, researchers, teachers and more, making a difference in patients' lives. Your skill and compassion can make us even stronger.
But note: we included schedule? Actually schedule is separate.
We also need to include the preference note somewhere. Could be in About the role or Requirements. It's a hiring preference; maybe put in Requirements as a note.
Better: Add a paragraph under About the role about preference? Might be okay.
But we need to keep all info. Let's place preference note in Requirements section as a note.
Now Requirements section:
Requirements
- Current Massachusetts RN License
- Evidence of Continuing Education
- Prior experience working as a RN required; Med Surg experience preferred
- Current Telemetry experience or able to pass Telemetry Competency Exam within 90 days of beginning position
- Current AHA BLS Certification
- Utilizes appropriate time management skills
- Communicates effectively
- Preference will be given, by seniority, to those qualified nurses who were serially displaced within the 18 months following his/her displacement according to MNA contract section 9.4 (f)(1)
- Documented Professional Developmental activities (recommended)
- Knowledge of Critical Paths (recommended)
- Charge Nurse experience preferred (recommended)
- BSN Preferred (recommended)
- AHA ACLS Preferred (recommended)
But we need to differentiate minimum vs recommended? Not required but could be okay.
We could add a note that recommended items are preferred but not required. But we must not invent. The posting says "Recommended Requirements". So we can label them as (Preferred) or (Recommended). We'll keep as is.
Now Pay section:
Pay
Pay Range $37.14 - $82.22. This position is covered by a collective bargaining agreement. The pay range listed for this position is the base hourly wage range the organization reasonably and in good faith expects to pay for this position at this time. The pay range for this position is established and governed by the terms of the applicable collective bargaining agreement. Employees hired into this position will receive compensation consistent with the terms of the applicable collective bargaining agreement.
Schedule section:
Schedule
36 hours per week; 7:00 a.m.‑7:30 p.m., every other weekend and holiday rotation.
We need to ensure we used correct formatting
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings inside, but we should follow. We could have Requirements as Requirements
then maybe - for each item. Could separate Minimum and Preferred using or separate paragraphs? Probably just list all items.
- Qualifications: Could be similar to Requirements. But we should not duplicate. The instruction says prefer a few substantive sections over many thin ones. So we can combine Minimum and Preferred into Requirements. Qualifications maybe not needed.
- Skills: Could extract skills like time management, communication, etc. But those are already in Requirements. Could create Skills section for those soft skills. However we need to avoid thin sections. Might be better to include them in Requirements.
Thus sections: About the role (unit description), Requirements (minimum + recommended), Pay, Schedule.
Check if any other specific content: "Preference will be given, by seniority, to those qualified nurses who were serially displaced within the 18 months following his/her displacement according toMNAcontract section 9.4 (f)(1)." That's a preference note; could be included in Requirements or About the role? It's a hiring preference. Could be placed in Requirements as a note.
Also "As with all job assignments, staff may be floated to areas where they are needed" - could be a responsibility or note. Could be included in About the role or Requirements.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include that preference note and floating statement.
We need to avoid boilerplate: remove EEO, equal opportunity, scam warning, application instructions, navigation, cookie, legal. The posting includes "Equal Opportunity Employer/Veterans/Disabled" at end - remove.
Also "As a health care organization, we have a responsibility to do everything in our power to care for and protect our patients, our colleagues and our communities. Beth Israel Lahey Health requires that all staff be vaccinated against influenza (flu) as a condition of employment. More than 35,000 people working together. Nurses, doctors, technicians, therapists, researchers, teachers and more, making a difference in patients' lives. Your skill and compassion can make us even stronger." This is somewhat boilerplate but maybe considered organizational description. It's not a standard EEO but could be considered generic marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph is not exactly EEO but could be considered generic fluff. However it's substantive? It mentions influenza vaccination requirement - that is a specific requirement (must be vaccinated). That's a substantive requirement (condition of employment). So we should keep that as a requirement (maybe under Requirements). The rest about 35,000 people etc is fluff; could be considered boilerplate. But we need to preserve ALL substantive information; we can drop non-substantive fluff. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove generic marketing fluff, but we should keep substantive info. The influenza vaccination requirement is substantive; we can keep that. The rest about 35,000 people etc may be considered filler; but not explicitly listed as boilerplate to remove. Safer to keep it? Might be considered non-substantive but not prohibited. However we want to avoid filler/placeholder text. The instruction: "Prefer a few substantive sections over many thin ones." So we could include a short paragraph about the organization under About the role maybe. But we need to decide.
I think we can include a brief "About the organization" paragraph under About the role or as a separate section? But we only have headings list; we could add a paragraph under About the role after unit description.
Thus About the role: includes unit description and maybe the organization statement about making a difference, vaccination requirement, etc.
But we need to avoid duplication.
Let's extract substantive pieces:
- Intro: "When you join the growing BILH team, you're not just taking a job, you’re making a difference in people’s lives." That's motivational; could be part of About the role.
- Schedule: "36hpw; 7a-7:30p, every other weekend and holiday rotation"
- Unit Description: "2 East is a 49bed general medical/surgical telemetry unit that provides care to adult and geriatric patients. The staff cares for patients with a wide variety of acute conditions and patients with multiple comorbidities."
- Preference note: "Preference will be given, by seniority, to those qualified nurses who were serially displaced within the 18 months following his/her displacement according toMNAcontract section 9.4 (f)(1)."
- Minimum Requirements list (as above)
- Recommended Requirements list (as above)
- Floating statement: "As with all job assignments, staff may be floated to areas where they are needed"
- Pay range: "$37.14 - $82.22" plus description about collective bargaining agreement.
- Influenza vaccination requirement: "Beth Israel Lahey Health requires that all staff be vaccinated against influenza (flu) as a condition of employment."
- Organization size/mission: "More than 35,000 people working together. Nurses, doctors, technicians, therapists, researchers, teachers and more, making a difference in patients' lives. Your skill and compassion can make us even stronger." This is fluff but maybe okay.
We need to output HTML fragment only.
We'll create sections:
About the role
When you join the growing BILH team, you're not just taking a job, you’re making a difference in people’s lives. 2 East is a 49‑bed general medical/surgical telemetry unit that provides care to adult and geriatric patients. The staff cares for patients with a wide variety of acute conditions and patients with multiple comorbidities. As with all job assignments, staff may be floated to areas where they are needed. Beth Israel Lahey Health requires that all staff be vaccinated against influenza (flu) as a condition of employment. More than 35,000 people working together. Nurses, doctors, technicians, therapists, researchers, teachers and more, making a difference in patients' lives. Your skill and compassion can make us even stronger.
But note: we included schedule? Actually schedule is separate.
We also need to include the preference note somewhere. Could be in About the role or Requirements. It's a hiring preference; maybe put in Requirements as a note.
Better: Add a paragraph under About the role about preference? Might be okay.
But we need to keep all info. Let's place preference note in Requirements section as a note.
Now Requirements section:
Requirements
- Current Massachusetts RN License
- Evidence of Continuing Education
- Prior experience working as a RN required; Med Surg experience preferred
- Current Telemetry experience or able to pass Telemetry Competency Exam within 90 days of beginning position
- Current AHA BLS Certification
- Utilizes appropriate time management skills
- Communicates effectively
- Preference will be given, by seniority, to those qualified nurses who were serially displaced within the 18 months following his/her displacement according to MNA contract section 9.4 (f)(1)
- Documented Professional Developmental activities (recommended)
- Knowledge of Critical Paths (recommended)
- Charge Nurse experience preferred (recommended)
- BSN Preferred (recommended)
- AHA ACLS Preferred (recommended)
But we need to differentiate minimum vs recommended? Not required but could be okay.
We could add a note that recommended items are preferred but not required. But we must not invent. The posting says "Recommended Requirements". So we can label them as (Preferred) or (Recommended). We'll keep as is.
Now Pay section:
Pay
Pay Range $37.14 - $82.22. This position is covered by a collective bargaining agreement. The pay range listed for this position is the base hourly wage range the organization reasonably and in good faith expects to pay for this position at this time. The pay range for this position is established and governed by the terms of the applicable collective bargaining agreement. Employees hired into this position will receive compensation consistent with the terms of the applicable collective bargaining agreement.
Schedule section:
Schedule
36 hours per week; 7:00 a.m.‑7:30 p.m., every other weekend and holiday rotation.
We need to ensure we used correct formatting
About the role
When you join the growing BILH team, you're not just taking a job, you’re making a difference in people’s lives. 2 East is a 49‑bed general medical/surgical telemetry unit that provides care to adult and geriatric patients. The staff cares for patients with a wide variety of acute conditions and patients with multiple comorbidities. As with all job assignments, staff may be floated to areas where they are needed. Beth Israel Lahey Health requires that all staff be vaccinated against influenza (flu) as a condition of employment. More than 35,000 people working together. Nurses, doctors, technicians, therapists, researchers, teachers and more, making a difference in patients' lives. Your skill and compassion can make us even stronger.
But note: we included schedule? Actually schedule is separate. We also need to include the preference note somewhere. Could be in About the role or Requirements. It's a hiring preference; maybe put in Requirements as a note. Better: Add a paragraph under About the role about preference? Might be okay. But we need to keep all info. Let's place preference note in Requirements section as a note. Now Requirements section:Requirements
- Current Massachusetts RN License
- Evidence of Continuing Education
- Prior experience working as a RN required; Med Surg experience preferred
- Current Telemetry experience or able to pass Telemetry Competency Exam within 90 days of beginning position
- Current AHA BLS Certification
- Utilizes appropriate time management skills
- Communicates effectively
- Preference will be given, by seniority, to those qualified nurses who were serially displaced within the 18 months following his/her displacement according to MNA contract section 9.4 (f)(1)
- Documented Professional Developmental activities (recommended)
- Knowledge of Critical Paths (recommended)
- Charge Nurse experience preferred (recommended)
- BSN Preferred (recommended)
- AHA ACLS Preferred (recommended)
Pay
Pay Range $37.14 - $82.22. This position is covered by a collective bargaining agreement. The pay range listed for this position is the base hourly wage range the organization reasonably and in good faith expects to pay for this position at this time. The pay range for this position is established and governed by the terms of the applicable collective bargaining agreement. Employees hired into this position will receive compensation consistent with the terms of the applicable collective bargaining agreement.
Schedule section:Schedule
36 hours per week; 7:00 a.m.‑7:30 p.m., every other weekend and holiday rotation.
We need to ensure we used correct formatting