Patient Scheduling - Phone Virtual Interview Events
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Fold minor metadata into short
or drop
- Preserve ALL substantive information
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions
- Include section ONLY when posting has real specific content
- Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment, no /, no markdown code fences
Now, let's structure:
1. The intro paragraph: "Be the friendly first point of contact..." - this is "About the role" or similar. I'll use
About the role
with .
2. Phone interview event dates/times: This is specific info about interview events. Could be under a heading like "Interview events" or "Application process". But the rules say remove application instructions. However, this is specific event dates/times, not generic instructions. Might be considered metadata. The rules say "fold minor metadata into a short
or drop it." This seems like minor metadata about interview scheduling. I'll include as a short paragraph under a heading maybe "Interview events" but the rules say only include sections with real specific content. This is specific. But it's about the application process, which might be considered application instructions. The rules say "remove ... application instructions". I think I should drop it or fold into a short paragraph. Since it's specific dates, maybe keep as a paragraph under a heading? But the rules say "never create ... sections unless the posting actually states them". The posting states "Pre-scheduled Phone Interview Event Dates/Times" with dates. That's a section. But it's application-related. I'll include it as a section with heading "Interview events" and list the dates.
3. Work Schedule: "Hours may vary based upon operational needs of the clinic." This is schedule info. The rules say never create Schedule section unless posting actually states them. It does state it, but it's vague ("Hours may vary..."). That's placeholder-like. The rules say never emit heading followed by filler/placeholder text (e.g., "varies"). So I should NOT create a Schedule section for this. I'll fold into a short paragraph maybe under "About the role" or separate paragraph.
4. Pay: "UW Health offers a competitive compensation and benefits package. Work experience that is relevant to the position will be taken into consideration when determining the starting base pay." This is pay info. It's somewhat generic but does state something. The rules say never create Pay section unless posting actually states them. It does state, but it's generic. However, it's not "commensurate with experience" exactly, but similar. The rules say never emit heading followed by filler/placeholder text (e.g., "commensurate with experience"). This is similar. I think I should not create a Pay section. Fold into a paragraph.
5. "Be part of something remarkable" with bullet points of duties. This is Responsibilities. I'll create
Responsibilities
with - for each duty.
6. Education: Minimum and Preferred. This is Qualifications or Requirements. I'll create
Qualifications
with subsections? But rules say use for section headings. Could have Education under Qualifications. I'll do Qualifications
then ? But only allowed? The rules say "use for section headings". It doesn't forbid , but likely they want only for top-level sections. I'll keep flat: maybe "Education" as a heading? But the rules list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Qualifications" is a heading. I'll put Education under Qualifications as a list.
7. Work Experience: Two roles with different requirements. This is also Qualifications/Requirements. I'll include under Qualifications or separate "Requirements" heading. The rules have both "Requirements" and "Qualifications" as example headings. I'll use "Requirements" for the experience requirements. But Education is also a requirement. I'll combine under "Qualifications" with sub-lists.
8. Commitment to Social Impact and Belonging: EEO boilerplate - remove.
9. Job Description links at end - remove.
Now, let's decide on sections:
- About the role (intro paragraph)
- Interview events (dates) - but is this application instructions? The rules say remove application instructions. However, this is specific event dates. Might be considered part of the posting's unique content. I'll include as a short section with heading "Interview events" and list dates.
- Responsibilities (list of duties)
- Qualifications (Education and Experience)
- Maybe a note about pay and schedule in a paragraph at the end? But rules say not to create sections for them if they are filler. I'll include a short paragraph under "About the role" or separate "Additional information" but not a heading.
Better to have:
About the role
Be the friendly first point of contact...
Pre-scheduled phone interview events are available on the following dates: ...
Hours may vary based upon operational needs of the clinic. UW Health offers a competitive compensation and benefits package; starting base pay considers relevant work experience.
Responsibilities
- Schedule appointments via phone, in-person or electronic correspondence.
- Complete multi-disciplinary scheduling.
- Take incoming phone calls from patients and their families to assist them with their appointment scheduling needs.
- Make outgoing phone calls to patients to schedule their appointments.
- Coordinate with clinic staff to ensure that patients receive appropriate care in a timely manner.
Qualifications
Education
? But only allowed? The rules say "use for section headings". It doesn't say you can't use , but to be safe, I'll use for each sub-section? That would create many headings. The example headings include "Qualifications" as one. I'll keep Qualifications as one heading and use lists with labels.
I'll do:
Qualifications
Education: Minimum – High school diploma or equivalent. Preferred – Associate or Bachelor’s degree in Business Administration, Healthcare, or other related field.
Patient Scheduling Specialist experience: Minimum – One (1) year of previous experience in an office or customer service environment. Preferred – Previous experience working in healthcare; previous experience scheduling patients; previous experience with answering phones, greeting clients and customers in person.
Patient Scheduling Coordinator experience: Advanced level scheduling of patients. Minimum – One (1) year of previous experience working in an office or customer service environment. Preferred – One (1) year or more experience working with electronic medical scheduling.
But the rules say use - for any list of duties/requirements/benefits. The experience requirements are lists. I could make them lists.
Better:
Qualifications
Education
? Not allowed? I'll use for each? That would be too many. The rules: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect only those top-level headings. I'll keep Qualifications as one heading and use for each category.
I'll structure:
Qualifications
- Education: Minimum – High school diploma or equivalent. Preferred – Associate or Bachelor’s degree in Business Administration, Healthcare, or other related field.
- Patient Scheduling Specialist: Minimum – One (1) year of previous experience in an office or customer service environment. Preferred – Previous experience working in healthcare; previous experience scheduling patients; previous experience with answering phones, greeting clients and customers in person.
- Patient Scheduling Coordinator: Advanced level scheduling of patients. Minimum – One (1) year of previous experience working in an office or customer service environment. Preferred – One (1) year or more experience working with electronic medical scheduling.
But the rules say "use - for any list of duties/requirements/benefits". This is a list of requirement categories, each with details. That's okay.
Alternatively, separate lists for each. But I think this is fine.
Now, the interview events: I'll include as a list under a heading "Interview events". But is that a standard heading? Not in the example list. The example headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Interview events" is not there. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has specific dates. I could fold into About the role as a paragraph. That might be better to avoid extra heading.
I'll fold interview events into About the role paragraph.
Similarly, pay and schedule into About the role.
Thus final HTML:
About the role
Be the friendly first point of contact for patients and families to help connect them with exceptional care at UW Health.
Pre-scheduled phone interview events are available on the following dates: October 29 from 8:15 am – 12:00 pm; November 12 from 12:15 pm – 4:00 pm; November 19 from 8:15 am – 12:00 pm; December 3 from 12:15 pm – 4:00 pm; December 17 from 8:15 am – 12:00 pm.
Hours may vary based upon operational needs of the clinic. UW Health offers a competitive compensation and benefits package; starting base pay considers relevant work experience.
Responsibilities
- Schedule appointments via phone, in-person or electronic correspondence.
- Complete multi-disciplinary scheduling.
- Take incoming phone calls from patients and their families to assist them with their appointment scheduling needs.
- Make outgoing phone calls to patients to schedule their appointments.
- Coordinate with clinic staff to ensure that patients receive appropriate care in a timely manner.
Qualifications
- Education: Minimum –
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Fold minor metadata into short
or drop - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real specific content - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Now, let's structure: 1. The intro paragraph: "Be the friendly first point of contact..." - this is "About the role" or similar. I'll use
About the role
with. 2. Phone interview event dates/times: This is specific info about interview events. Could be under a heading like "Interview events" or "Application process". But the rules say remove application instructions. However, this is specific event dates/times, not generic instructions. Might be considered metadata. The rules say "fold minor metadata into a short
or drop it." This seems like minor metadata about interview scheduling. I'll include as a short paragraph under a heading maybe "Interview events" but the rules say only include sections with real specific content. This is specific. But it's about the application process, which might be considered application instructions. The rules say "remove ... application instructions". I think I should drop it or fold into a short paragraph. Since it's specific dates, maybe keep as a paragraph under a heading? But the rules say "never create ... sections unless the posting actually states them". The posting states "Pre-scheduled Phone Interview Event Dates/Times" with dates. That's a section. But it's application-related. I'll include it as a section with heading "Interview events" and list the dates. 3. Work Schedule: "Hours may vary based upon operational needs of the clinic." This is schedule info. The rules say never create Schedule section unless posting actually states them. It does state it, but it's vague ("Hours may vary..."). That's placeholder-like. The rules say never emit heading followed by filler/placeholder text (e.g., "varies"). So I should NOT create a Schedule section for this. I'll fold into a short paragraph maybe under "About the role" or separate paragraph. 4. Pay: "UW Health offers a competitive compensation and benefits package. Work experience that is relevant to the position will be taken into consideration when determining the starting base pay." This is pay info. It's somewhat generic but does state something. The rules say never create Pay section unless posting actually states them. It does state, but it's generic. However, it's not "commensurate with experience" exactly, but similar. The rules say never emit heading followed by filler/placeholder text (e.g., "commensurate with experience"). This is similar. I think I should not create a Pay section. Fold into a paragraph. 5. "Be part of something remarkable" with bullet points of duties. This is Responsibilities. I'll create
Responsibilities
with- for each duty.
6. Education: Minimum and Preferred. This is Qualifications or Requirements. I'll create
Qualifications
with subsections? But rules say usefor section headings. Could have Education under Qualifications. I'll do
Qualifications
then? But only
allowed? The rules say "use
for section headings". It doesn't forbid
, but likely they want only
for top-level sections. I'll keep flat: maybe "Education" as a heading? But the rules list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Qualifications" is a heading. I'll put Education under Qualifications as a list. 7. Work Experience: Two roles with different requirements. This is also Qualifications/Requirements. I'll include under Qualifications or separate "Requirements" heading. The rules have both "Requirements" and "Qualifications" as example headings. I'll use "Requirements" for the experience requirements. But Education is also a requirement. I'll combine under "Qualifications" with sub-lists. 8. Commitment to Social Impact and Belonging: EEO boilerplate - remove. 9. Job Description links at end - remove. Now, let's decide on sections: - About the role (intro paragraph) - Interview events (dates) - but is this application instructions? The rules say remove application instructions. However, this is specific event dates. Might be considered part of the posting's unique content. I'll include as a short section with heading "Interview events" and list dates. - Responsibilities (list of duties) - Qualifications (Education and Experience) - Maybe a note about pay and schedule in a paragraph at the end? But rules say not to create sections for them if they are filler. I'll include a short paragraph under "About the role" or separate "Additional information" but not a heading. Better to have:
About the role
Be the friendly first point of contact...
Pre-scheduled phone interview events are available on the following dates: ...
Hours may vary based upon operational needs of the clinic. UW Health offers a competitive compensation and benefits package; starting base pay considers relevant work experience.
Responsibilities
- Schedule appointments via phone, in-person or electronic correspondence.
- Complete multi-disciplinary scheduling.
- Take incoming phone calls from patients and their families to assist them with their appointment scheduling needs.
- Make outgoing phone calls to patients to schedule their appointments.
- Coordinate with clinic staff to ensure that patients receive appropriate care in a timely manner.
Qualifications
Education
? But onlyallowed? The rules say "use
for section headings". It doesn't say you can't use
, but to be safe, I'll use
for each sub-section? That would create many headings. The example headings include "Qualifications" as one. I'll keep Qualifications as one heading and use lists with labels. I'll do:
Qualifications
Education: Minimum – High school diploma or equivalent. Preferred – Associate or Bachelor’s degree in Business Administration, Healthcare, or other related field.
Patient Scheduling Specialist experience: Minimum – One (1) year of previous experience in an office or customer service environment. Preferred – Previous experience working in healthcare; previous experience scheduling patients; previous experience with answering phones, greeting clients and customers in person.
Patient Scheduling Coordinator experience: Advanced level scheduling of patients. Minimum – One (1) year of previous experience working in an office or customer service environment. Preferred – One (1) year or more experience working with electronic medical scheduling.
But the rules say use- for any list of duties/requirements/benefits. The experience requirements are lists. I could make them lists.
Better:
Qualifications
Education
? Not allowed? I'll usefor each? That would be too many. The rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect only those top-level headings. I'll keep Qualifications as one heading and use
- for each category.
I'll structure:
- Education: Minimum – High school diploma or equivalent. Preferred – Associate or Bachelor’s degree in Business Administration, Healthcare, or other related field.
- Patient Scheduling Specialist: Minimum – One (1) year of previous experience in an office or customer service environment. Preferred – Previous experience working in healthcare; previous experience scheduling patients; previous experience with answering phones, greeting clients and customers in person.
- Patient Scheduling Coordinator: Advanced level scheduling of patients. Minimum – One (1) year of previous experience working in an office or customer service environment. Preferred – One (1) year or more experience working with electronic medical scheduling.
- for any list of duties/requirements/benefits". This is a list of requirement categories, each with details. That's okay.
Alternatively, separate lists for each. But I think this is fine.
Now, the interview events: I'll include as a list under a heading "Interview events". But is that a standard heading? Not in the example list. The example headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Interview events" is not there. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has specific dates. I could fold into About the role as a paragraph. That might be better to avoid extra heading.
I'll fold interview events into About the role paragraph.
Similarly, pay and schedule into About the role.
Thus final HTML:
About the role
Be the friendly first point of contact for patients and families to help connect them with exceptional care at UW Health.
Pre-scheduled phone interview events are available on the following dates: October 29 from 8:15 am – 12:00 pm; November 12 from 12:15 pm – 4:00 pm; November 19 from 8:15 am – 12:00 pm; December 3 from 12:15 pm – 4:00 pm; December 17 from 8:15 am – 12:00 pm.
Hours may vary based upon operational needs of the clinic. UW Health offers a competitive compensation and benefits package; starting base pay considers relevant work experience.
Responsibilities
- Schedule appointments via phone, in-person or electronic correspondence.
- Complete multi-disciplinary scheduling.
- Take incoming phone calls from patients and their families to assist them with their appointment scheduling needs.
- Make outgoing phone calls to patients to schedule their appointments.
- Coordinate with clinic staff to ensure that patients receive appropriate care in a timely manner.
Qualifications
- Education: Minimum –
Qualifications