Cardiac Sonographer (PRN)
for each section. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc.
We need to parse the posting:
- Intro: "Find your calling at Mercy! The Advanced Cardiac Sonographer proficiently performs a variety of diagnostic and interventional procedures assisting in diagnosing and monitoring a wide range of medical conditions. The role requires technical expertise in operating ultrasound equipment, patient care skills, and the ability to provide accurate and high-quality diagnostic images. This role also requires a strong commitment to patient care and collaborative communication with patients and healthcare professionals to provide optimal care."
That's about the role.
- Position Details Minimum Qualifications: Education: Graduate of a school of Sonography and completed required clinical hours OR received on the job training by a Preceptor who is registered in Cardiac ultrasound. Experience: One (1) year of relevant experience. Licensure: State licensure may be required depending on the specific state of practice. Certification: ARDMS (RDCS) or CCI(RCS); Basic Life Support (BLS)
- Preferred Qualifications Preferred Skills, Knowledge, and Abilities: Knowledge in producing diagnostic images proficiently with the ability to recognize technical abnormalities. Strong attention to detail and ability to follow complex instructions. Excellent communication and interpersonal skills. Ability to work effectively in a fast-paced, collaborative environment. Knowledge of protocols and ability to make adjustments as needed. Knowledge of safe & proper machine operation. Knowledge of machine emergency procedures and radiation safety procedures. Flexibility
- Physical Requirements: Position requires the ability to push, pull, and/or lift 50 lbs. on a regular basis. Position requires prolonged standing and walking during each shift. Position requires the ability to grip, reach, bend, kneel, twist, and squat to perform duties.
- Why Mercy?: From day one, Mercy offers outstanding benefits - including medical, dental, and vision coverage, paid time off, tuition support, and matched retirement plans for team members working 32+ hours per pay period. Join a caring, collaborative team where your voice matters. At Mercy, you'll help shape the future of healthcare through innovation, technology, and compassion. As we grow, you'll grow with us.
We need to output sections: About the role (prose), Responsibilities (maybe not explicit? The intro includes performing procedures, but we could treat that as responsibilities. However we have no explicit responsibilities list. Could we create a Responsibilities section with bullet list of duties? The posting says "proficiently performs a variety of diagnostic and interventional procedures assisting in diagnosing and monitoring a wide range of medical conditions." That's a duty. Also "operating ultrasound equipment", "patient care skills", "provide accurate and high-quality diagnostic images", "strong commitment to patient care and collaborative communication". Could list those as bullet points. But we must not invent or summarize away detail; we can list them as bullet points derived from the text. That seems okay.
Requirements: Minimum Qualifications (education, experience, licensure, certification). Could be a list.
Qualifications: Preferred Qualifications (skills, knowledge, abilities). Could be list.
Skills: maybe combine with Preferred Qualifications? But we already have Skills section; we could put the preferred skills there. However we already used Qualifications for preferred qualifications; maybe we treat Requirements as minimum qualifications, Qualifications as preferred qualifications, Skills as maybe the same? But we need to avoid thin sections. Better to have: About the role (prose), Responsibilities (bullet list of duties), Requirements (minimum qualifications bullet list), Qualifications (preferred qualifications bullet list), Benefits (benefits bullet list). Skills maybe not needed if we already have Qualifications. But the instruction says use headings for sections like Skills, Benefits, Pay, Schedule. We should include a section only if posting has real specific content for it. We have content for Skills (the preferred skills). So we could have Skills section. Qualifications could be for minimum qualifications? Actually they said "Qualifications" heading could be used for qualifications (maybe both). But we have both minimum and preferred. Could combine? But we need to avoid thin sections. Perhaps we do: About the role (prose), Responsibilities (bullet list), Requirements (minimum qualifications bullet list), Skills (preferred skills bullet list), Benefits (benefits bullet list). No Qualifications heading.
Check if we need to include "Qualifications" heading: The posting has "Minimum Qualifications" and "Preferred Qualifications". Could treat "Requirements" as minimum qualifications, "Qualifications" as preferred qualifications. But then we also have Skills heading which might duplicate. Better to follow typical structure: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. But we have limited content; we can assign:
- About the role: intro paragraph.
- Responsibilities: bullet list of duties (performing procedures, operating equipment, patient care, providing images, commitment to patient care, collaborative communication).
- Requirements: bullet list of minimum qualifications (education, experience, licensure, certification).
- Qualifications: bullet list of preferred qualifications (maybe the same as skills? Actually preferred qualifications include knowledge, skills, abilities). Could be Qualifications.
- Skills: maybe we could list specific skills like "knowledge in producing diagnostic images", "strong attention to detail", etc. But that overlaps with Qualifications. To avoid duplication, we could treat Qualifications as the preferred qualifications (knowledge, skills, abilities) and Skills as maybe the physical requirements? But physical requirements are not skills. Hmm.
Alternatively, we could combine: Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (maybe physical requirements? but those are not skills). Better to follow the instruction: Use headings for sections only when posting has real specific content. So we need to decide which sections we have content for:
- About the role: yes.
- Responsibilities: we can derive duties from the description.
- Requirements: yes (minimum qualifications).
- Qualifications: yes (preferred qualifications).
- Skills: maybe we could list specific skills from preferred qualifications (knowledge, attention to detail, communication, etc.) but that's essentially the same as qualifications. However we could still have a Skills section listing those skills. But then Qualifications would be redundant. Perhaps we treat Qualifications as the preferred qualifications (knowledge, skills, abilities) and Skills as maybe the technical skills like operating ultrasound equipment, recognizing abnormalities, etc. But again overlapping.
Given the instruction to prefer a few substantive sections over many thin ones, we should avoid splitting too finely. So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits. That's five sections. Skills could be omitted because its content is covered in Qualifications. Pay and Schedule omitted.
Thus output:
About the role
... (the intro paragraph)
Responsibilities
- Perform a variety of diagnostic and interventional ultrasound procedures to assist in diagnosing and monitoring medical conditions.
- Operate ultrasound equipment with technical expertise.
- Provide accurate and high-quality diagnostic images.
- Demonstrate strong commitment to patient care.
- Communicate and collaborate effectively with patients and healthcare professionals.
Requirements
- Education: Graduate of a school of Sonography and completed required clinical hours OR received on‑the‑job training by a Preceptor who is registered in Cardiac ultrasound.
- Experience: One (1) year of relevant experience.
- Licensure: State licensure may be required depending on the specific state of practice.
- Certification: ARDMS (RDCS) or CCI(RCS); Basic Life Support (BLS).
Qualifications
- Knowledge in producing diagnostic images proficiently with the ability to recognize technical abnormalities.
- Strong attention to detail and ability to follow complex instructions.
- Excellent communication and interpersonal skills.
- Ability to work effectively in a fast‑paced, collaborative environment.
- Knowledge of protocols and ability to make adjustments as needed.
- Knowledge of safe & proper machine operation.
- Knowledge of machine emergency procedures and radiation safety procedures.
- Flexibility.
Benefits
- Medical, dental, and vision coverage.
- Paid time off.
- Tuition support.
- Matched retirement plans for team members working 32+ hours per pay period.
We need to ensure we didn't include any boilerplate. The "Why Mercy?" paragraph includes also "Join a caring, collaborative team where your voice matters. At Mercy, you'll help shape the future of healthcare through innovation, technology, and compassion. As we grow, you'll grow with us." That's more promotional; we could include that in Benefits section as prose? But we already made Benefits a list of specific benefits. The extra sentences are more about culture; maybe we could include them in About the role or a separate section like "Why Mercy?" but we don't have a heading for that. Could incorporate into Benefits as prose after list? But we should not invent sections. Could add a after the list describing the culture. That's still part of Benefits section? Might be okay to keep as prose within Benefits. However the instruction: Use
for prose. So we could have Benefits section with a
for the tangible benefits and then a for the cultural statements. That preserves all substantive info.
Thus Benefits section:
Benefits
- Medical, dental, and vision coverage.
- Paid time off.
- Tuition support.
- Matched retirement plans for team members working 32+ hours per pay period.
Join a caring, collaborative team where your voice matters. At Mercy, you'll help shape the future of healthcare through innovation, technology, and compassion. As we grow, you'll grow with us.
Now check for any leftover info: The "Physical Requirements" we haven't included. That's substantive; we need to include it somewhere. Could be part of Requirements or a separate section like "Physical Requirements". But we don't have a heading for Physical Requirements; we could include under Requirements as additional bullet points. Or we could create a separate section "Physical Requirements". The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list Physical Requirements as a predefined heading, but we could still use a heading if we want, but the 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. However they say "include a section ONLY when the posting has real, specific content for it". So we could add a Physical Requirements section if we want. But to keep sections few, we could fold physical requirements into Requirements section. That seems acceptable.
Thus Requirements bullet list will include physical requirements as additional bullets.
Let's compile Requirements:
- Education: Graduate of a school of Sonography and completed required clinical hours OR received on‑the‑job training by a Preceptor who is registered in Cardiac ultrasound.
- Experience: One (1) year of relevant experience.
- Licensure: State licensure may be required depending on the specific state of practice.
- Certification: ARDMS (RDCS) or CCI(RCS); Basic Life Support (BLS).
- Physical Requirements: Ability
for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting: - Intro: "Find your calling at Mercy! The Advanced Cardiac Sonographer proficiently performs a variety of diagnostic and interventional procedures assisting in diagnosing and monitoring a wide range of medical conditions. The role requires technical expertise in operating ultrasound equipment, patient care skills, and the ability to provide accurate and high-quality diagnostic images. This role also requires a strong commitment to patient care and collaborative communication with patients and healthcare professionals to provide optimal care." That's about the role. - Position Details Minimum Qualifications: Education: Graduate of a school of Sonography and completed required clinical hours OR received on the job training by a Preceptor who is registered in Cardiac ultrasound. Experience: One (1) year of relevant experience. Licensure: State licensure may be required depending on the specific state of practice. Certification: ARDMS (RDCS) or CCI(RCS); Basic Life Support (BLS) - Preferred Qualifications Preferred Skills, Knowledge, and Abilities: Knowledge in producing diagnostic images proficiently with the ability to recognize technical abnormalities. Strong attention to detail and ability to follow complex instructions. Excellent communication and interpersonal skills. Ability to work effectively in a fast-paced, collaborative environment. Knowledge of protocols and ability to make adjustments as needed. Knowledge of safe & proper machine operation. Knowledge of machine emergency procedures and radiation safety procedures. Flexibility - Physical Requirements: Position requires the ability to push, pull, and/or lift 50 lbs. on a regular basis. Position requires prolonged standing and walking during each shift. Position requires the ability to grip, reach, bend, kneel, twist, and squat to perform duties. - Why Mercy?: From day one, Mercy offers outstanding benefits - including medical, dental, and vision coverage, paid time off, tuition support, and matched retirement plans for team members working 32+ hours per pay period. Join a caring, collaborative team where your voice matters. At Mercy, you'll help shape the future of healthcare through innovation, technology, and compassion. As we grow, you'll grow with us. We need to output sections: About the role (prose), Responsibilities (maybe not explicit? The intro includes performing procedures, but we could treat that as responsibilities. However we have no explicit responsibilities list. Could we create a Responsibilities section with bullet list of duties? The posting says "proficiently performs a variety of diagnostic and interventional procedures assisting in diagnosing and monitoring a wide range of medical conditions." That's a duty. Also "operating ultrasound equipment", "patient care skills", "provide accurate and high-quality diagnostic images", "strong commitment to patient care and collaborative communication". Could list those as bullet points. But we must not invent or summarize away detail; we can list them as bullet points derived from the text. That seems okay. Requirements: Minimum Qualifications (education, experience, licensure, certification). Could be a list. Qualifications: Preferred Qualifications (skills, knowledge, abilities). Could be list. Skills: maybe combine with Preferred Qualifications? But we already have Skills section; we could put the preferred skills there. However we already used Qualifications for preferred qualifications; maybe we treat Requirements as minimum qualifications, Qualifications as preferred qualifications, Skills as maybe the same? But we need to avoid thin sections. Better to have: About the role (prose), Responsibilities (bullet list of duties), Requirements (minimum qualifications bullet list), Qualifications (preferred qualifications bullet list), Benefits (benefits bullet list). Skills maybe not needed if we already have Qualifications. But the instruction says use headings for sections like Skills, Benefits, Pay, Schedule. We should include a section only if posting has real specific content for it. We have content for Skills (the preferred skills). So we could have Skills section. Qualifications could be for minimum qualifications? Actually they said "Qualifications" heading could be used for qualifications (maybe both). But we have both minimum and preferred. Could combine? But we need to avoid thin sections. Perhaps we do: About the role (prose), Responsibilities (bullet list), Requirements (minimum qualifications bullet list), Skills (preferred skills bullet list), Benefits (benefits bullet list). No Qualifications heading. Check if we need to include "Qualifications" heading: The posting has "Minimum Qualifications" and "Preferred Qualifications". Could treat "Requirements" as minimum qualifications, "Qualifications" as preferred qualifications. But then we also have Skills heading which might duplicate. Better to follow typical structure: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. But we have limited content; we can assign: - About the role: intro paragraph. - Responsibilities: bullet list of duties (performing procedures, operating equipment, patient care, providing images, commitment to patient care, collaborative communication). - Requirements: bullet list of minimum qualifications (education, experience, licensure, certification). - Qualifications: bullet list of preferred qualifications (maybe the same as skills? Actually preferred qualifications include knowledge, skills, abilities). Could be Qualifications. - Skills: maybe we could list specific skills like "knowledge in producing diagnostic images", "strong attention to detail", etc. But that overlaps with Qualifications. To avoid duplication, we could treat Qualifications as the preferred qualifications (knowledge, skills, abilities) and Skills as maybe the physical requirements? But physical requirements are not skills. Hmm. Alternatively, we could combine: Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (maybe physical requirements? but those are not skills). Better to follow the instruction: Use headings for sections only when posting has real specific content. So we need to decide which sections we have content for: - About the role: yes. - Responsibilities: we can derive duties from the description. - Requirements: yes (minimum qualifications). - Qualifications: yes (preferred qualifications). - Skills: maybe we could list specific skills from preferred qualifications (knowledge, attention to detail, communication, etc.) but that's essentially the same as qualifications. However we could still have a Skills section listing those skills. But then Qualifications would be redundant. Perhaps we treat Qualifications as the preferred qualifications (knowledge, skills, abilities) and Skills as maybe the technical skills like operating ultrasound equipment, recognizing abnormalities, etc. But again overlapping. Given the instruction to prefer a few substantive sections over many thin ones, we should avoid splitting too finely. So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits. That's five sections. Skills could be omitted because its content is covered in Qualifications. Pay and Schedule omitted. Thus output:
About the role
... (the intro paragraph)
Responsibilities
- Perform a variety of diagnostic and interventional ultrasound procedures to assist in diagnosing and monitoring medical conditions.
- Operate ultrasound equipment with technical expertise.
- Provide accurate and high-quality diagnostic images.
- Demonstrate strong commitment to patient care.
- Communicate and collaborate effectively with patients and healthcare professionals.
Requirements
- Education: Graduate of a school of Sonography and completed required clinical hours OR received on‑the‑job training by a Preceptor who is registered in Cardiac ultrasound.
- Experience: One (1) year of relevant experience.
- Licensure: State licensure may be required depending on the specific state of practice.
- Certification: ARDMS (RDCS) or CCI(RCS); Basic Life Support (BLS).
Qualifications
- Knowledge in producing diagnostic images proficiently with the ability to recognize technical abnormalities.
- Strong attention to detail and ability to follow complex instructions.
- Excellent communication and interpersonal skills.
- Ability to work effectively in a fast‑paced, collaborative environment.
- Knowledge of protocols and ability to make adjustments as needed.
- Knowledge of safe & proper machine operation.
- Knowledge of machine emergency procedures and radiation safety procedures.
- Flexibility.
Benefits
- Medical, dental, and vision coverage.
- Paid time off.
- Tuition support.
- Matched retirement plans for team members working 32+ hours per pay period.
after the list describing the culture. That's still part of Benefits section? Might be okay to keep as prose within Benefits. However the instruction: Use
for prose. So we could have Benefits section with a
- for the tangible benefits and then a
- Medical, dental, and vision coverage.
- Paid time off.
- Tuition support.
- Matched retirement plans for team members working 32+ hours per pay period.
for the cultural statements. That preserves all substantive info. Thus Benefits section:
Benefits
Join a caring, collaborative team where your voice matters. At Mercy, you'll help shape the future of healthcare through innovation, technology, and compassion. As we grow, you'll grow with us.
Now check for any leftover info: The "Physical Requirements" we haven't included. That's substantive; we need to include it somewhere. Could be part of Requirements or a separate section like "Physical Requirements". But we don't have a heading for Physical Requirements; we could include under Requirements as additional bullet points. Or we could create a separate section "Physical Requirements". The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't list Physical Requirements as a predefined heading, but we could still use a heading if we want, but the instruction says "Use