Registered Nurse - Brain Injury Unit Spaulding

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, we need to decide what sections to include. The posting includes: - Summary: "Job Summary Accountable for interpreting the plan of medical care, assessment of patients' clinical decision-making regarding nursing care, assuring nursing care is provided in a safe and competent manner, providing individualized nursing care, and evaluating nursing care for groups of patients." - Essential Functions: list of duties. - Qualifications: Education, Licenses and Credentials, Experience, Knowledge, Skills and Abilities. - Additional Job Details (if Applicable): Physical Requirements (list). Also Remote Type, Work Location, Scheduled Weekly Hours, Employee Type, Work Shift. - Pay Range: "$37.76 - $82.96/Hourly Grade SRHRN460" - Benefits: mention "In addition to competitive base pay, we offer comprehensive benefits, career advancement opportunities, differentials, premiums and bonuses as applicable and recognition programs..." - EEO statement etc (boilerplate to remove). - Also "At Mass General Brigham, we believe in recognizing and rewarding..." that's about benefits/compensation. - Also "Mass General Brigham Competency Framework" (maybe not needed). We need to produce sections: About the role (maybe summary), Responsibilities (essential functions), Requirements (maybe qualifications?), Qualifications (education/licenses), Skills (knowledge, skills and abilities), Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID. We need to preserve all substantive info, not invent. We must not include sections with placeholder text like "commensurate with experience". Not present. We need to decide which sections have content. - About the role: Could use the Job Summary paragraph. - Responsibilities: Essential Functions list. - Requirements: Could be Education, Licenses and Credentials, Experience? But we also have Qualifications section separate. The instruction says use headings for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We could treat: - About the role: Job Summary. - Responsibilities: Essential Functions. - Requirements: maybe "Can this role accept experience in lieu of a degree? No" plus maybe "Patient Care? Yes". But those are minor. Could also include "Education Associate's Degree Nursing required or Bachelor's Degree Nursing preferred". However that seems more qualifications. The distinction between Requirements and Qualifications is ambiguous but we need to follow instruction: include sections only when posting has real specific content for it. We can decide to put education/license/experience under Qualifications, and maybe Requirements could be empty? Better to avoid empty sections. So we could combine Requirements and Qualifications? But we must use headings as given; we can decide to not include Requirements if no distinct content separate from Qualifications. However the posting does have "Qualifications Education ... Licenses and Credentials ... Experience ... Knowledge, Skills and Abilities". That's typical qualifications. So we can put that under Qualifications heading. Then maybe Requirements could be something like "Patient Care? Yes" and "Can this role accept experience in lieu of a degree? No". That's specific. So we can include Requirements heading with those two points. - Skills: Knowledge, Skills and Abilities list. - Benefits: paragraph about comprehensive benefits etc. - Pay: Pay Range. - Schedule: Scheduled Weekly Hours, Work Shift, Remote Type (Onsite), Work Location maybe. We need to avoid boilerplate like EEO, competency framework, etc. We need to use

for each section heading. Inside sections, use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to output only HTML fragment. Let's extract content. Job Summary: "Accountable for interpreting the plan of medical care, assessment of patients' clinical decision-making regarding nursing care, assuring nursing care is provided in a safe and competent manner, providing individualized nursing care, and evaluating nursing care for groups of patients." Essential Functions list: - Maintain accurate, detailed reports, and records. - Administer medications to patients and monitor patients for reactions or side effects. - Record patients' medical information and vital signs. - Monitor, record, and report symptoms or changes in patients' conditions. - Consult and coordinate with healthcare team members to assess, plan, implement, or evaluate patient care plans. - Modify patient treatment plans as indicated by patients' responses and conditions. Qualifications: Education: Associate's Degree Nursing required or Bachelor's Degree Nursing preferred Licenses and Credentials: Registered Nurse [RN - State License] - Generic - HR Only required Experience: Clinical nursing experience 0-1 year required Knowledge, Skills and Abilities list: - Familiarity with the principles and skills needed for practical nursing to provide patient care and treatment. - Knowledgeable of the care required by respective age groups for which care is being provided. - Ability to maintain confidentiality and secure sensitive information. - Knowledge of medical terminology. - Excellent verbal and communication skills. - Ability to accurately screen and triage acute patients. Additional Job Details (Physical Requirements) list many items. Should we include under Requirements? Or maybe under a separate section? The instruction only allows those headings; we could put physical requirements under Requirements or maybe under Qualifications? But they are not qualifications. Could be under Requirements. However we already used Requirements for patient care and experience-in-lieu. Could we expand Requirements to include physical requirements? The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not strict that we must only use those exact headings? It says use those for section headings. Likely we should only use those headings. So we need to map all content into those categories. Thus we need to decide where to put physical requirements. Could be under Requirements (as they are job requirements). Or maybe under Qualifications? But they are not qualifications. I'd put them under Requirements. Thus Requirements heading will contain: - Patient Care? Yes - Can this role accept experience in lieu of a degree? No - Physical Requirements list (many items). Could be a list. But we need to avoid too thin sections; we can combine. Now Benefits: "In addition to competitive base pay, we offer comprehensive benefits, career advancement opportunities, differentials, premiums and bonuses as applicable and recognition programs designed to celebrate your contributions and support your professional growth." Also earlier: "At Mass General Brigham, we believe in recognizing and rewarding the unique value each team member brings to our organization. Our approach to determining base pay is comprehensive, and any offer extended will take into account your skills, relevant experience if applicable, education, certifications and other essential factors. The base pay information provided offers an estimate based on the minimum job qualifications; however, it does not encompass all elements contributing to your total compensation package." That's more about pay/compensation, but we have Pay section for range. The benefits paragraph is separate. We could combine benefits statement under Benefits heading. Pay: "$37.76 - $82.96/Hourly Grade SRHRN460" Schedule: "Scheduled Weekly Hours 36", "Employee Type Regular", "Work Shift Day (United States of America)", "Remote Type Onsite", "Work Location 1575 Cambridge Street". Also maybe "Scheduled Weekly Hours 36" is schedule. We need to avoid duplication. Now we need to output HTML. Structure:

  About the role

  Accountable for interpreting the plan of medical care, assessment of patients' clinical decision-making regarding nursing care, assuring nursing care is provided in a safe and competent manner, providing individualized nursing care, and evaluating nursing care for groups of patients.

  Responsibilities

  • Maintain accurate, detailed reports, and records.
  • Administer medications to patients and monitor patients for reactions or side effects.
  • Record patients' medical information and vital signs.
  • Monitor, record, and report symptoms or changes in patients' conditions.
  • Consult and coordinate with healthcare team members to assess, plan, implement, or evaluate patient care plans.
  • Modify patient treatment plans as indicated by patients' responses and conditions.

  Requirements

  • Patient Care: Yes
  • Accept experience in lieu of a degree: No
  • Physical Requirements:
    • Standing Frequently (34-66%)
    • Walking Frequently (34-66%)
    • Sitting Occasionally (3-33%)
    • Lifting Frequently (34-66%) 35lbs+ (w/assisted device)
    • Carrying Frequently (34-66%) 20lbs - 35lbs
    • Pushing Occasionally (3-33%)
    • Pulling Occasionally (3-33%)
    • Climbing Rarely (Less than 2%)
    • Balancing Frequently (34-66%)
    • Stooping Occasionally (3-33%)
    • Kneeling Occasionally (3-33%)
    • Crouching Occasionally (3-33%)
    • Crawling Rarely (Less than 2%)
    • Reaching Frequently (34-66%)
    • Gross Manipulation (Handling) Frequently (34-66%)
    • Fine Manipulation (Fingering) Frequently (34-66%)
    • Feeling Constantly (67-100%)
    • Foot Use Rarely (Less than 2%)
    • Vision - Far Constantly (67-100%)
    • Vision - Near Constantly (67-100%)
    • Talking Constantly (67-100%)
    • Hearing Constantly (67-100%)
  But nested lists may be okay. However instruction: Use
  • for any list of duties/requirements/benefits. It didn't forbid nested lists. Could flatten physical requirements as separate list under Requirements heading. Could do:

    Requirements

    • Patient Care: Yes
    • Accept experience in lieu of a degree: No

    Physical Requirements

    ... but we cannot use h4 because only h3 headings allowed? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could keep physical requirements as part of Requirements list items, maybe as a sublist. But we need to preserve all substantive information; we can include them as list items. Simplify: Under Requirements, we can have a list that includes each physical requirement as a separate list item. That will be long but okay. Thus:

    Requirements

    • Patient Care: Yes
    • Accept experience in lieu of a degree: No
    • Standing Frequently (34-66%)
    • Walking Frequently