RN Medical Surgical Telemetry Days

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Remove boilerplate. Must preserve all substantive info. Let's parse the posting: - "$15,000 Sign on Bonus for Eligible Candidates Join Baylor Scott & White - Lake Pointe Rowlett as a Registered Nurse and be part of something better!" This is a sign-on bonus. That is a benefit/pay? It's a sign-on bonus. Could be part of Benefits or Pay. Since we only include sections if real content. We have mention of "$15,000 Sign on Bonus". That's a specific benefit. Also mention of benefits: Immediate eligibility for health and welfare benefits, 401(k) savings plan with dollar-for-dollar match up to 5%, Tuition Reimbursement, PTO accrual beginning Day 1. Also note benefits may vary. - Patient Population: Stroke, Chest Pain, Med-surg, Telemetry - Patient Ratios: 1:4-5 - Number of Rooms: 26 on 2 South and 4-10 beds on 2 North - Shift: Full-Time Days - Required Experience: Candidates MUST have minimum of 1yr of true, recent Telemetry RN experience. - About Baylor Scott & White Medical Center – Lake Pointe description. - About Us (BSWH) description. - Benefits list. - Job Summary (some prose). - Essential Functions Of The Role (list of duties). - Key Success Factors (list of skills/qualities). - Belonging Statement (maybe not needed? It's a statement about belonging; could be part of About Us? Might be considered boilerplate? It's not EEO but it's a values statement. Might keep as part of About Us? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Belonging Statement is not exactly EEO but could be considered similar. Might keep? It's a statement about belonging; could be considered part of culture. Might keep as a paragraph under About Us? But we have no section for culture. Could include as a paragraph under About Us? But we already have About Us section maybe. We'll decide later. - Qualifications list: Grad of Accredited Program, RN License, 1 Years of recent Telemetry RN experience, Basic Life Support (BLS) or obtain with (30) thirty days of hire or transfer. - Also mention of "Key Success Factors" which includes skills. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content: - About the role: Could be the Job Summary? Or description of role? The posting includes "Job Summary As a Registered Nurse, oversee patient care using a professional practice model..." That's about the role. So we can put that under About the role heading. - Responsibilities: Essential Functions Of The Role (list of duties). That's responsibilities. - Requirements: Could be shift, patient ratios, etc? Or maybe "Required Experience" etc. But we have Qualifications separate. Usually Requirements could be experience, licensure, etc. But we have Qualifications section for credentials. We'll decide: Requirements could include shift, patient ratios, etc? However the instruction: Use headings only when posting has real specific content. We have content for Shift, Patient Ratios, Number of Rooms, Patient Population. Those could be under About the role or maybe a separate section like "Role Details". But we don't have a heading for that; we could put them under About the role as prose or list. - Qualifications: list of education/license/experience/BLS. - Skills: Key Success Factors (skills, abilities). Could be under Skills. - Benefits: list of benefits plus sign-on bonus. - Pay: Not explicitly stated besides sign-on bonus. No base pay. So we should not create Pay section unless posting actually states them. It does not state base pay, only sign-on bonus. Should we include Pay? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Benefits (yes). It does not state Pay (base salary). Sign-on bonus is a benefit, not base pay. So we should not create Pay section. - Schedule: Shift: Full-Time Days. That's schedule info. So we can create Schedule section with that content. Thus sections: About the role, Responsibilities, Requirements?, Qualifications, Skills, Benefits, Schedule. Do we need Requirements? Could combine experience etc into Qualifications. But we have separate Qualifications heading. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Requirements if we have content. What would be Requirements? Could be "Candidates MUST have minimum of 1yr of true, recent Telemetry RN experience." plus maybe "Grad of Accredited Program", "RN License", "BLS". Those are qualifications. But we could treat Requirements as experience and licensure, and Qualifications as education? However the posting lumps them together. To avoid duplication, we could put all under Qualifications and omit Requirements. But we need to decide if we should include Requirements heading with content like "Minimum 1 year recent Telemetry RN experience". That is a requirement. We could also include "Grad of an accredited nursing program" and "Current RN license" as requirements. But then Qualifications could be something else like "Key Success Factors"? Actually Key Success Factors are skills. So we could map: - Requirements: experience, licensure, BLS. - Qualifications: education (Grad of Accredited Program) maybe? But that's also a requirement. Hmm. Better to follow typical structure: Requirements = experience, licensure, certifications. Qualifications = education, maybe additional preferred qualifications. But the posting does not separate preferred vs required. It lists: Grad of Accredited Program, RN License, 1 Years of recent Telemetry RN experience, Basic Life Support (BLS) or obtain with (30) thirty days of hire or transfer. All are required. Thus we could put all under Requirements and omit Qualifications, or we could put under Qualifications and omit Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we should combine to avoid thin sections. We could have Qualifications section that includes education, licensure, experience, BLS. Then we could skip Requirements. Or we could have Requirements section that includes experience, licensure, BLS, and Qualifications section that includes education. But that would be thin. Thus better to have one section for Qualifications (or Requirements) that includes all. Which heading is more appropriate? The posting uses "Qualifications" heading later: "Qualifications Grad of Accredited ProgramRN License1 Years of recent Telemetry RN experienceBasic Life Support (BLS) or obtain with (30) thirty days of hire or transfer". So the posting itself uses "Qualifications". So we should use Qualifications heading for that content. Thus we will not include Requirements heading. Now About the role: Use Job Summary paragraph. Responsibilities: Essential Functions Of The Role (list). We'll convert each sentence into

items. Skills: Key Success Factors (list). We'll convert each bullet into

. Benefits: Include sign-on bonus and the list: Immediate eligibility for health and welfare benefits, 401(k) savings plan with dollar-for-dollar match up to 5%, Tuition Reimbursement, PTO accrual beginning Day 1. Also note benefits may vary based upon position type and/or level. We'll include that note as prose. Schedule: Shift: Full-Time Days. Also maybe mention patient ratios etc? But schedule is just shift. We'll put that. We also have Patient Population, Patient Ratios, Number of Rooms. Where to put? Could be under About the role as additional details. We'll incorporate them into About the role paragraph or as a list under About the role? The instruction: Use

for prose. We could make a

for those details under About the role? But About the role heading expects prose; we could add a
after the

under same section? The instruction didn't forbid mixing lists under a heading. It said use

• for any list of duties/requirements/benefits, and

  for prose. So we can have a

  for prose description, and a

  for list of details like patient population, ratios, rooms. That seems fine. Thus About the role section:

  About the role

  then a

  with the job summary prose. Then a

  with items: Patient Population: Stroke, Chest Pain, Med-surg, Telemetry; Patient Ratios: 1:4-5; Number of Rooms: 26 on 2 South and 4-10 beds on 2 North. Now Responsibilities:

  Responsibilities

  then
  with each essential function as
  • . Need to extract each sentence from "Essential Functions Of The Role". Let's parse: "As an RN, conduct detailed clinical assessments and prioritize patient and family needs. Create, implement, and evaluate care plans. Adjust plans to reach desired outcomes. Building relationships, managing discomfort, staying professional are vital in therapeutic connections with patients and families. Creating care plans reflecting values aids in resolving issues. You will help educate patients, families, nurses, and community members. Empower them with knowledge for better healthcare choices. Assess and document learning needs regularly. Work with colleagues and community to create a care plan. Delegate tasks carefully and follow up promptly. You'll use different strategies for problem-solving with patients, families, and staff. Recognize limitations and prioritize safety, effectiveness, and efficiency in patient care planning and delivery. Achieve goals through teamwork, recognize contributions, commit to growth. Contribute to peers' development, show community service commitment." We'll turn each into
  • . Now Qualifications:

    Qualifications

    then
    with items: Grad of Accredited Program; RN License; 1 Years of recent Telemetry RN experience; Basic Life Support (BLS) or obtain with (30) thirty days of hire or transfer. Now Skills:

    Skills

    then
    with items from Key Success Factors. Let's list: - A deep understanding of nursing and patient care standards, as well as procedures. - Know nursing laws, rules, standards, and guidelines in your area. - Understand hospital procedures and rules. - Proficiency in medical terms, focusing on health, disease prevention, management, common meds, and their side effects. - Respect for medical and professional nursing ethics and patient privacy rights. - Exceptional communication skills, allowing for clear expression of thoughts both verbally and in writing. - Positive social skills to facilitate interactions with a diverse range of parties. - Excellent problem-solving capabilities, driving effective critical thinking. - Basic computer skills, encompassing areas such as Microsoft Office, information security, scheduling and payroll systems, electronic medical documentation, and email. Now Benefits:

    Benefits

    then
    with items: $15,000 Sign on Bonus for Eligible Candidates; Immediate eligibility for health and welfare benefits; 401(k) savings plan with dollar-for-dollar match up to 5%; Tuition Reimbursement; PTO accrual beginning Day 1. Also note: Benefits may vary based upon position type and/or level. We'll add a

    after the list for that note. Now Schedule:

    Schedule

    then

    Full-Time Days. We should not include any boilerplate like "About Us", "Belonging Statement", "Job Summary" heading (we used About the role). Also we should not include "Patient Population" etc as separate headings. Now ensure we don't repeat job title. Not included. Now output only HTML fragment. Let's craft. Check