Unit Support Technician

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Children’s Minnesota" (company overview) and "Department Overview", "Position Summary", "License/Certification/Education", "Experience", "Knowledge/Skills/Abilities", plus salary/benefits info. We must use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should only include sections when posting has real specific content. The posting does not have explicit "Responsibilities" heading but Position Summary includes responsibilities. Could map that to a section "Responsibilities". Similarly "Requirements" could cover License/Certification/Education, Experience, Knowledge/Skills/Abilities. "Qualifications" maybe similar. But we need to avoid duplication and filler. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose appropriate headings based on content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove navigation, cookie, legal, duplicated lines. Also remove application instructions (none present). Also remove social media links? Those are part of About Children's Minnesota but maybe considered boilerplate? It's not navigation but it's contact info. Might keep as part of About the organization? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Social media links maybe not required to remove but could be considered navigation? Probably safe to keep as part of About Children's Minnesota description? Might be considered not essential but not prohibited. However we can keep it as part of About the organization paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting except removed boilerplate. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... maybe combine About Children's Minnesota and Department Overview? Actually "About the role" could be Position Summary. But we also have "About Children's Minnesota" which is company overview. Could be separate section "About Children's Minnesota". But the allowed headings list includes "About the role". Not "About Children's Minnesota". However we could still use that 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 stick to those headings. So we need to map content to those headings. Thus we could have: - About the role: includes Position Summary (what the Unit Support Technician does) and maybe Department Overview? Actually Department Overview describes the unit; could be part of About the role context. - Responsibilities: could be derived from Position Summary bullet points. - Requirements: could include License/Certification/Education, Experience, Knowledge/Skills/Abilities. - Qualifications: maybe similar to Requirements but we could avoid duplication. Perhaps we combine Requirements and Qualifications into one section? But we need to avoid filler. Better to have one section for Requirements that includes all needed qualifications. - Skills: could list specific skills like computer skills, communication, etc. - Benefits: includes medical, dental, vision, retirement, fringe benefits, shift differentials. - Pay: includes salary range statement. - Schedule: maybe not present; we should not create Schedule section unless posting actually states it. The posting does not mention schedule specifics, only full-time/part-time note. It mentions full-time employment (40 standard hrs per week) and prorated for part-time. That's schedule info. Could we consider that as schedule? It mentions standard hours. Might be enough to create a Schedule section. But the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary info and benefits info, and mentions full-time/part-time. So we can include Pay, Benefits, Schedule. Thus we need sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Good. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, requirements list, skills list, benefits list. We need to use

  for prose. We must preserve all substantive information. Let's extract. Company overview: About Children’s Minnesota paragraph(s). We'll include that as prose under About the role maybe. Department Overview: description of CVICU. Could be part of About the role. Position Summary: description of Unit Support Technician duties. Let's list duties/responsibilities: - Provides exemplary customer service to families, staff, providers and visitors, both in-person and by phone. - Provides monitoring of patients requiring continuous telemetry throughout Children's. - Alerts clinicians based on identified acute changes. - Creates telemetry reports daily or as otherwise needed. - Answers questions, warmly, promptly, and correctly, and problem solves as needed. - Provides first response to phone calls that come into the units. - Arranges for deliveries to patients rooms. - Directs visitors to their destinations. - Maintains a safe, welcoming environment at all times, modeling service excellence to the organization. - Serves as key liaison to other departments and provides other disciplines with the tools for their jobs. - Supports patient care on the unit(s) and provides overall administrative support for the unit. - Acts as the unit(s) technology resource. That's many. Requirements/License/Certification/Education: - High School Diploma or equivalent required - Basic Life Support (BLS) Certification required - Health Unit Coordinator certificate preferred - Previous Health Unit Coordinator experience preferred - Medical terminology preferred - Telemetry/EKG monitoring experience preferred Knowledge/Skills/Abilities: - Situational awareness - Outstanding professional and positive customer service skills essential - Positive attitude - Exceptional problem solving skills - Strong computer skills such as Microsoft word, excel or hospital technology systems - Ability to coach others with hospital technology systems - Demonstrates excellent interpersonal, written and verbal communication skills with a clear understanding of English language (reading, writing and speaking) - Self-directed, organized, and problem solver - Ability to multitask, direct and support information processes on patient care units, work independently and within a team - Adaptable to change in various work place settings Benefits: - In addition to your salary, this position may be eligible for medical, dental, vision, retirement, and other fringe benefits. - Positions that require night, weekend or on-call work may be eligible for shift differentials or premium pay. 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. - 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. Schedule: - Full-time employment (40 standard hrs per week). Part-time positions prorated based on scheduled weekly hours. We also have contingency statements: All job offers contingent upon occupational health assessment, drug screen, background investigation, I-9 compliance. That's substantive; should we include? It's not in the allowed headings but could be placed under Requirements or a separate section like "Contingencies". But we must not invent sections not in list? 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 says "Use

  for section headings (e.g. ...)". Likely we should stick to those. However we need to preserve all substantive information; we could include that info under Requirements or maybe under a

  within Requirements. Since it's about hiring contingencies, could be part of Requirements. We'll add a bullet list under Requirements for "Contingent upon successful completion of...". Also EEO statement we must remove. So we will omit the equal opportunity employer paragraph. Also remove duplicated lines: there is 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 near start and later? Let's check: At start: "Children’s Minnesota is proud to be recognized by Modern Healthcare as one of 2023’s Top Diversity Leaders." Then later near end: "Children’s Minnesota is proud to be an equal opportunity employer..." That's different. No duplicate of that line. There's duplicate maybe "Children’s Minnesota is proud to be recognized..." appears only once. There's also "Children’s Minnesota is proud to be an equal opportunity employer..." which we remove. Also there is "Please visit childrensMN.org." and social media links; we may keep as part of About the role prose. Now craft HTML. We'll start with

  About the role

  then a

  containing About Children’s Minnesota, Department Overview, Position Summary maybe as prose. But we also need a Responsibilities section with list. Better: About the role: brief overview of the role and unit. Then Responsibilities: list of duties. Then Requirements: list of education/certification/experience/knowledge etc plus contingencies. Then Skills: maybe separate list of skills like computer skills, communication, etc. But many skills overlap with requirements. Could combine. Given instruction to prefer few substantive sections over many thin ones, we could merge Requirements and Skills into one Requirements section that includes all. But they asked to use headings like Skills; we could still include Skills section if we have specific skill list. Let's decide sections: - About the role (overview) - Responsibilities (duties list) - Requirements (education, certification, experience, knowledge/abilities, contingencies) - Benefits - Pay - Schedule We can omit Skills as separate because its content overlaps with Requirements; but we could still include Skills if we want. However to avoid thin sections, maybe combine. Thus we will have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Now ensure we use

  • for any list of duties/requirements/benefits. Thus:

    About the role

    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. Department Overview Our cardiovascular intensive care unit (CVICU) is a 25-bed pediatric critical care unit for patients with complex conditions and their families. As a member of the largest pediatric heart program in the state, our team works closely with more than 200 interdisciplinary professionals dedicated to the care of children with life-changing cardiovascular diagnoses. In this unit, we care for patients along their continuum of acute recovery to provide for their changing physical and emotional needs as we prepare them to return home. We specialize in caring for children experiencing