Per Diem Clinical Nurse-Days - Mount Sinai Hospital - NEURO ICU

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: - 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. Now, analyze the provided job posting. The posting includes: - Job Description: "The (Per Diem) Clinical Nurse is a Registered Professional Nurse who provides safe, competent quality care based on nursing theory and research to a designated group of patients and significant others." - Responsibilities: broken into subsections: Patient Care, Patient Experience, Quality and Safety, Operations, Professional Development. Each has bullet points. - Qualifications: list of education, licensure, certifications, collective bargaining unit. - Employer Description: "Strength through Unity and Inclusion" and "About The Mount Sinai Health System" – this is employer boilerplate, but it's substantive about the employer. However, the instruction says to remove boilerplate like EEO/equal-opportunity. The employer description includes mission, size, rankings. It might be considered employer branding. The rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The employer description includes EEO statement at the end. But the description before that is about the health system. Should I include it? The instruction says "Preserve ALL substantive information". The employer description is substantive about the employer. However, the user might want only the job-specific sections. The example headings include "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". There's no "About the employer" heading. But the posting includes "Employer Description" and "About The Mount Sinai Health System". Could be folded into an "About the role" or "About the employer" section. But the rule: "include a section ONLY when the posting has real, specific content for it". The employer description is real and specific. However, the instruction also says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The EEO statement is at the end. The employer description includes that. I think I should include the employer description but omit the EEO boilerplate. The compensation section is present: "Compensation The Mount Sinai Health System (MSHS) provides salary ranges... The salary range for the role is $85.9387 - $85.9387 Hourly." That's specific pay information. So I should include a Pay section. Also, there is no schedule or benefits explicitly mentioned. The posting mentions "Per Diem" in the title, but not schedule details. The compensation mentions hourly rate. No benefits listed. So no Benefits or Schedule sections. Now, structure: - About the role: could include the job description paragraph and maybe the employer description? But the employer description is separate. I'll create an "About the role" section with the job description paragraph. Then maybe an "About the employer" section? But the allowed headings are listed: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the employer" is not listed. However, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not exhaustive. But to be safe, I'll use "About the role" for the job description, and perhaps include employer description under "About the role" or separate "About the employer". But the instruction says "Do NOT repeat the job title as a heading". The job title is "(Per Diem) Clinical Nurse". The page already shows it. So I won't include a heading for the title. I'll create sections: 1. About the role: includes the job description paragraph and maybe the employer description? The employer description is about the health system, not the role. Could be separate. But the rule says "Prefer a few substantive sections over many thin ones." I'll include employer description under "About the role" or create "About the employer". Since the example headings don't include "About the employer", I'll fold it into "About the role" or maybe omit it? The instruction says "Preserve ALL substantive information". The employer description is substantive. I'll include it as a subsection under "About the role" or as a separate section with heading "About the employer". But the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings. I'll use "About the employer" as an h3. But the user might expect only the listed headings. However, the instruction says "e.g." meaning examples. I think it's okay to add "About the employer". But to be safe, I'll include the employer description in the "About the role" section as a paragraph. Alternatively, I could create a section "Employer Overview". But I'll follow the pattern: use h3 for each major section. Let's outline: - About the role: job description paragraph. - Responsibilities: with subsections? The responsibilities are grouped into Patient Care, Patient Experience, Quality and Safety, Operations, Professional Development. Each has bullet points. I could make each a sub-list under Responsibilities. Use

  • for each bullet. But the subsections are headings within responsibilities. The rule says use

    for section headings. Should I make each a separate h3? The example headings include "Responsibilities" as a section. The posting has subsections. I could make them h4? But the rule only mentions h3. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention subheadings. I think I should keep Responsibilities as one section with sub-lists grouped by category. Use

    for Responsibilities, then within that, use

    ? But the output is HTML fragment, and they didn't forbid h4. However, they said "use

    for section headings". Might be okay to use h4 for subsections. But to keep it simple, I'll make each responsibility category a separate h3? That would create many sections: Patient Care, Patient Experience, Quality and Safety, Operations, Professional Development. But the example headings include "Responsibilities" as a single heading. The posting has multiple responsibility categories. I think it's better to have one Responsibilities section with subheadings (maybe h4) or just list all bullets under Responsibilities with category labels as bold text. But the rule: "Use

    • for any list of duties/requirements/benefits". The duties are listed under each category. I could create a list for each category, with the category as a heading (maybe

      ) then

      . But the instruction says "use

      for section headings". It doesn't say we cannot use h4. I'll use h4 for subsections within Responsibilities. But the output should be clean. Let's see similar tasks: they often want each major section as h3, and within responsibilities, they might want subsections as h4. However, the instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests the top-level sections are those. Responsibilities is one top-level section. So I'll keep Responsibilities as one h3, and inside, I'll use

      for each category (Patient Care, Patient Experience, etc.) then

      • for each bullet. Similarly, Qualifications: there is a list of qualifications. That could be a section "Qualifications" with
        • . Compensation: Pay section with the salary range. Employer Description: I'll include as "About the employer" h3. But the EEO statement at the end is boilerplate, remove. Also, the collective bargaining unit is part of qualifications. Now, let's parse the content. Job Description: "The (Per Diem) Clinical Nurse is a Registered Professional Nurse who provides safe, competent quality care based on nursing theory and research to a designated group of patients and significant others." Responsibilities: Patient Care: - Delivers patient care by incorporating the tenets of the professional practice model of Relationship Centered Care and through the application of the nursing process based upon theory, research, evidence-based practice, and approved organizational nursing standards. - Assesses and evaluates patient care needs and applies critical thinking skills in patient care management. - Integrates relevant assessment and intervention skills in the delivery of nursing care. - Collaborates with the interdisciplinary healthcare team in the development, implementation, and evaluation of the plan of care. - Prioritizes all aspects of patient care including teaching, rounding, coaching, and planning after hospital care and delegating to others as appropriate. - Educates patients and caregivers while anticipating needs and readiness to learn, about their plan of care, transition of care, promotion of health, and prevention of disease. - Communicates effectively and professionally with patients, family and all members of the Interdisciplinary Patient Care Team. - Manages assignments within the Care Delivery Model of Modified Primary Nursing and demonstrates allocation of material resources effectively. Patient Experience: - Role models the tenets of Mount Sinai Relationship Centered Care (MSHRCC) through facilitation of the following actions including, but not limited to, Admission Welcome, Bedside shift Report, HELP, AM/PM Care, 5 Minute Sit Down, Purposeful Hourly Rounding, Medication Review, Discharge Wrap Up, and MD/RN Unit Collaboration. - Establishes and maintains a therapeutic relationship with the patient and family. - Uses evidence-based practices to increase understanding of patients perceptions of care. - Initiates service recovery for patients and family members who have concerns and escalates to Clinical Nurse Manager/Assistant Nurse Manager/Nursing Shift Manager or Patient Relations as needed. - Demonstrates caring, respect, compassion, empathy and active listening through dialogue, body language and actions. - Supports staff use of evidence-based practices to increase understanding of patients perceptions of care. - Conducts Purposeful Hourly Rounding (PHR) on assigned patients addressing the 4 Ps. Quality and Safety: - Practices safe and efficient patient-centered care, identifying and escalating barriers and opportunities for improvement. - Demonstrates clinical skills and knowledge crucial to quality and safety in the patient population served. - Implements process improvement strategies based on institutional, evidence-based ensure and procedures. (typo: "ensure" maybe "standards") - Engages in formal and informal peer and institutional review processes. - Collaborates with interdisciplinary teams to create and implement quality improvement projects, evidence-based practice activities and nursing research studies. - Contributes to quality and safety practices and required compliance measures. - Implements principles of high reliability to identify and avoid high risk behaviors to provide a safe environment for patients. - Escalates potential safety hazards or gaps from