Registered Nurse - CVICU
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those headings if applicable. However we have content like "About Children’s Minnesota" which is about the organization, not role. Could map to "About the role"? Might be better to use "About the role" heading for role summary. But we also have Department Overview. Could treat as "About the role"? Hmm.
We need to preserve all substantive information, not invent. We should not repeat job title as heading. We need to include sections only when posting has real specific content.
Let's extract sections:
- About Children’s Minnesota (organization description). Could be under "About the role"? Not exactly. Maybe we can create a section "About Children’s Minnesota" as 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. Likely we should use those standard headings where applicable. For organization description, maybe "About the role" is not correct. Could use "About Children’s Minnesota" as a heading but not in list. However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It may imply we should use those headings for sections; but we can also use other headings if needed? Safer to follow examples: use those headings only. So we need to map content to those headings.
We have:
- About the role: could include Position Summary and Department Overview? Actually Position Summary describes role. Department Overview describes unit. Could combine under About the role.
- Responsibilities: Position Summary includes coordinates and provides family-centered nursing care, accountable for professional practice etc. Could list responsibilities.
- Requirements: Education Requirements, licensure, certifications, experience.
- Qualifications: maybe similar to Requirements; but we could treat Requirements as qualifications.
- Skills: maybe not explicitly listed; we could omit if no specific skills.
- Benefits: mention medical, dental, vision, retirement, fringe benefits, shift differentials.
- Pay: salary range statement.
- Schedule: not specified; we should not create Schedule section if not specific.
We must not include filler like "commensurate with experience". The posting says "The posted salary represents a market competitive range based on salary survey benchmark data...". That's specific enough to include Pay section.
We need to preserve all substantive info: include details about Children’s Minnesota, department overview, position summary, education requirements, physical demands (link), salary, benefits, MNA contract note, equal opportunity statement (but EEO boilerplate should be removed per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate). So we should remove the EEO paragraph at the end. Also remove "Please visit childrensMN.org." maybe considered navigation? It's not boilerplate but maybe okay to keep? It's not legal/EEO. Might keep as part of About Children’s Minnesota? It's a link. Could keep as part of description.
We must not include duplicated lines. There's duplicate "Children’s Minnesota is proud to be recognized by Modern Healthcare as one of 2023’s Top Diversity Leaders." appears twice? Actually appears once in first paragraph and later again? Let's check: first paragraph includes that line. Later near end: "Children’s Minnesota is proud to be an equal opportunity employer..." not duplicate. So only one.
We need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we should use those standard headings where applicable. For organization description, maybe "About the role" is not correct. Could use "About Children’s Minnesota" as a heading but not in list. However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It may imply we should use those headings for sections; but we can also use other headings if needed? Safer to follow examples: use those headings only. So we need to map content to those headings.
We have:
- About the role: could include Position Summary and Department Overview? Actually Position Summary describes role. Department Overview describes unit. Could combine under About the role.
- Responsibilities: Position Summary includes coordinates and provides family-centered nursing care, accountable for professional practice etc. Could list responsibilities.
- Requirements: Education Requirements, licensure, certifications, experience.
- Qualifications: maybe similar to Requirements; but we could treat Requirements as qualifications.
- Skills: maybe not explicitly listed; we could omit if no specific skills.
- Benefits: mention medical, dental, vision, retirement, fringe benefits, shift differentials.
- Pay: salary range statement.
- Schedule: not specified; we should not create Schedule section if not specific.
We must not include filler like "commensurate with experience". The posting says "The posted salary represents a market competitive range based on salary survey benchmark data...". That's specific enough to include Pay section.
We need to preserve all substantive info: include details about Children’s Minnesota, department overview, position summary, education requirements, physical demands (link), salary, benefits, MNA contract note, equal opportunity statement (but EEO boilerplate should be removed per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate). So we should remove the EEO paragraph at the end. Also remove "Please visit childrensMN.org." maybe considered navigation? It's not boilerplate but maybe okay to keep? It's not legal/EEO. Might keep as part of About Children’s Minnesota? It's a link. Could keep as part of description.
We must not include duplicated lines. There's duplicate "Children’s Minnesota is proud to be recognized by Modern Healthcare as one of 2023’s Top Diversity Leaders." appears twice? Actually appears once in first paragraph and later again? Let's check: first paragraph includes that line. Later near end: "Children’s Minnesota is proud to be an equal opportunity employer..." not duplicate. So only one.
We need to output only HTML fragment, no /, no markdown.
We'll structure:
About the role
About the role
... combine About Children’s Minnesota and Department Overview and Position Summary?
But we might want separate sections: About the role (role summary), Responsibilities, Requirements, Qualifications, Benefits, Pay. Let's decide: About the role: Position Summary (coordinates and provides family-centered nursing care...). Responsibilities: maybe bullet list derived from Position Summary? Could list: Coordinates and provides family-centered nursing care to infants, children and adolescents; Utilizes the nursing process; Accountable for professional practice including independent nursing functions and delegated medical functions performed in collaboration with other health team members. Requirements: Education Requirements bullet list: Graduate of an accredited school of nursing; Current Minnesota RN licensure; Current BLS certification; One (1) year pediatric nursing experience in a hospital setting or one (1) year of adult critical care and/or cardiac step-down experience; Additional certification(s) may be required based on unit; Department specific required qualifications need to be obtained within 6 months of employment; Current Pediatric Advanced Life Support (PALS) certification required or obtained during orientation. Qualifications: maybe we can include Department Overview as qualifications? Or we could treat Department Overview as part of About the role? Hmm. Better: Use Qualifications for Department Overview and specialized skills (ECMO, CRRT, VAD, hemodynamic monitoring, etc.). But those are more about unit. Could be under Qualifications. Skills: maybe list technical skills: hemodynamic monitoring, critical medication management, maintenance of systemic perfusion, management of organ failure, ECMO, CRRT, VAD, etc. Benefits: medical, dental, vision, retirement, fringe benefits, shift differentials for night/weekend/on-call. Pay: salary range statement. We must not create sections with filler. Ensure each section has substantive content. Let's craft. We'll need to use- for any list of duties/requirements/benefits.
We'll need to use
for prose. We'll need to avoid repeating job title. We'll need to include Physical Demands link? It's a link: "Please click here to view the Physical Demands". That's substantive. Could be under Requirements? Or maybe a separate section? Not in headings list. Could be under Requirements as a note. Could be a
with link. We'll need to include MNA contract position note: "THIS IS AN MNA CONTRACT POSITION." Could be under Requirements or a note. We'll need to include equal opportunity statement? Remove. We'll need to include "Children’s Minnesota is proud to be recognized by Modern Healthcare as one of 2023’s Top Diversity Leaders." That's substantive; could be under About the role? Maybe under About Children’s Minnesota. We'll need to include the description of Children’s Minnesota at start. Could be under About the role? Or maybe a separate section "About Children’s Minnesota". But not in headings list. However we could treat as part of About the role? Might be odd. But we could create a heading "About Children’s Minnesota" as
even though not in examples; instruction 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 exclusive. So we can use other headings as needed. Safer to use those examples but we can also add others if needed. I'd rather include a section "About Children’s Minnesota" to preserve that info. Thus final HTML:
About Children’s Minnesota
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.
About the role
Coordinates and provides family-centered nursing care to infants, children and adolescents, utilizing the nursing process. Accountable for professional practice including independent nursing functions and delegated medical functions performed in collaboration with other health team members. THIS IS AN MNA CONTRACT POSITION.
Responsibilities
- Coordinates and provides family-centered nursing care to infants, children and adolescents
- Utilizes the nursing process
- Accountable for professional practice including independent nursing functions and delegated medical functions performed in collaboration with other health team members
Requirements
- Graduate of an accredited school of nursing
- Current Minnesota RN licensure
- Current BLS certification
- One (1) year pediatric nursing experience in a hospital setting or one (1) year of adult critical care and/or cardiac step-down experience
- Additional certification(s) may be required based on the unit
- Department specific required qualifications need to be obtained within 6 months of employment
- Current Pediatric Advanced Life Support (PALS) certification required or obtained during orientation
- Physical demands: click here to view the Physical Demands
Qualifications
Works in a 25‑bed pediatric cardiovascular intensive care unit (CVICU) that cares for patients with complex conditions, including heart failure, post‑repair of congenital heart defects, heart catheterization, and pre‑ and post‑transplant. The unit routinely utilizes extracorporeal membrane oxygenation (ECMO), continuous renal replacement therapy (CRRT), ventricular assist devices (VAD), hemodynamic monitoring, critical medication management, maintenance of systemic perfusion, and management of organ failure. The team collaborates with over 200 interdisciplinary professionals and emphasizes teamwork, open communication, safety, respect, learning, and professional growth.
Skills
- Hemodynamic monitoring
- Critical medication management
- Maintenance of systemic perfusion
- Management of organ failure
- Extracorporeal membrane oxygenation (ECMO)
- Continuous renal replacement therapy (CRRT)
- Ventricular assist devices (VAD)
Benefits
- Medical, dental, vision, and retirement plans
- Other fringe benefits
- Shift differentials or premium pay for night, weekend, or on‑call work
Pay
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. Individual pay rates consider market indicators, skills, education, training, credentials, experience, internal equity, and organizational needs.
We must not include Schedule section as not specified. Check for any boilerplate: removed EEO, removed navigation? We kept Facebook/Twitter/Instagram and visit childrensMN.org - that's okay. Check for duplicate lines: we didn't duplicate