Registered Nurse CDH Pediatrics Full-time Nights

We need to output HTML fragment with sections: About the role? The posting includes introductory paragraph about Northwestern Medicine, mission, etc. That could be "About the role" or maybe "About Northwestern Medicine". The instructions: 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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to extract substantive content: The posting includes: - Intro paragraph: "At Northwestern Medicine, every patient interaction makes a difference in cultivating a positive workplace. This patient-first approach is what sets us apart as a leader in the healthcare industry. As an integral part of our team, you'll have the opportunity to join our quest for better health care, no matter where you work within the Northwestern Medicine system. We pride ourselves on providing competitive benefits: from tuition reimbursement and loan forgiveness to 401(k) matching and lifecycle benefits, our goal is to take care of our employees. Ready to join our quest for better?" This is about the organization and benefits mention. - Job Description: "The Staff Nurse Inpatient reflects the mission, vision, and values of NM, adheres to the organization’s Code of Ethics and Corporate Compliance Program, and complies with all relevant policies, procedures, guidelines and all other regulatory and accreditation standards. A clinically competent, registered, professional nurse who prescribes, delegates and coordinates nursing care to the acutely ill patient through the nursing process of assessment, planning, intervention, implementation and evaluation. Effectively interacts with patient, significant others, and other health team members, while maintaining ANA standards of professional nursing practice." - Responsibilities: list bullet points (starting with "Collects and analyzes data..."). - Qualifications Required: list bullet points (BSN, IL RN, BLS, strong interpersonal skills, ability to collaborate, strong analytic abilities, ADN acceptable with commitment to obtain BSN within three years). - Preferred: list bullet points (Experience in specific clinical area, Additional Preferences for the Emergency Room and the Pediatric Emergency Room, Trauma Nurse Specialist (TNS), Emergency Communications Registered Nurse, Certified Pediatric Nurse, Certified Emergency Nurse). - Additional Information: includes EEO statement (should be removed as boilerplate), Background Check (maybe keep? It's not boilerplate? It's about background check process; could be considered relevant but maybe it's boilerplate? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Background check is not EEO but could be considered procedural; but it's not a benefit or requirement. Might be considered minor metadata; we could fold into a short

  or drop. Probably we can keep a short paragraph about background check? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Background check could be considered minor metadata; we could include a short

  summarizing that they conduct background checks including criminal history, etc. But we need to preserve ALL substantive information; is background check substantive? It's part of hiring process; maybe we keep it as a short paragraph. - Artificial Intelligence Disclosure: also maybe minor metadata; could be folded into short

  or dropped. Probably drop as it's not essential. - Benefits: "We offer a wide range of benefits that provide employees with tools and resources to improve their physical, emotional, and financial well-being while providing protection for unexpected life events. Please visit our Benefits section to learn more." This is vague; no specific benefits listed besides earlier mention of tuition reimbursement, loan forgiveness, 401(k) matching, lifecycle benefits. The earlier intro mentioned those. So we have some specific benefits mentioned: tuition reimbursement, loan forgiveness, 401(k) matching, lifecycle benefits. Also sign-on bonus eligibility details: "Sign-on Bonus Eligibility (if sign-on bonus offered for position): Internal employees and rehires who left Northwestern Medicine within 1 year are not eligible for the sign on bonus. Exception: New graduate internal employees seeking their first licensed clinical position at NM may be eligible depending upon the job family." That's specific about sign-on bonus eligibility. So we have benefits and sign-on bonus info. We should not create a Benefits section unless posting actually states them. It does state some benefits (tuition reimbursement, loan forgiveness, 401(k) matching, lifecycle benefits) and sign-on bonus eligibility. So we can include a Benefits section with those specifics. We should not create Pay or Schedule sections because not mentioned. We need sections: maybe About the role (intro), Responsibilities, Qualifications (maybe combine Required and Preferred?), Benefits. Could also have a "Preferred Qualifications" subsection but we can combine into Qualifications with subheadings? The instruction only mentions using

  for section headings; we can have multiple

  sections. Could have "Qualifications" and inside we can have

  for required and

  for preferred? Or we could separate Required and Preferred as separate sections? The instruction says prefer a few substantive sections over many thin ones. So maybe combine Required and Preferred into one Qualifications section with two lists: Required (ul) and Preferred (ul). Or we could have "Required Qualifications" and "Preferred Qualifications" as subheadings but those would be

  maybe not allowed; we only have

  . Better to have one Qualifications section with two lists labeled via

  or . But we need to use

  • for any list of duties/requirements/benefits. So we can have

    Required Qualifications:

    then
    ... and

    Preferred Qualifications:

    then
    ... Similarly for Responsibilities we have a list. For Benefits we have a list of specific benefits and sign-on bonus eligibility; we can make a
    . Now about the intro: we could have an

    About the role

    with

    containing the introductory paragraph(s). The intro includes mention of benefits; but we will also have a Benefits section later; we should not duplicate. We could keep the intro focusing on mission/patient-first approach, opportunity, etc., and maybe mention that they provide competitive benefits but we can keep that as part of intro; but then Benefits section will repeat some. To avoid duplication, we could keep intro without benefits details, but we must preserve ALL substantive information; we cannot omit the benefit details. So we need to include them somewhere. Could include them in Benefits section only, and intro can omit the benefit mention. However the intro sentence: "We pride ourselves on providing competitive benefits: from tuition reimbursement and loan forgiveness to 401(k) matching and lifecycle benefits, our goal is to take care of our employees." That's substantive; if we omit it, we lose info. So we need to keep it. We could keep it in the intro paragraph, and Benefits section could just list those same benefits; duplication is okay? The instruction says preserve ALL substantive information; duplication is not prohibited but we should avoid unnecessary duplication? Not explicitly forbidden. However we might want to avoid repeating same info; but it's okay if we keep both. However we could restructure: intro paragraph about mission and opportunity; Benefits section lists the specific benefits; we could drop the benefit mention from intro to avoid duplication, but then we lose the sentence about "We pride ourselves on providing competitive benefits..." which is substantive. Could we rephrase to keep the sentiment but not list specifics? The sentence includes specifics; we could keep the sentence but then Benefits section would repeat the list; duplication may be okay. I'd rather keep the intro as is (including benefits mention) and then Benefits section also list them; it's not harmful. Now we need to remove boilerplate: EEO statement, background check maybe keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Background check is not EEO but could be considered legal; but it's about hiring process; maybe we keep it as minor metadata? The instruction says fold minor metadata into a short

    or drop it. So we could include a short

    about background check. However the background check paragraph includes details: "Northwestern Medicine conducts a background check that includes criminal history on newly hired team members and, at times, internal transfers. If you are offered a position with us, you will be required to complete an authorization and disclosure form that gives Northwestern Medicine permission to run the background check. Results are evaluated on a case-by-case basis, and we follow all local, state, and federal laws, including the Illinois Health Care Worker Background Check Act." That's substantive but maybe considered boilerplate? It's fairly standard; but it's not EEO. I'd keep it as a short paragraph under maybe a section "Background Check"? But we are not supposed to create sections unless there is real specific content; we have content. Could we add a section "Background Check"? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Background Check is not in the list; but we could still use

    for any heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Likely we should stick to those headings; adding other headings may be against instruction. Better to fold background check into a short

    under maybe "About the role" or at end. Since it's minor metadata, we can fold into a short

    after the intro. Similarly AI disclosure can be dropped. Now we need to ensure we don't include any headings with empty/filler content. Thus final HTML:

    About the role

    At Northwestern Medicine, every patient interaction makes a difference in cultivating a positive workplace. This patient-first approach is what sets us apart as a leader in the healthcare industry. As an integral part of our team, you'll have the opportunity to join our quest for better health care, no matter where you work within the Northwestern Medicine system. We pride ourselves on providing competitive benefits: from tuition reimbursement and loan forgiveness to 401(k) matching and lifecycle benefits, our goal is to take care of our employees. Ready to join our quest for better?

    Responsibilities

    • Collects and analyzes data, identifies expected outcomes, develops and implements an individualized plan, coordinates care delivery and evaluates progress toward attainment of outcomes.
    • Directs care and determines the appropriate utilization of any assistant involved in providing direct patient care.
    • Collaborates with patient, family, physicians and ancillary staff.
    • Creates a documented plan, focused on outcomes and decisions related to the care and delivery of services that indicates communications with patients, families, and others.
    • Participates in shared governance, committee work, and unit projects.
    • Evaluates and documents the patient’s responses to nursing interventions in the health record and properly individualizes the plan of care based on the evaluation of findings.
    • Utilizes the best available evidence, including research findings to guide practice decisions.

    Qualifications