Director, Nursing Excellence
Children's Minnesota · Minneapolis, MN · 1 mo ago
HealthcareFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Children’s Minnesota" (organization description) then "Position Summary". We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections when posting has real, specific content. We need to extract content.
The posting includes:
- About Children’s Minnesota (organization description). This could be "About the role"? Actually "About the role" is not present; we have "About Children’s Minnesota". The instruction says use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections when posting has real, specific content. We need to extract content.
The posting includes:
- About Children’s Minnesota (organization description). This could be "About the role"? Actually "About the role" is not present; we have "About Children’s Minnesota". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings if appropriate. The "About Children’s Minnesota" is about the organization, not the role. Could be considered "About the role"? Not exactly. But we could treat it as "About the role"? Might be okay but maybe better to not create a heading if not matching. However we need to preserve all substantive information. We could put that description under a
without a heading? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings, but not required to use all. We need to include a section ONLY when the posting has real, specific content for it. So we need to decide which sections have content. We have: - Position Summary: describes role responsibilities. That could go under "Responsibilities". Also there are duties like development, implementation, evaluation of programs, collaboration, etc. So we can put under Responsibilities. - Location, DHS Background Study Required?, License/Certification/Registration, Education, Experience, Knowledge/Skills/Abilities: these are qualifications/requirements. Could split into Requirements (license, education, experience) and Qualifications (maybe certifications) and Skills (knowledge/skills/abilities). But we need to avoid thin sections. Perhaps combine into one "Requirements" section covering license, education, experience, and maybe certifications. Then "Skills" for knowledge/skills/abilities. - Benefits: mention medical, dental, vision, retirement, fringe benefits, shift differentials, etc. So we have Benefits content. - Pay: mention posted salary market competitive range, annual salaries based on full-time, prorated for part-time, factors considered. That's Pay content. - Schedule: Not explicitly mentioned; only mention full-time 40 hrs per week, part-time prorated. No explicit schedule details like shift work. Might not have enough to create Schedule section. Could skip. - About the role: we have Position Summary which could be considered About the role. But we already used Responsibilities for duties. Could use About the role for a brief overview of the role (position summary). Then Responsibilities for detailed duties. However the instruction says prefer a few substantive sections over many thin ones. So maybe combine About the role and Responsibilities into one section? But we need headings. Could use "About the role" for position summary paragraph, and "Responsibilities" for bullet list of duties. That seems reasonable. We need to remove boilerplate: EEO, equal opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. The posting includes EEO statement at end; we should remove that. Also remove lines about "All job offers are contingent upon successful completion..." maybe that's not boilerplate? It's about contingencies; could be considered part of requirements? Might be considered boilerplate but it's substantive? It's about hiring process; maybe we can keep as part of Requirements? But it's not about qualifications. Might be considered administrative; but we can keep if not boilerplate. However it's about contingencies; could be considered generic. Safer to remove? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The contingency statement is not exactly those categories, but could be considered legal? It's about job offer contingencies; might be considered legal. I'd remove it to be safe. Also remove "Children’s Minnesota is proud to be recognized by Modern Healthcare as one of 2023’s Top Diversity Leaders." That's accolades; could be kept under About Children’s Minnesota? It's about organization; we can keep. We need to preserve all substantive information; not invent or summarize away detail. Let's extract content: About Children’s Minnesota paragraph: "Children’s Minnesota is one of the largest pediatric health systems in the United States and the only health system in Minnesota to provide care exclusively to children, from before birth through young adulthood. An independent and not-for-profit system since 1924, Children’s Minnesota is one system serving kids throughout the Upper Midwest at two free-standing hospitals, nine primary care clinics, multiple specialty clinics and seven rehabilitation sites. As The Kids Experts™ in our region, Children’s Minnesota is regularly ranked by U.S. News & World Report as a top children’s hospital. Find us on Facebook @childrensminnesota or on Twitter and Instagram @childrensmn. Please visit childrensMN.org. Children’s Minnesota is proud to be recognized by Modern Healthcare as one of 2023’s Top Diversity Leaders. The national honor recognizes the top diverse healthcare executives and organizations influencing public policy, care delivery, and promoting diversity, equity and inclusion in their organizations and the industry." We can keep that as a paragraph under maybe "About the role"? But it's about organization. Could use "About the role" heading but content is about organization; maybe better to use "About the role" for position summary, and put organization description under a generic
without heading? But 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 suggests using those. To be safe, we could put organization description under a heading "About the role" albeit not perfect but still a section. Or we could not use a heading and just put
. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot have other headings, but to follow the pattern. I'll use "About the role" for the organization description? Might be confusing. Better to use "About the role" for position summary (which is about the role). Then we need another section for organization description? Could incorporate into "About the role" as a brief intro? But the position summary is separate. Let's think: The posting has "About Children’s Minnesota" then "Position Summary". So we could have two sections: "About the role" (maybe we treat as "About Children’s Minnesota"? Not ideal). Another approach: Use "About the role" for the position summary, and put the organization description as a
before any heading (since no heading needed). The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must wrap everything in headings; we can have free
before headings. So we can output a
with organization description, then
About the role
with position summary paragraph, thenResponsibilities
with bullet list of duties, thenRequirements
with bullet list of license, education, experience, certifications, etc., thenSkills
with bullet list of knowledge/skills/abilities, thenBenefits
with bullet list of benefits, thenPay
with paragraph about salary. No Schedule. We must ensure we don't create sections with filler like "commensurate with experience". We have specific content. Now extract details: Position Summary (from posting): "The Director, Nursing Excellence provides strategic and operational leadership for nursing professional practice, nursing excellence, and clinical outcomes across the organization. This role is responsible for the development, implementation, and evaluation of programs supporting professional governance, Magnet designation, evidence-based practice, and empirical outcomes. This position collaborates with nursing, medical, and operational leaders to align nursing practice with organizational priorities, ensuring high-quality, patient-centered, and cost-effective care. The Director advances continuous improvement, fosters professional development, and ensures compliance with regulatory and accreditation requirements." We can keep as paragraph. Responsibilities: The duties are essentially the same as position summary; but we can break into bullet list: - Provide strategic and operational leadership for nursing professional practice, nursing excellence, and clinical outcomes across the organization. - Develop, implement, and evaluate programs supporting professional governance, Magnet designation, evidence-based practice, and empirical outcomes. - Collaborate with nursing, medical, and operational leaders to align nursing practice with organizational priorities, ensuring high-quality, patient-centered, and cost-effective care. - Advance continuous improvement and foster professional development. - Ensure compliance with regulatory and accreditation requirements. We need to ensure we don't duplicate content unnecessarily but it's okay. Requirements: License/Certification/Registration, Education, Experience, plus maybe DHS Background Study Required? and Location? Location is On-site. Could include location as part of Requirements? Might be separate but we can include as bullet. Let's list: - Active RN license required. - Nursing Professional Development (NPD) or Nurse Executive certification preferred. - BLS certification if applicable. - Bachelor's degree in Nursing required. - Master's degree in Nursing, Healthcare Administration, or related field preferred. - 7-10 years progressive nursing leadership experience. - Experience with Magnet designation or nursing excellence programs preferred. - Experience in quality improvement, analytics, and program development. - Demonstrated success leading large-scale, interdisciplinary initiatives. - DHS Background Study Required? Yes. - Location: On-site. We could also include "Location (e.g. remote or on-site): On-site" as bullet. Skills/Knowledge/Abilities bullet list: - Strategic thinking & execution - Change leadership & continuous improvement - Data-driven decision making - Collaboration & influencing - Talent development & coaching - Financial & operational acumen - Integrates evidence-based practice into programs and operations - Supports mission, vision, and professional standards - Promotes continuous learning and professional growth - Ensures adherence to organizational policies and procedures - Maintains compliance with regulatory and Magnet accreditation standards - Manages staff, time, and budget effectively - Promotes efficiency and accountability Benefits bullet list: - Medical, dental, vision, retirement, and other fringe benefits. - Shift differentials or premium pay for positions requiring night, weekend or on-call work. Pay paragraph: "The posted salary represents a market competitive range based on salary survey benchmark data for similar roles in the local or national market. Annual salaries displayed are based on full-time employment (40 standard hrs per week). Annual salaries for part-time positions will be prorated based on the employee’s scheduled weekly hours in relation to the full-time standard. When determining individual pay rates, we carefully consider a wide range of factors including but not limited to market indicators for the specific role, the skills, education, training, credentials and experience of the candidate, internal equity and organizational needs." We should not include the line about "All job offers are contingent upon successful completion..." as we decided to remove. Now produce HTML fragment:About Children’s Minnesota paragraph...
About the role
Position summary paragraph...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...