Patient Access QA Auditor
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- 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 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
2. **Analyze the Input Text:**
Let me parse the job posting content:
- Mission/Intro: "At OSS Health, our mission is to continually strive to be the healthcare leader in quality, innovation and value. We make every effort to understand and exceed the expectations and needs of our patients. We are committed to providing an environment that is safe, respectful, and dignified at all times. Joining OSS Health means joining a culture of excellence and teamwork, with a strong focus on employee development and community support. OSS Health offers a great work environment, professional development opportunities, meaningful careers, and competitive compensation. Are you ready to provide a 5-star “OSSOME” experience? Apply today!"
- JOB SUMMARY: "The Quality Assurance Auditor is responsible for the completion of manual and system- driven inspections aimed at measuring Quality Assurance across all Patient Access functions. The auditor has responsibility for preparing reports to communicate results and findings to the QA Coordinator."
- SCHEDULE: "FT, 40 hours per week - Monday-Friday 8:00am - 4:30pm"
- ESSENTIAL DUTIES AND RESPONSIBILITIES: A bulleted list of duties
- EDUCATION: "High school diploma or its equivalent."
- EXPERIENCE AND QUALIFICATIONS: A list of requirements/qualifications
- BENEFITS INCLUDE: A list of benefits
Now I need to map these to the requested HTML structure using `
` for section headings. The allowed headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's figure out the mapping:
- "About the role" could cover the mission/job summary
- "Responsibilities" = Essential Duties and Responsibilities
- "Requirements" or "Qualifications" = Education, Experience and Qualifications
- "Skills" might be part of qualifications, but I'll see
- "Benefits" = Benefits Include
- "Pay" = Not explicitly stated, but "Competitive Wages" is mentioned under Benefits. However, the rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule is stated. Benefits are stated. Pay "Competitive Wages" is stated but vague. I'll be careful. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule is stated. Benefits are stated. Pay is mentioned as "Competitive Wages" but it's very generic. I think I should include Benefits and Schedule since they have specific content. Pay might be tricky. The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if I include Pay, I need actual content. "Competitive Wages" is content, but is it enough? I'll include it if it's substantive. Actually, the rule prefers a few substantive sections over many thin ones. I'll see.
Let's list the sections I can confidently create with real specific content:
- About the role (mission + job summary)
- Responsibilities (essential duties)
- Requirements/Qualifications (education, experience, qualifications)
- Benefits (specific benefits listed)
- Schedule (specific schedule)
What about Skills? The qualifications list some skills: "excellent analytical and problem-solving skills", "excellent written and verbal communication skills", "proficient computer skills", etc. I could fold those into Qualifications or make a Skills section. The rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to decide which to include. I'll probably do: About the role, Responsibilities, Requirements, Benefits, Schedule. Or maybe Qualifications instead of Requirements. Let's see the exact wording: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists examples, not an exhaustive required list. I should pick the ones that have real content and avoid thin ones.
Let's map the content:
- "About the role": I can combine the mission statement and the Job Summary. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Quality Assurance Auditor". I won't use that as a heading. I'll use "About the role" to cover the mission and summary, but I need to be careful not to make it thin. The mission is substantive. The Job Summary is substantive. I'll put them under "About the role" or maybe just "About the role" as an h3, then prose.
- "Responsibilities": "ESSENTIAL DUTIES AND RESPONSIBILITIES" maps directly. I'll use `Responsibilities
` and list the duties.
- "Requirements" or "Qualifications": The posting has "EDUCATION" and "EXPERIENCE AND QUALIFICATIONS". I could use one h3 for Qualifications, covering education and experience. Or separate. I'll use `Qualifications
` and list education and experience together, or use `Requirements
`. The examples list both "Requirements" and "Qualifications". I'll pick one. Maybe "Qualifications" since the section is titled "EXPERIENCE AND QUALIFICATIONS". I'll use `Qualifications
`.
- "Skills": Some skills are embedded in qualifications. I could add a Skills section, but it might be thin. I'll fold skills into Qualifications or omit if not distinct. The rule: "Prefer a few substantive sections over many thin ones." I'll likely omit a separate Skills section unless I can make it substantive. I'll include skills as part of Qualifications or drop them if they're just repetitions. Actually, the qualifications list specific skills: "excellent analytical and problem-solving skills", "excellent written and verbal communication skills", "proficient computer skills", "ability to work efficiently, independently and prioritize tasks", "understand procedures associated with a variety of health insurance plans", "strong understanding of healthcare billing regulatory and compliance requirements". These are substantial. I could make a Skills section, but I'll probably integrate them into Qualifications to keep it clean.
- "Benefits": "BENEFITS INCLUDE:" with specific list. I'll use `Benefits
`.
- "Schedule": "SCHEDULE: FT, 40 hours per week - Monday-Friday 8:00am - 4:30pm". I'll use `Schedule
`.
- "Pay": "Competitive Wages" is mentioned under Benefits. But the rule says never create Pay section unless posting actually states them, and avoid filler. "Competitive Wages" is stated, but it's very generic. I could include it, but I risk having a thin section. The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". "Competitive Wages" is not a placeholder, it's actual text. However, I'll be cautious. I think I'll include Pay if I can quote "Competitive Wages" but maybe fold it into Benefits or just mention it in a short p. Actually, the rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule and Benefits are stated. Pay is stated as "Competitive Wages". I'll include a Pay section with "Competitive Wages" but I need to make sure it's not thin. I could do `
Competitive Wages
` under a Pay heading, but the rule prefers few sections. I might just fold it into Benefits or omit Pay entirely. Let's re-read: "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." This implies I should create Pay/Schedule/Benefits only if the posting states them. Schedule and Benefits are clearly stated. Pay is stated as "Competitive Wages". I'll include Pay with that text, but I'll make sure it's substantive. Actually, I'll include it as a short paragraph.
Let's plan the HTML structure:
About the role
...mission and job summary...
Responsibilities
- ...duties...
Qualifications
- Education: High school diploma or equivalent
- Experience: Minimum two years Hospital or medical office experience in Patient Access areas
- Skills: ...
Benefits
- ...benefits...
Schedule
FT, 40 hours per week - Monday-Friday 8:00am - 4:30pm
Wait, I need to check the exact headings allowed: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "Requirements" is an option. I have "Education" and "Experience and Qualifications". I could use `Requirements
` and list education and experience under it. Or `Qualifications
`. I'll use `Qualifications
` since the section title is "EXPERIENCE AND QUALIFICATIONS".
Let's carefully extract all substantive info, remove boilerplate. The input has no cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate that I can see. It ends with "Apply today!" which is application instruction, I should remove that per rules
` 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 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 2. **Analyze the Input Text:** Let me parse the job posting content: - Mission/Intro: "At OSS Health, our mission is to continually strive to be the healthcare leader in quality, innovation and value. We make every effort to understand and exceed the expectations and needs of our patients. We are committed to providing an environment that is safe, respectful, and dignified at all times. Joining OSS Health means joining a culture of excellence and teamwork, with a strong focus on employee development and community support. OSS Health offers a great work environment, professional development opportunities, meaningful careers, and competitive compensation. Are you ready to provide a 5-star “OSSOME” experience? Apply today!" - JOB SUMMARY: "The Quality Assurance Auditor is responsible for the completion of manual and system- driven inspections aimed at measuring Quality Assurance across all Patient Access functions. The auditor has responsibility for preparing reports to communicate results and findings to the QA Coordinator." - SCHEDULE: "FT, 40 hours per week - Monday-Friday 8:00am - 4:30pm" - ESSENTIAL DUTIES AND RESPONSIBILITIES: A bulleted list of duties - EDUCATION: "High school diploma or its equivalent." - EXPERIENCE AND QUALIFICATIONS: A list of requirements/qualifications - BENEFITS INCLUDE: A list of benefits Now I need to map these to the requested HTML structure using `
` for section headings. The allowed headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's figure out the mapping:
- "About the role" could cover the mission/job summary
- "Responsibilities" = Essential Duties and Responsibilities
- "Requirements" or "Qualifications" = Education, Experience and Qualifications
- "Skills" might be part of qualifications, but I'll see
- "Benefits" = Benefits Include
- "Pay" = Not explicitly stated, but "Competitive Wages" is mentioned under Benefits. However, the rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule is stated. Benefits are stated. Pay "Competitive Wages" is stated but vague. I'll be careful. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule is stated. Benefits are stated. Pay is mentioned as "Competitive Wages" but it's very generic. I think I should include Benefits and Schedule since they have specific content. Pay might be tricky. The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So if I include Pay, I need actual content. "Competitive Wages" is content, but is it enough? I'll include it if it's substantive. Actually, the rule prefers a few substantive sections over many thin ones. I'll see.
Let's list the sections I can confidently create with real specific content:
- About the role (mission + job summary)
- Responsibilities (essential duties)
- Requirements/Qualifications (education, experience, qualifications)
- Benefits (specific benefits listed)
- Schedule (specific schedule)
What about Skills? The qualifications list some skills: "excellent analytical and problem-solving skills", "excellent written and verbal communication skills", "proficient computer skills", etc. I could fold those into Qualifications or make a Skills section. The rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to decide which to include. I'll probably do: About the role, Responsibilities, Requirements, Benefits, Schedule. Or maybe Qualifications instead of Requirements. Let's see the exact wording: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists examples, not an exhaustive required list. I should pick the ones that have real content and avoid thin ones.
Let's map the content:
- "About the role": I can combine the mission statement and the Job Summary. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Quality Assurance Auditor". I won't use that as a heading. I'll use "About the role" to cover the mission and summary, but I need to be careful not to make it thin. The mission is substantive. The Job Summary is substantive. I'll put them under "About the role" or maybe just "About the role" as an h3, then prose.
- "Responsibilities": "ESSENTIAL DUTIES AND RESPONSIBILITIES" maps directly. I'll use `Responsibilities
` and list the duties.
- "Requirements" or "Qualifications": The posting has "EDUCATION" and "EXPERIENCE AND QUALIFICATIONS". I could use one h3 for Qualifications, covering education and experience. Or separate. I'll use `Qualifications
` and list education and experience together, or use `Requirements
`. The examples list both "Requirements" and "Qualifications". I'll pick one. Maybe "Qualifications" since the section is titled "EXPERIENCE AND QUALIFICATIONS". I'll use `Qualifications
`.
- "Skills": Some skills are embedded in qualifications. I could add a Skills section, but it might be thin. I'll fold skills into Qualifications or omit if not distinct. The rule: "Prefer a few substantive sections over many thin ones." I'll likely omit a separate Skills section unless I can make it substantive. I'll include skills as part of Qualifications or drop them if they're just repetitions. Actually, the qualifications list specific skills: "excellent analytical and problem-solving skills", "excellent written and verbal communication skills", "proficient computer skills", "ability to work efficiently, independently and prioritize tasks", "understand procedures associated with a variety of health insurance plans", "strong understanding of healthcare billing regulatory and compliance requirements". These are substantial. I could make a Skills section, but I'll probably integrate them into Qualifications to keep it clean.
- "Benefits": "BENEFITS INCLUDE:" with specific list. I'll use `Benefits
`.
- "Schedule": "SCHEDULE: FT, 40 hours per week - Monday-Friday 8:00am - 4:30pm". I'll use `Schedule
`.
- "Pay": "Competitive Wages" is mentioned under Benefits. But the rule says never create Pay section unless posting actually states them, and avoid filler. "Competitive Wages" is stated, but it's very generic. I could include it, but I risk having a thin section. The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". "Competitive Wages" is not a placeholder, it's actual text. However, I'll be cautious. I think I'll include Pay if I can quote "Competitive Wages" but maybe fold it into Benefits or just mention it in a short p. Actually, the rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule and Benefits are stated. Pay is stated as "Competitive Wages". I'll include a Pay section with "Competitive Wages" but I need to make sure it's not thin. I could do `
Responsibilities
` and list the duties. - "Requirements" or "Qualifications": The posting has "EDUCATION" and "EXPERIENCE AND QUALIFICATIONS". I could use one h3 for Qualifications, covering education and experience. Or separate. I'll use `Qualifications
` and list education and experience together, or use `Requirements
`. The examples list both "Requirements" and "Qualifications". I'll pick one. Maybe "Qualifications" since the section is titled "EXPERIENCE AND QUALIFICATIONS". I'll use `Qualifications
`. - "Skills": Some skills are embedded in qualifications. I could add a Skills section, but it might be thin. I'll fold skills into Qualifications or omit if not distinct. The rule: "Prefer a few substantive sections over many thin ones." I'll likely omit a separate Skills section unless I can make it substantive. I'll include skills as part of Qualifications or drop them if they're just repetitions. Actually, the qualifications list specific skills: "excellent analytical and problem-solving skills", "excellent written and verbal communication skills", "proficient computer skills", "ability to work efficiently, independently and prioritize tasks", "understand procedures associated with a variety of health insurance plans", "strong understanding of healthcare billing regulatory and compliance requirements". These are substantial. I could make a Skills section, but I'll probably integrate them into Qualifications to keep it clean. - "Benefits": "BENEFITS INCLUDE:" with specific list. I'll use `Benefits
`. - "Schedule": "SCHEDULE: FT, 40 hours per week - Monday-Friday 8:00am - 4:30pm". I'll use `Schedule
`. - "Pay": "Competitive Wages" is mentioned under Benefits. But the rule says never create Pay section unless posting actually states them, and avoid filler. "Competitive Wages" is stated, but it's very generic. I could include it, but I risk having a thin section. The rule: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". "Competitive Wages" is not a placeholder, it's actual text. However, I'll be cautious. I think I'll include Pay if I can quote "Competitive Wages" but maybe fold it into Benefits or just mention it in a short p. Actually, the rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule and Benefits are stated. Pay is stated as "Competitive Wages". I'll include a Pay section with "Competitive Wages" but I need to make sure it's not thin. I could do `Competitive Wages
` under a Pay heading, but the rule prefers few sections. I might just fold it into Benefits or omit Pay entirely. Let's re-read: "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." This implies I should create Pay/Schedule/Benefits only if the posting states them. Schedule and Benefits are clearly stated. Pay is stated as "Competitive Wages". I'll include Pay with that text, but I'll make sure it's substantive. Actually, I'll include it as a short paragraph. Let's plan the HTML structure:About the role
...mission and job summary...
Responsibilities
- ...duties...
Qualifications
- Education: High school diploma or equivalent
- Experience: Minimum two years Hospital or medical office experience in Patient Access areas
- Skills: ...
Benefits
- ...benefits...
Schedule
FT, 40 hours per week - Monday-Friday 8:00am - 4:30pm
Wait, I need to check the exact headings allowed: "use