Business Support Specialist-Full time-Nights-Dubuque
MercyOne · Dubuque, IA · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title as heading. No Job ID etc. Remove boilerplate (EEO, etc). Must preserve all substantive info.
Let's parse the posting:
- Employment Type: Full time
- Shift: Night Shift
- Description: long paragraph about MercyOne, mission, etc. Then "Join the MercyOne Family! We are looking to hire a Business Support Specialist As a Business Support Specialist at MercyOne, you will provide 24-hour/7 day a week operation/monitoring of communications center equipment and systems to hospital, client/tenants, affiliated on-campus and off-campus sites. Provides informational services to public, all campus and off-campus sites. Responsible for greeting patients and visitors, providing directions to various areas in the hospital while promoting a positive public image for MercyOne Dubuque Medical Center. Provides mailing services and meeting room coordination to hospital, medical clinic, and affiliates. Provides system support for all beeper paging. Works under general supervision of Business Support Services Director/Coordinator."
Then "ESSENTIAL FUNCTIONS" list bullet-like sentences.
Then "MINIMUM QUALIFICATIONS" list.
Then "Colleagues of MercyOne Health System enjoy competitive compensation with a full benefits package and opportunity for growth throughout the system! Visit MercyOne Careers to learn more about the benefits, culture, and career development opportunities available to you at MercyOne Health System circle of care."
Then "Want to learn more about MercyOne Dubuque? Click here: Find a Location Dubuque, Iowa (IA), MercyOne Dubuque Our Commitment Rooted in our Mission and Core Values, we honor the dignity of every person and recognize the unique perspectives, experiences, and talents each colleague brings. By finding common ground and embracing our differences, we grow stronger together and deliver more compassionate, person-centered care. We are an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, veteran status, or any other status protected by federal, state, or local law."
We must remove EEO boilerplate, navigation, legal, etc. Also remove application instructions (Visit MercyOne Careers...). Also remove "Want to learn more about MercyOne Dubuque? Click here: Find a Location Dubuque, Iowa (IA), MercyOne Dubuque". Also remove "Our Commitment ..."? That is mission statement but maybe considered substantive? It's about mission and values; could be part of About the role? Might be considered filler but it's about organization. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The mission statement is substantive? It's generic but part of description. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement is not boilerplate; it's about organization values. Could keep as part of About the role? But we have no About the role heading unless we have content. We could create an About the role section with description of MercyOne and role. The description includes mission etc. So we can put that in About the role.
Responsibilities: The essential functions list.
Requirements/Qualifications: Minimum qualifications list.
Skills: maybe derived from qualifications: knowledge of Microsoft O365, communication skills, etc. Could create Skills section.
Benefits: The posting mentions "competitive compensation with a full benefits package". That's vague but mentions benefits package. It says "full benefits package". Not specific details. The rule: never create Benefits section unless posting actually states them. It does state "full benefits package" but not specifics. Is that enough? It says "competitive compensation with a full benefits package". That is a statement about benefits existing, but not details. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits package exists, but not details. I'd argue we can include a Benefits section with that statement (full benefits package). However they also said prefer a few substantive sections over many thin ones. Could combine Benefits with Pay? But Pay not mentioned. So maybe we include Benefits with that statement.
Schedule: Night Shift mentioned. So we can include Schedule section with Night Shift.
Pay: Not mentioned, so omit.
Now we need to format.
We must not repeat job title as heading. So no
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title as heading. No Job ID etc. Remove boilerplate (EEO, etc). Must preserve all substantive info.
Let's parse the posting:
- Employment Type: Full time
- Shift: Night Shift
- Description: long paragraph about MercyOne, mission, etc. Then "Join the MercyOne Family! We are looking to hire a Business Support Specialist As a Business Support Specialist at MercyOne, you will provide 24-hour/7 day a week operation/monitoring of communications center equipment and systems to hospital, client/tenants, affiliated on-campus and off-campus sites. Provides informational services to public, all campus and off-campus sites. Responsible for greeting patients and visitors, providing directions to various areas in the hospital while promoting a positive public image for MercyOne Dubuque Medical Center. Provides mailing services and meeting room coordination to hospital, medical clinic, and affiliates. Provides system support for all beeper paging. Works under general supervision of Business Support Services Director/Coordinator."
Then "ESSENTIAL FUNCTIONS" list bullet-like sentences.
Then "MINIMUM QUALIFICATIONS" list.
Then "Colleagues of MercyOne Health System enjoy competitive compensation with a full benefits package and opportunity for growth throughout the system! Visit MercyOne Careers to learn more about the benefits, culture, and career development opportunities available to you at MercyOne Health System circle of care."
Then "Want to learn more about MercyOne Dubuque? Click here: Find a Location Dubuque, Iowa (IA), MercyOne Dubuque Our Commitment Rooted in our Mission and Core Values, we honor the dignity of every person and recognize the unique perspectives, experiences, and talents each colleague brings. By finding common ground and embracing our differences, we grow stronger together and deliver more compassionate, person-centered care. We are an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, veteran status, or any other status protected by federal, state, or local law."
We must remove EEO boilerplate, navigation, legal, etc. Also remove application instructions (Visit MercyOne Careers...). Also remove "Want to learn more about MercyOne Dubuque? Click here: Find a Location Dubuque, Iowa (IA), MercyOne Dubuque". Also remove "Our Commitment ..."? That is mission statement but maybe considered substantive? It's about mission and values; could be part of About the role? Might be considered filler but it's about organization. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The mission statement is substantive? It's generic but part of description. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement is not boilerplate; it's about organization values. Could keep as part of About the role? But we have no About the role heading unless we have content. We could create an About the role section with description of MercyOne and role. The description includes mission etc. So we can put that in About the role.
Responsibilities: The essential functions list.
Requirements/Qualifications: Minimum qualifications list.
Skills: maybe derived from qualifications: knowledge of Microsoft O365, communication skills, etc. Could create Skills section.
Benefits: The posting mentions "competitive compensation with a full benefits package". That's vague but mentions benefits package. It says "full benefits package". Not specific details. The rule: never create Benefits section unless posting actually states them. It does state "full benefits package" but not specifics. Is that enough? It says "competitive compensation with a full benefits package". That is a statement about benefits existing, but not details. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits package exists, but not details. I'd argue we can include a Benefits section with that statement (full benefits package). However they also said prefer a few substantive sections over many thin ones. Could combine Benefits with Pay? But Pay not mentioned. So maybe we include Benefits with that statement.
Schedule: Night Shift mentioned. So we can include Schedule section with Night Shift.
Pay: Not mentioned, so omit.
Now we need to format.
We must not repeat job title as heading. So no Business Support Specialist
. Use headings for sections.
We need to decide which sections to include: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Check if we have content for each.
About the role: description of MercyOne and role overview. We'll combine the initial description paragraph plus mission etc. Must preserve all substantive info; we can't omit details. We'll need to include the description about MercyOne Dubuque being leading hospital, services, Magnet hospital, etc. Also the shift and employment type? Those could go in Schedule and Employment Type maybe but we have Schedule for Night Shift, Employment Type maybe not a heading; could be included in About the role or separate? There's no heading for Employment Type; we could include it in About the role as a sentence.
Responsibilities: essential functions list.
Requirements: minimum qualifications list.
Skills: maybe we can extract from qualifications: knowledge of Microsoft O365, communication skills, ability to interact, etc. Could be part of Requirements though. But we can still have Skills.
Benefits: statement about full benefits package.
Schedule: Night Shift.
We must not create sections with filler like "commensurate with experience". We have actual content.
Now produce HTML.
We need to wrap each section: About the role
then
...
for prose, and- for lists. We must not include markdown fences. Let's craft. About the role paragraph: Should include employment type full time, shift night shift, description of MercyOne, mission, services, Magnet hospital, and that we are hiring Business Support Specialist and what they do (overview). We'll keep it as prose. Responsibilities: list of essential functions. We'll extract each sentence after "ESSENTIAL FUNCTIONS". They are: - Adheres to the principles of caring and expected behaviors outlined in MercyOne Medical Center's Model of Caring and Trinity Health's Code of Conduct, fostering a climate where all customers are treated in a manner consistent with MercyOne’s Mission and Values. - Maintains a working knowledge of applicable Federal, State and local laws and regulations, Trinity Health’s Organizational Integrity Program, Standards of Conduct, as well as other policies and procedures in order to ensure adherence in a manner that reflects honest, ethical and professional behavior. - Performs other duties consistent with purpose of job as directed. - Receives and routes incoming telephone calls by operating the SPOK Console quickly and efficiently per established protocol. - Performs page requests and initiates security calls by operating the hospital public address system, Motorola pagers, and security radio. - Announces all emergency codes via public address system, i.e., STAT calls, ALL CODES, notifying appropriate hospital personnel and/or outside agency personnel for quick response. - Monitors all alarm panels including emergency data computer and fire panel and printer and notifies appropriate personnel when an alarm is activated in a timely manner. We'll put each as
- . Requirements: Minimum qualifications list: - High school diploma or GED required. Degree from higher level education degree that requires a high school diploma or GED as a pre-requisite is also permitted. - Previous experience in direct customer relations/communications center preferred. - Experience within Microsoft O365 (M365 Word, Powerpoint, Excel, Teams, Edge) and Internet. - Maintains a professional, collaborative work environment so as to foster a positive public image for MercyOne Medical Center. - Knows and adheres to all laws and regulations pertaining to patient health, safety and medical information (i.e. HIPAA, Stark, etc.) - Must have ability to interact with associates, physicians, visitors and patients consistent with MercyOne’s Mission & Values, Mercy’s Model of Caring, which includes the Caring Model Principles and the Guiding Behaviors, and Trinity Health’s Code of Conduct. - Must have excellent written and verbal communication skills with the ability to relate to people across all levels & diverse backgrounds; ability to handle interactions with discretion, tact & courtesy. - Ability to adapt to constant interruptions and handle critical response situations in a CALM, ORDERLY MANNER. - Ability to quickly and accurately recognize names and numbers in various department databases. We'll put each as
- .
Skills: Could be derived: knowledge of Microsoft O365, communication skills, ability to interact, etc. But to avoid duplication, maybe we skip Skills and incorporate into Requirements. However we need to decide sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Skills into one section called Requirements/Qualifications? But headings must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Requirements and Qualifications both? Might be thin. Better to have Requirements (includes qualifications) and Skills separate if we have distinct content. But we might not have enough distinct content for Skills separate; we could still make Skills with bullet points like "Excellent written and verbal communication", "Proficiency in Microsoft O365", "Ability to handle critical situations calmly", "Ability to recognize names and numbers quickly". That's essentially same as requirements. Might be considered thin. I'd rather not create Skills if it's just repeating. Could combine Requirements and Qualifications into one heading "Requirements". But we have both Requirements and Qualifications as possible headings; we can choose one. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can pick any of those. We'll include Requirements and maybe Qualifications if we have distinct content. But we have minimum qualifications; that's qualifications. So we could use Qualifications heading for the list. Then we could have Responsibilities separate. And About the role separate. Benefits separate. Schedule separate. That's five sections. Thus: - About the role (prose) - Responsibilities (ul) - Qualifications (ul) - Benefits (p) - Schedule (p) We'll omit Skills. Now ensure we don't include boilerplate: Remove EEO, navigation, legal, application instructions, etc. Also remove lines like "Visit MercyOne Careers to learn more about the benefits, culture, and career development opportunities available to you at MercyOne Health System circle of care." That's application instructions/benefits promo; we should remove. Also remove "Want to learn more about MercyOne Dubuque? Click here: Find a Location Dubuque, Iowa (IA), MercyOne Dubuque". Remove. Also remove "Our Commitment Rooted in our Mission and Core Values, we honor the dignity of every person..." That's mission statement but could be considered part of About the role? It's about organization values; we could keep as part of About the role but it's somewhat generic. However it's not boilerplate; it's about mission and values. Might be okay to keep. But we already have mission description earlier. Might be duplicate. Safer to keep only the earlier description about MercyOne Dubuque services and mission. The "Our Commitment" paragraph is similar to earlier mission; could be considered duplicate. We'll drop it to avoid duplication. Now craft About the role paragraph: "Employment Type: Full time. Shift: Night Shift. At MercyOne, health care is more than just a doctor’s visit or a place to go when you’re in need of medical attention. Our Mission is based on improving the health of our communities – that means not only when you are sick but keeping you well. MercyOne Dubuque is the leading hospital in the tri-states, offering the only comprehensive cardiology center