Contact Center Referral Specialist I
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent. Remove boilerplate (cookie/navigation/legal/EEO etc). Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them.
Let's parse the posting.
Job Description paragraph: "The Referral Specialist is the first connection between Intermountain and patients and is responsible to focus on establishing collaborative relationships with patients and fellow caregivers (employees) to deliver the highest level of customer/patient satisfaction. Referral Specialists are responsible for fostering relationships with patients, parents and guardians regarding the patient's care to include ensuring compliance with managed care, commercial insurance, and public insurance requirements, submitting and tracking referrals, and providing efficient patient flow and service excellence. This is a hybrid position required to work in office as needed Schedule - Monday - Friday 8:00am - 5:00pm Pacific Standard Time"
So we have: About the role (maybe description). Responsibilities: list of duties. Requirements: maybe minimum requirements. Qualifications: maybe preferred requirements? Skills: list. Benefits: mention of benefits package. Pay: hourly range $19.41 - $28.14. Schedule: Monday-Friday 8:00am-5:00pm PST.
Also location: Nevada Central Office Work City Las Vegas Work State Nevada. Scheduled Weekly Hours 40.
We need to decide sections.
We have "About the role": could be the initial paragraph describing role.
"Responsibilities": essential functions list.
"Requirements": Minimum Requirements.
"Qualifications": Preferred Requirements? Could combine but we need separate sections only if content.
"Skills": list of skills.
"Benefits": mention of benefits package.
"Pay": hourly range.
"Schedule": schedule and weekly hours.
We must not include sections with filler. All these have content.
We must not repeat job title. Use for each section heading.
We must use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive info; do not invent or summarize away detail.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the long legal statements at end: "We care about your well-being..." etc. That's benefits description but it's generic; we need to keep benefits info? The posting says: "We care about your well-being – mind, body, and spirit – which is why we provide our caregivers a generous benefits package that covers a wide range of programs to foster a sustainable culture of wellness that encompasses living healthy, happy, secure, connected, and engaged. Learn More About Our Comprehensive Benefits Package Here." That's somewhat generic but still mentions benefits package. It's not specific details like health insurance etc. Should we include? The instruction: "Prefer a few substantive sections over many thin ones." Also "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')". The benefits description is vague but still mentions benefits package. It's not specific like "health, dental, 401k". Might be considered filler? However it's the only benefits info. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits package generically. So we can include Benefits section with that sentence. But we should avoid fluff like "Learn More About Our Comprehensive Benefits Package Here." That's basically a link instruction; maybe we can keep the sentence about benefits package but drop the "Learn More..." as it's application instruction? It's not exactly application instruction but it's a call to action. Might be considered boilerplate. Safer to include just the benefits sentence: "We care about your well-being – mind, body, and spirit – which is why we provide our caregivers a generous benefits package that covers a wide range of programs to foster a sustainable culture of wellness that encompasses living healthy, happy, secure, connected, and engaged." That's still somewhat generic but it's what they wrote.
Pay: "The hourly range for this position is listed below. Actual hourly rate dependent upon experience. $19.41 - $28.14". We'll include that.
Schedule: "This is a hybrid position required to work in office as needed Schedule - Monday - Friday 8:00am - 5:00pm Pacific Standard Time" plus "Scheduled Weekly Hours 40". We'll combine.
Location info: "Location: Nevada Central Office Work City Las Vegas Work State Nevada". Could be part of About the role or maybe a separate section? Not listed as a heading; we could incorporate into About the role paragraph.
We must not include duplicated lines.
Now craft HTML.
We'll have:
About the role
The Referral Specialist is the first connection between Intermountain and patients and is responsible for establishing collaborative relationships with patients and fellow caregivers (employees) to deliver the highest level of customer/patient satisfaction. Referral Specialists foster relationships with patients, parents and guardians regarding the patient's care, ensuring compliance with managed care, commercial insurance, and public insurance requirements, submitting and tracking referrals, and providing efficient patient flow and service excellence. This is a hybrid position required to work in office as needed. Location: Nevada Central Office, Las Vegas, Nevada. Scheduled weekly hours: 40.
But note schedule and weekly hours maybe better under Schedule section. We'll keep location there.
Responsibilities: essential functions list.
We need to extract essential functions bullet points from "Essential Functions". They are sentences separated by periods. Let's list:
- Effectively identifies and resolves patient, provider, and staff requests which may include; referral processing, scheduling/registration, business/billing/payor inquiries, and medical requests.
- Uses analytical skills and technical resources to anticipate and resolve patient requests, demonstrates critical thinking and problem solving during challenging patient interactions and situations with ability to recognize and follow appropriate procedures for medical and non-medical emergencies.
- Contributes to and supports enterprise productivity and quality measures/initiatives by participating, planning, communicating, and encouraging team and individual contributions toward Intermountain Health Key Performance Indicators.
- Verifies eligibility and benefits; obtains authorizations, and tracks referrals to ensure compliance with guidelines.
- Acts as a liaison between hospitals, physicians, health plans, vendors and patients or other referral sources to submit for insurance authorization for procedures, specialist visits for patients referred by an Intermountain primary care provider.
- Gathers pertinent information from insurance carriers, financial counselors and other ancillary staff to make certain of the patients’ financial obligations for services provided.
- Documents appropriate and complete information within the referral shell to include authorization information, location patient referred to close the loop, coordinating with teams, providers, staff, insurance companies, patients, and other clinics.
- Follows the three-touch process, reach out to patient via MyChart, phone call and letter.
- Forwards all pertinent medical records and authorization information referred to the provider’s office.
We'll put each as - .
Requirements: Minimum Requirements list:
- Demonstrated experience using multiple business software applications and insurance web portals simultaneously
- Prior experience in healthcare
We'll list.
Qualifications: Preferred Requirements:
- Associate or higher level degree
- One year of experience with referral services, referral processing, authorization/referral claims administration or a directly related field
We'll list.
Skills: list:
- Medical Terminology
- Computer Literacy
- Customer Service
- Electronic Medical Records (EMR)
- Data Entry
- Problem Solving
- Communication (Written/Oral)
- Detail Oriented
- Critical Thinking
- Analytical Thinking
- Interpersonal skills
We'll list.
Benefits: paragraph as above.
Pay: paragraph with hourly range.
Schedule: paragraph with schedule and weekly hours.
We must not include any other sections like "Physical Requirements". The instruction says to use headings only for those listed; we could omit Physical Requirements because not in list. But we must preserve ALL substantive information; do not invent or summarize away detail. If we omit Physical Requirements, we lose that info. However the instruction says to 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. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we should use those headings for sections; but we could also include other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it gives examples. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a Physical Requirements section if we want, but it's not in the examples. Safer to stick to the given headings and incorporate Physical Requirements info into another section, maybe Responsibilities or Requirements? But it's substantive; we need to preserve it. Could we add a Physical Requirements
? The instruction didn't forbid, but the examples limited to those. Might be okay but risk. Better to incorporate into Responsibilities or Requirements? It's about physical demands, not exactly responsibilities. Could add a separate section but not in list; risk of being marked wrong. I'd rather add a Physical Requirements section as Physical Requirements
because it's substantive and we need to preserve. 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 exhaustive. So we can add others.
Thus include Physical Requirements.
Now we need to ensure we don't include boilerplate like "We care about your well-being..." we kept benefits sentence. Also we need to remove the line "Learn More About Our Comprehensive Benefits Package Here." and the rest of legal statements.
Also remove duplicated lines: there may be duplicate of schedule? We'll just include once.
Now craft final HTML.
We'll open with About the role
then
...
Then Responsibilities
- ...
Then Requirements
...
Then Qualifications
...
Then Skills
...
Then Benefits
...
Then Pay
...
Then Schedule
...
Then Physical Requirements
... maybe list.
Physical Requirements text: "Ongoing need for employee to see and read information, labels, monitors, identify equipment and supplies, and be able to assess customer needs.Frequent interactions with customers that require employee to communicate as well as understand spoken information, alarms, needs, and issues quickly and accurately.Manual dexterity of hands and fingers to manipulate complex and delicate equipment with precision and accuracy. This includes frequent computer, phone, and cable set-up and use.Expected to lift and utilize full range of movement to transport, pull, and push equipment. Will also work on hands and knees and bend to set-up, troubleshoot, lift, and carry supplies and equipment. Typically includes items of varying weights,
- for any list of duties/requirements/benefits, and
for prose. We need to preserve all substantive info; do not invent or summarize away detail. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to cut out the long legal statements at end: "We care about your well-being..." etc. That's benefits description but it's generic; we need to keep benefits info? The posting says: "We care about your well-being – mind, body, and spirit – which is why we provide our caregivers a generous benefits package that covers a wide range of programs to foster a sustainable culture of wellness that encompasses living healthy, happy, secure, connected, and engaged. Learn More About Our Comprehensive Benefits Package Here." That's somewhat generic but still mentions benefits package. It's not specific details like health insurance etc. Should we include? The instruction: "Prefer a few substantive sections over many thin ones." Also "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')". The benefits description is vague but still mentions benefits package. It's not specific like "health, dental, 401k". Might be considered filler? However it's the only benefits info. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits package generically. So we can include Benefits section with that sentence. But we should avoid fluff like "Learn More About Our Comprehensive Benefits Package Here." That's basically a link instruction; maybe we can keep the sentence about benefits package but drop the "Learn More..." as it's application instruction? It's not exactly application instruction but it's a call to action. Might be considered boilerplate. Safer to include just the benefits sentence: "We care about your well-being – mind, body, and spirit – which is why we provide our caregivers a generous benefits package that covers a wide range of programs to foster a sustainable culture of wellness that encompasses living healthy, happy, secure, connected, and engaged." That's still somewhat generic but it's what they wrote. Pay: "The hourly range for this position is listed below. Actual hourly rate dependent upon experience. $19.41 - $28.14". We'll include that. Schedule: "This is a hybrid position required to work in office as needed Schedule - Monday - Friday 8:00am - 5:00pm Pacific Standard Time" plus "Scheduled Weekly Hours 40". We'll combine. Location info: "Location: Nevada Central Office Work City Las Vegas Work State Nevada". Could be part of About the role or maybe a separate section? Not listed as a heading; we could incorporate into About the role paragraph. We must not include duplicated lines. Now craft HTML. We'll have:
About the role
The Referral Specialist is the first connection between Intermountain and patients and is responsible for establishing collaborative relationships with patients and fellow caregivers (employees) to deliver the highest level of customer/patient satisfaction. Referral Specialists foster relationships with patients, parents and guardians regarding the patient's care, ensuring compliance with managed care, commercial insurance, and public insurance requirements, submitting and tracking referrals, and providing efficient patient flow and service excellence. This is a hybrid position required to work in office as needed. Location: Nevada Central Office, Las Vegas, Nevada. Scheduled weekly hours: 40.
But note schedule and weekly hours maybe better under Schedule section. We'll keep location there. Responsibilities: essential functions list. We need to extract essential functions bullet points from "Essential Functions". They are sentences separated by periods. Let's list: - Effectively identifies and resolves patient, provider, and staff requests which may include; referral processing, scheduling/registration, business/billing/payor inquiries, and medical requests. - Uses analytical skills and technical resources to anticipate and resolve patient requests, demonstrates critical thinking and problem solving during challenging patient interactions and situations with ability to recognize and follow appropriate procedures for medical and non-medical emergencies. - Contributes to and supports enterprise productivity and quality measures/initiatives by participating, planning, communicating, and encouraging team and individual contributions toward Intermountain Health Key Performance Indicators. - Verifies eligibility and benefits; obtains authorizations, and tracks referrals to ensure compliance with guidelines. - Acts as a liaison between hospitals, physicians, health plans, vendors and patients or other referral sources to submit for insurance authorization for procedures, specialist visits for patients referred by an Intermountain primary care provider. - Gathers pertinent information from insurance carriers, financial counselors and other ancillary staff to make certain of the patients’ financial obligations for services provided. - Documents appropriate and complete information within the referral shell to include authorization information, location patient referred to close the loop, coordinating with teams, providers, staff, insurance companies, patients, and other clinics. - Follows the three-touch process, reach out to patient via MyChart, phone call and letter. - Forwards all pertinent medical records and authorization information referred to the provider’s office. We'll put each as - .
Requirements: Minimum Requirements list:
- Demonstrated experience using multiple business software applications and insurance web portals simultaneously
- Prior experience in healthcare
We'll list.
Qualifications: Preferred Requirements:
- Associate or higher level degree
- One year of experience with referral services, referral processing, authorization/referral claims administration or a directly related field
We'll list.
Skills: list:
- Medical Terminology
- Computer Literacy
- Customer Service
- Electronic Medical Records (EMR)
- Data Entry
- Problem Solving
- Communication (Written/Oral)
- Detail Oriented
- Critical Thinking
- Analytical Thinking
- Interpersonal skills
We'll list.
Benefits: paragraph as above.
Pay: paragraph with hourly range.
Schedule: paragraph with schedule and weekly hours.
We must not include any other sections like "Physical Requirements". The instruction says to use headings only for those listed; we could omit Physical Requirements because not in list. But we must preserve ALL substantive information; do not invent or summarize away detail. If we omit Physical Requirements, we lose that info. However the instruction says to 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. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies we should use those headings for sections; but we could also include other headings if needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it gives examples. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a Physical Requirements section if we want, but it's not in the examples. Safer to stick to the given headings and incorporate Physical Requirements info into another section, maybe Responsibilities or Requirements? But it's substantive; we need to preserve it. Could we add a
Physical Requirements
? The instruction didn't forbid, but the examples limited to those. Might be okay but risk. Better to incorporate into Responsibilities or Requirements? It's about physical demands, not exactly responsibilities. Could add a separate section but not in list; risk of being marked wrong. I'd rather add a Physical Requirements section asPhysical Requirements
because it's substantive and we need to preserve. The instruction says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can add others. Thus include Physical Requirements. Now we need to ensure we don't include boilerplate like "We care about your well-being..." we kept benefits sentence. Also we need to remove the line "Learn More About Our Comprehensive Benefits Package Here." and the rest of legal statements. Also remove duplicated lines: there may be duplicate of schedule? We'll just include once. Now craft final HTML. We'll open with
About the role
then...
ThenResponsibilities
- ...
Requirements
- ...
Then
Qualifications
- ...
Then
Skills
- ...
Then
Benefits
...
ThenPay
...
ThenSchedule
...
ThenPhysical Requirements
- ... maybe list.
Physical Requirements text: "Ongoing need for employee to see and read information, labels, monitors, identify equipment and supplies, and be able to assess customer needs.Frequent interactions with customers that require employee to communicate as well as understand spoken information, alarms, needs, and issues quickly and accurately.Manual dexterity of hands and fingers to manipulate complex and delicate equipment with precision and accuracy. This includes frequent computer, phone, and cable set-up and use.Expected to lift and utilize full range of movement to transport, pull, and push equipment. Will also work on hands and knees and bend to set-up, troubleshoot, lift, and carry supplies and equipment. Typically includes items of varying weights,