Mental Health Specialist
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content accordingly. 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.
Thus we need to decide which sections to include based on content.
We have:
- About Children’s Minnesota (company overview) – could be "About the role"? Actually "About the role" is generic heading for role description. But we have "About Children’s Minnesota" which is about the organization. Could map to "About the role"? Not exactly. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It suggests we should use those headings if appropriate. But we can also use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies those are examples; we can use those headings where appropriate. Probably we should map content to these standard headings.
We have:
- Position Summary: describes responsibilities. Could go under "Responsibilities".
- License/Certification/Registration, Education, Experience, Knowledge/Skills/Abilities: these are qualifications/requirements. Could go under "Requirements" or "Qualifications". The instruction includes both Requirements and Qualifications as possible headings. We need to decide.
- Physical Demands: maybe under "Requirements" or separate? Could be part of Requirements.
- Salary and benefits: there is some info about salary range, benefits eligibility, shift differentials. So we could have "Pay" and "Benefits" sections.
- Schedule: not mentioned explicitly; no schedule info. So we should not create a Schedule section.
- About the role: maybe we could include a brief overview of the role (Position Summary) under About the role? But we already have Position Summary; maybe we treat that as About the role.
Better approach: Use headings:
- About the role (contains Position Summary and maybe Department Overview? Actually Department Overview describes the department; could be part of About the role or separate. But we can include Department Overview under About the role as context.
- Responsibilities: maybe we can extract duties from Position Summary: providing direct patient care, assisting with data collection, assisting with establishing therapeutic goals, participating in facilitation of therapeutic patient groups, monitoring department milieu and patient spaces for hazards, assisting with de-escalation, implementing behavioral modification, floating to provide care, etc. Could list as .
- Requirements: includes License/Certification/Registration (BLS), Education (Bachelor's), Experience (one year pediatric healthcare preferred, experience with children with behavioral dysregulation etc preferred), Knowledge/Skills/Abilities (education/experience providing gender, culture, age appropriate care; strong interpersonal skills; excellent verbal/written communication; professional attitude; develop rapport). Also Physical Demands (link). Could be part of Requirements.
- Qualifications: maybe we could combine Requirements and Qualifications but we need to avoid thin sections. Perhaps we can have one "Requirements" section that includes all.
- Skills: maybe separate Skills from Knowledge/Skills/Abilities? But we can include skills under Requirements.
- Benefits: we have info about medical, dental, vision, retirement, fringe benefits, shift differentials/premium pay for night/weekend/on-call. So we can have Benefits section.
- Pay: we have info about posted salary representing market competitive range based on survey benchmark data, annual salaries based on full-time, prorated for part-time, factors considered. That's specific enough to create a Pay section.
We must not create sections with filler like "commensurate with experience". The Pay section we have actual content: "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." That's substantive.
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." That's substantive.
Schedule: no explicit schedule info, so omit.
Now we need to remove boilerplate: EEO statement, etc. Also remove "Please click here to view the Physical Demands" maybe we keep as a link? The Physical Demands is a link; we should keep the reference but not the boilerplate. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep the Physical Demands reference as a link? It says "Please click here to view the Physical Demands". That's a directive; we could keep as a with a link? But we don't have URL. We could keep the text as is, but it's not boilerplate; it's a reference. We'll keep it.
Also remove duplicated lines: there are duplicate statements about Children’s Minnesota being proud to be recognized etc. We'll keep only one instance.
Now structure:
About the role
... combine About Children’s Minnesota and Department Overview? Might be too much but okay.
Better: About the role: includes Position Summary and maybe Department Overview? Actually About the role could be a brief description of the role; we have Position Summary. We'll put Position Summary there.
Then
Responsibilities
with list of duties extracted from Position Summary.
Then Requirements
with for license/cert, education, experience, knowledge/skills/abilities, physical demands.
Then Benefits
with list.
Then Pay
with describing salary determination.
We must not repeat job title as heading.
Now ensure we don't include any filler like "commensurate with experience". Not present.
Now produce HTML.
Let's craft content.
About the role: Use Position Summary paragraph: "The Mental Health Specialist is responsible for providing direct patient care to children and adolescents with behavioral challenges or a mental health diagnosis based on the individual treatment plan. Under the direction of a Registered Nurse, they assist with collecting data regarding a patient's physical, psychological, or safety status on an ongoing basis. The Mental Health Specialist may assist patients in establishing daily therapeutic goals or participate in facilitation of therapeutic patient groups. They are responsible for continually monitoring the department milieu and patient spaces to assess for any potential hazards or personal patient safety concerns. Utilizing a therapeutic approach, the Mental Health Specialist may assist with de-escalation or implementing behavioral modification and management when appropriate. This role may float to provide care and support for all mental health patients throughout the mental health care continuum including outside the inpatient mental health unit within the Children's MN system."
We could also add a brief about department: "The pediatric emergency department at Children’s Minnesota Minneapolis campus is the only freestanding pediatric Level I trauma center in the area..." but that's more about department. Might be okay to include under About the role as context. But we risk making section too long but still substantive.
Better to keep About the role as Position Summary only, and maybe add a separate section for Department Overview? But we don't have a heading for that; we could incorporate into About the role as a paragraph before Position Summary.
Let's do:
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. The pediatric emergency department at Children’s Minnesota Minneapolis campus is the only freestanding pediatric Level I trauma center in the area. Our interdisciplinary team of dedicated professionals cares for a wide-range of pediatric trauma and injuries, such as chest, bone, spinal cord, head and neck and abdominal injuries. We care for over 48,000 patients annually and treat almost 40 percent of all pediatric trauma in the Twin Cities. Our 28-bed Level I trauma center serves our neighbors in Minneapolis, as well as outlying facilities that depend on our critical care expertise. We offer a variety of services to our community partners, including critical care transport and telehealth. Although our specialty is pediatric emergency medicine, we are a community-based hospital that serves as a safety-net for families without a primary care provider. Our family-centered focus strives to consider social, economic and cultural diversity — living our core value of putting “Kids First.” We provide care from birth through adulthood, considering age and developmental level when interacting with our patients. We incorporate the Comfort Promise into our care — ensuring that procedural pain is minimized whenever possible. We value teamwork, open communication, safety, and respect. We embrace an environment that encourages learning, and professional growth. Our team of emergency department professionals is committed to providing excellent care to our patients and families.
The Mental Health Specialist is responsible for providing direct patient care to children and adolescents with behavioral challenges or a mental health diagnosis based on the individual treatment plan. Under the direction of a Registered Nurse, they assist with collecting data regarding a patient's physical, psychological, or safety status on an ongoing basis. The Mental Health Specialist may assist patients in establishing daily therapeutic goals or participate in facilitation of therapeutic patient groups. They are responsible for continually monitoring the department milieu and patient spaces to assess for any potential hazards or personal patient safety concerns. Utilizing a therapeutic approach, the Mental Health Specialist may assist with de-escalation or implementing behavioral modification and management when appropriate. This role may float to provide care and support for all mental health patients throughout the mental health care continuum including outside the inpatient mental health unit within the Children's MN system.
That seems okay.
Now Responsibilities: we can list bullet points from the Position Summary (maybe same as above but as list). But we already have prose; we could still list responsibilities as . However we must not duplicate content? The instruction says preserve ALL substantive information; we can rephrase but not lose detail. It's okay to have both prose and list? Might be redundant but
- 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. Thus we need to decide which sections to include based on content. We have: - About Children’s Minnesota (company overview) – could be "About the role"? Actually "About the role" is generic heading for role description. But we have "About Children’s Minnesota" which is about the organization. Could map to "About the role"? Not exactly. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It suggests we should use those headings if appropriate. But we can also use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies those are examples; we can use those headings where appropriate. Probably we should map content to these standard headings. We have: - Position Summary: describes responsibilities. Could go under "Responsibilities". - License/Certification/Registration, Education, Experience, Knowledge/Skills/Abilities: these are qualifications/requirements. Could go under "Requirements" or "Qualifications". The instruction includes both Requirements and Qualifications as possible headings. We need to decide. - Physical Demands: maybe under "Requirements" or separate? Could be part of Requirements. - Salary and benefits: there is some info about salary range, benefits eligibility, shift differentials. So we could have "Pay" and "Benefits" sections. - Schedule: not mentioned explicitly; no schedule info. So we should not create a Schedule section. - About the role: maybe we could include a brief overview of the role (Position Summary) under About the role? But we already have Position Summary; maybe we treat that as About the role. Better approach: Use headings: - About the role (contains Position Summary and maybe Department Overview? Actually Department Overview describes the department; could be part of About the role or separate. But we can include Department Overview under About the role as context. - Responsibilities: maybe we can extract duties from Position Summary: providing direct patient care, assisting with data collection, assisting with establishing therapeutic goals, participating in facilitation of therapeutic patient groups, monitoring department milieu and patient spaces for hazards, assisting with de-escalation, implementing behavioral modification, floating to provide care, etc. Could list as
- .
- Requirements: includes License/Certification/Registration (BLS), Education (Bachelor's), Experience (one year pediatric healthcare preferred, experience with children with behavioral dysregulation etc preferred), Knowledge/Skills/Abilities (education/experience providing gender, culture, age appropriate care; strong interpersonal skills; excellent verbal/written communication; professional attitude; develop rapport). Also Physical Demands (link). Could be part of Requirements.
- Qualifications: maybe we could combine Requirements and Qualifications but we need to avoid thin sections. Perhaps we can have one "Requirements" section that includes all.
- Skills: maybe separate Skills from Knowledge/Skills/Abilities? But we can include skills under Requirements.
- Benefits: we have info about medical, dental, vision, retirement, fringe benefits, shift differentials/premium pay for night/weekend/on-call. So we can have Benefits section.
- Pay: we have info about posted salary representing market competitive range based on survey benchmark data, annual salaries based on full-time, prorated for part-time, factors considered. That's specific enough to create a Pay section.
We must not create sections with filler like "commensurate with experience". The Pay section we have actual content: "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." That's substantive.
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." That's substantive.
Schedule: no explicit schedule info, so omit.
Now we need to remove boilerplate: EEO statement, etc. Also remove "Please click here to view the Physical Demands" maybe we keep as a link? The Physical Demands is a link; we should keep the reference but not the boilerplate. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep the Physical Demands reference as a link? It says "Please click here to view the Physical Demands". That's a directive; we could keep as a
with a link? But we don't have URL. We could keep the text as is, but it's not boilerplate; it's a reference. We'll keep it. Also remove duplicated lines: there are duplicate statements about Children’s Minnesota being proud to be recognized etc. We'll keep only one instance. Now structure:
About the role
... combine About Children’s Minnesota and Department Overview? Might be too much but okay. Better: About the role: includes Position Summary and maybe Department Overview? Actually About the role could be a brief description of the role; we have Position Summary. We'll put Position Summary there. Then
Responsibilities
with- list of duties extracted from Position Summary.
Then
Requirements
with- for license/cert, education, experience, knowledge/skills/abilities, physical demands.
Then
Benefits
with- list.
Then
Pay
withdescribing salary determination. We must not repeat job title as heading. Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML. Let's craft content. About the role: Use Position Summary paragraph: "The Mental Health Specialist is responsible for providing direct patient care to children and adolescents with behavioral challenges or a mental health diagnosis based on the individual treatment plan. Under the direction of a Registered Nurse, they assist with collecting data regarding a patient's physical, psychological, or safety status on an ongoing basis. The Mental Health Specialist may assist patients in establishing daily therapeutic goals or participate in facilitation of therapeutic patient groups. They are responsible for continually monitoring the department milieu and patient spaces to assess for any potential hazards or personal patient safety concerns. Utilizing a therapeutic approach, the Mental Health Specialist may assist with de-escalation or implementing behavioral modification and management when appropriate. This role may float to provide care and support for all mental health patients throughout the mental health care continuum including outside the inpatient mental health unit within the Children's MN system." We could also add a brief about department: "The pediatric emergency department at Children’s Minnesota Minneapolis campus is the only freestanding pediatric Level I trauma center in the area..." but that's more about department. Might be okay to include under About the role as context. But we risk making section too long but still substantive. Better to keep About the role as Position Summary only, and maybe add a separate section for Department Overview? But we don't have a heading for that; we could incorporate into About the role as a paragraph before Position Summary. Let's do:
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. The pediatric emergency department at Children’s Minnesota Minneapolis campus is the only freestanding pediatric Level I trauma center in the area. Our interdisciplinary team of dedicated professionals cares for a wide-range of pediatric trauma and injuries, such as chest, bone, spinal cord, head and neck and abdominal injuries. We care for over 48,000 patients annually and treat almost 40 percent of all pediatric trauma in the Twin Cities. Our 28-bed Level I trauma center serves our neighbors in Minneapolis, as well as outlying facilities that depend on our critical care expertise. We offer a variety of services to our community partners, including critical care transport and telehealth. Although our specialty is pediatric emergency medicine, we are a community-based hospital that serves as a safety-net for families without a primary care provider. Our family-centered focus strives to consider social, economic and cultural diversity — living our core value of putting “Kids First.” We provide care from birth through adulthood, considering age and developmental level when interacting with our patients. We incorporate the Comfort Promise into our care — ensuring that procedural pain is minimized whenever possible. We value teamwork, open communication, safety, and respect. We embrace an environment that encourages learning, and professional growth. Our team of emergency department professionals is committed to providing excellent care to our patients and families.
The Mental Health Specialist is responsible for providing direct patient care to children and adolescents with behavioral challenges or a mental health diagnosis based on the individual treatment plan. Under the direction of a Registered Nurse, they assist with collecting data regarding a patient's physical, psychological, or safety status on an ongoing basis. The Mental Health Specialist may assist patients in establishing daily therapeutic goals or participate in facilitation of therapeutic patient groups. They are responsible for continually monitoring the department milieu and patient spaces to assess for any potential hazards or personal patient safety concerns. Utilizing a therapeutic approach, the Mental Health Specialist may assist with de-escalation or implementing behavioral modification and management when appropriate. This role may float to provide care and support for all mental health patients throughout the mental health care continuum including outside the inpatient mental health unit within the Children's MN system.
That seems okay. Now Responsibilities: we can list bullet points from the Position Summary (maybe same as above but as list). But we already have prose; we could still list responsibilities as- . However we must not duplicate content? The instruction says preserve ALL substantive information; we can rephrase but not lose detail. It's okay to have both prose and list? Might be redundant but