Patient Services Representative (PSR) - Dermatology - Plastic Surgery - WHOLEyou
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (not provided anyway)
- Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop
- Preserve ALL substantive information; do NOT invent or summarize
- Remove boilerplate (EEO, equal opportunity, scam warnings, 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 parse the content.
The posting starts with "Job Duties Description 0.6 FTE - Day Shift Starting Pay - $20.40 to $29.98 (Based on Experience) Offers for external candidates are generally made between the minimum and midpoint of the range, based on experience. At Olmsted Medical Center, we value our employees and are committed to providing a comprehensive and competitive benefits package. To keep up with the evolving trends, Olmsted Medical Center offers the following for employees who are employed at a 0.5 FTE or higher."
Then lists benefits: Medical Insurance, Paid Time Off, Dental Insurance, Vision Insurance, Basic Life Insurance, Tuition Reimbursement, Employer Paid Short-Term Disability and Long-Term Disability, Adoption Assistance Plan.
Then "Qualifications" with bullet points: Prior computer experience required, Knowledge of medical terminology preferred, General knowledge of Accounts Receivable preferred, BLS certification.
Then "Job Responsibilities" with bullet points: Greets visitors..., Patient registration..., Monitors monthly update..., Identifies primary care providers..., Answers patient questions..., Schedules and verifies..., Collects patient payments..., Works closely..., Attends education..., Orders and stocks..., Performs internal..., Other duties as assigned.
Then EEO boilerplate (remove).
Then metadata fields: Minimum Education Required: High School Diploma or Equivalent; Minimum Experience Required: None; Shift: First (Day); Number of Openings: 1; Public Transportation Accessible: Yes; Veterans Encouraged to Apply: No; Physical Required: Yes; Drug Test Required: Yes; Compensation: $11.41 / Hourly; Postal Code: 55904; Job Type: Part Time; Place of Work: On-site; Requisition ID: PATIE003905; Job Benefits: Not specified.
Note: There's a discrepancy in pay: top says $20.40 to $29.98, later says $11.41/hourly. The top seems more detailed (starting pay range). The later "Compensation" field might be a mistake or for a different role? But we must preserve all substantive information. However, the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include both? But they conflict. The top is part of the job duties description, the later is a separate field. Probably the top is the correct pay for this posting (0.6 FTE day shift). The later "Compensation: $11.41 / Hourly" might be a generic field. Since the rule says preserve all substantive information, I should include the pay range from the description. The later compensation field might be erroneous but it's there. I'll include the pay range from the description as it's more specific. The "Compensation" field says $11.41/hourly, but that might be a minimum wage? Actually, the top says "Starting Pay - $20.40 to $29.98". That's likely the correct range. I'll include that in a Pay section.
Benefits are listed in the description, so we have a Benefits section.
Qualifications and Responsibilities are clear.
Now, metadata like Minimum Education, Minimum Experience, Shift, Job Type, Place of Work, Postal Code, etc. These are minor metadata. The rule: "fold minor metadata into a short
or drop it." And "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I should not create separate headings for each metadata field. Instead, I can create a "Details" or "Position Details" section with a paragraph summarizing key metadata, or incorporate into existing sections.
The rule says: "Prefer a few substantive sections over many thin ones." So I'll create sections for: About the role (maybe), Responsibilities, Requirements/Qualifications, Benefits, Pay, Schedule (shift), and maybe a Details paragraph for other metadata.
But the rule says: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So for each heading, we need real content.
Let's decide on sections:
1. About the role: Could include the FTE, shift, job type, place of work, postal code. But the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the role" is a suggested heading. I can put a paragraph describing the role: 0.6 FTE, Day Shift, Part Time, On-site, location (postal code 55904). That's substantive.
2. Responsibilities: list from Job Responsibilities.
3. Qualifications: list from Qualifications.
4. Benefits: list from benefits.
5. Pay: include the pay range $20.40 to $29.98 based on experience, and note about external candidates. Also maybe mention the $11.41/hourly? But that seems contradictory. I'll include the range from the description as it's more detailed. The later "Compensation: $11.41 / Hourly" might be a mistake; but to preserve all substantive info, I could mention both? However, the rule says "do NOT invent or summarize away detail." But if there's conflicting info, we should present both? The posting includes both. The top is in the description, the bottom is a field. I'll include the range and note the discrepancy? But the rule says preserve all substantive information. I'll include the pay range from the description and also mention the hourly rate from the metadata? But that might be confusing. Perhaps the $11.41 is the minimum wage? Actually, the top says "Starting Pay - $20.40 to $29.98". That's likely the actual pay. The later "Compensation: $11.41 / Hourly" might be a default field. I'll include the range and note "Starting pay range: $20.40 to $29.98 per hour based on experience. Offers for external candidates are generally made between the minimum and midpoint of the range." And maybe add a note: "Note: The posting also lists a compensation of $11.41/hourly, which may be a minimum or error." But that's editorializing. Better to just include the range from the description as it's part of the job duties description. The metadata compensation field might be for a different position? But it's in the same posting. I'll include both in the Pay section: "Starting pay range: $20.40 to $29.98 per hour based on experience. Offers for external candidates are generally made between the minimum and midpoint of the range. The posting also indicates a compensation of $11.41/hourly." That preserves both.
6. Schedule: Shift is First (Day), 0.6 FTE, Part Time. So a Schedule section.
7. Requirements: Could include education, experience, certifications (BLS), physical, drug test. But Qualifications already includes some. The metadata has Minimum Education Required, Minimum Experience Required, Physical Required, Drug Test Required, BLS certification. I can combine into a Requirements section with a list.
But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Requirements and Qualifications are separate? The posting has "Qualifications" and then metadata for education/experience. I'll create a "Requirements" section that includes education, experience, certifications, physical, drug test. And "Qualifications" for the skills/knowledge list. But that might be overlapping. The posting's "Qualifications" section lists: Prior computer experience required, Knowledge of medical terminology preferred, General knowledge of Accounts Receivable preferred, BLS certification. That's qualifications. The metadata has Minimum Education Required: High School Diploma or Equivalent; Minimum Experience Required: None. So I can create a "Requirements" section with education, experience, and other requirements (physical, drug test, BLS). And a "Qualifications" section for the skills/knowledge. But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine into one "Requirements & Qualifications" section? But the example headings include both Requirements and Qualifications. I'll keep them separate if both have content.
Let's see: Qualifications has 4 bullet points. Requirements (education, experience, physical, drug test) are also substantive. I'll create two sections: "Qualifications" for the skills/knowledge, and "Requirements" for education, experience, certifications, physical, drug test.
But BLS certification appears in both? In Qualifications it's listed as "BLS certification". In metadata, not explicitly but it's a qualification. I'll include BLS in Requirements as a certification.
Now, other metadata: Number of Openings: 1, Public Transportation Accessible: Yes, Veterans Encouraged to Apply: No, Postal Code: 55904, Requisition ID: PATIE003905. These are minor metadata. I'll fold them into a short paragraph in About the role or a separate "Details" paragraph. The rule says "fold minor metadata into a short
or drop it." I'll include a paragraph at the end of About the role or a separate "Position Details" section? But the rule says only include section if real content. A paragraph is not a section heading. I can just put a
after the About the role heading.
Also, the EEO boilerplate should be removed.
Now, let's structure the HTML.
I'll start with
About the role
then a paragraph describing the role: 0.6 FTE, Day Shift, Part Time, On-site, location (Rochester, MN 55904). Then maybe a paragraph with other details: "This position has 1 opening. Public transportation accessible. Veterans encouraged to apply: No. Requisition ID: PATIE003905."
Then
for prose - Do NOT repeat job title as heading (not provided anyway) - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop - Preserve ALL substantive information; do NOT invent or summarize - Remove boilerplate (EEO, equal opportunity, scam warnings, 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 parse the content. The posting starts with "Job Duties Description 0.6 FTE - Day Shift Starting Pay - $20.40 to $29.98 (Based on Experience) Offers for external candidates are generally made between the minimum and midpoint of the range, based on experience. At Olmsted Medical Center, we value our employees and are committed to providing a comprehensive and competitive benefits package. To keep up with the evolving trends, Olmsted Medical Center offers the following for employees who are employed at a 0.5 FTE or higher." Then lists benefits: Medical Insurance, Paid Time Off, Dental Insurance, Vision Insurance, Basic Life Insurance, Tuition Reimbursement, Employer Paid Short-Term Disability and Long-Term Disability, Adoption Assistance Plan. Then "Qualifications" with bullet points: Prior computer experience required, Knowledge of medical terminology preferred, General knowledge of Accounts Receivable preferred, BLS certification. Then "Job Responsibilities" with bullet points: Greets visitors..., Patient registration..., Monitors monthly update..., Identifies primary care providers..., Answers patient questions..., Schedules and verifies..., Collects patient payments..., Works closely..., Attends education..., Orders and stocks..., Performs internal..., Other duties as assigned. Then EEO boilerplate (remove). Then metadata fields: Minimum Education Required: High School Diploma or Equivalent; Minimum Experience Required: None; Shift: First (Day); Number of Openings: 1; Public Transportation Accessible: Yes; Veterans Encouraged to Apply: No; Physical Required: Yes; Drug Test Required: Yes; Compensation: $11.41 / Hourly; Postal Code: 55904; Job Type: Part Time; Place of Work: On-site; Requisition ID: PATIE003905; Job Benefits: Not specified. Note: There's a discrepancy in pay: top says $20.40 to $29.98, later says $11.41/hourly. The top seems more detailed (starting pay range). The later "Compensation" field might be a mistake or for a different role? But we must preserve all substantive information. However, the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include both? But they conflict. The top is part of the job duties description, the later is a separate field. Probably the top is the correct pay for this posting (0.6 FTE day shift). The later "Compensation: $11.41 / Hourly" might be a generic field. Since the rule says preserve all substantive information, I should include the pay range from the description. The later compensation field might be erroneous but it's there. I'll include the pay range from the description as it's more specific. The "Compensation" field says $11.41/hourly, but that might be a minimum wage? Actually, the top says "Starting Pay - $20.40 to $29.98". That's likely the correct range. I'll include that in a Pay section. Benefits are listed in the description, so we have a Benefits section. Qualifications and Responsibilities are clear. Now, metadata like Minimum Education, Minimum Experience, Shift, Job Type, Place of Work, Postal Code, etc. These are minor metadata. The rule: "fold minor metadata into a short
or drop it." And "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I should not create separate headings for each metadata field. Instead, I can create a "Details" or "Position Details" section with a paragraph summarizing key metadata, or incorporate into existing sections. The rule says: "Prefer a few substantive sections over many thin ones." So I'll create sections for: About the role (maybe), Responsibilities, Requirements/Qualifications, Benefits, Pay, Schedule (shift), and maybe a Details paragraph for other metadata. But the rule says: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So for each heading, we need real content. Let's decide on sections: 1. About the role: Could include the FTE, shift, job type, place of work, postal code. But the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So "About the role" is a suggested heading. I can put a paragraph describing the role: 0.6 FTE, Day Shift, Part Time, On-site, location (postal code 55904). That's substantive.
2. Responsibilities: list from Job Responsibilities.
3. Qualifications: list from Qualifications.
4. Benefits: list from benefits.
5. Pay: include the pay range $20.40 to $29.98 based on experience, and note about external candidates. Also maybe mention the $11.41/hourly? But that seems contradictory. I'll include the range from the description as it's more detailed. The later "Compensation: $11.41 / Hourly" might be a mistake; but to preserve all substantive info, I could mention both? However, the rule says "do NOT invent or summarize away detail." But if there's conflicting info, we should present both? The posting includes both. The top is in the description, the bottom is a field. I'll include the range and note the discrepancy? But the rule says preserve all substantive information. I'll include the pay range from the description and also mention the hourly rate from the metadata? But that might be confusing. Perhaps the $11.41 is the minimum wage? Actually, the top says "Starting Pay - $20.40 to $29.98". That's likely the actual pay. The later "Compensation: $11.41 / Hourly" might be a default field. I'll include the range and note "Starting pay range: $20.40 to $29.98 per hour based on experience. Offers for external candidates are generally made between the minimum and midpoint of the range." And maybe add a note: "Note: The posting also lists a compensation of $11.41/hourly, which may be a minimum or error." But that's editorializing. Better to just include the range from the description as it's part of the job duties description. The metadata compensation field might be for a different position? But it's in the same posting. I'll include both in the Pay section: "Starting pay range: $20.40 to $29.98 per hour based on experience. Offers for external candidates are generally made between the minimum and midpoint of the range. The posting also indicates a compensation of $11.41/hourly." That preserves both.
6. Schedule: Shift is First (Day), 0.6 FTE, Part Time. So a Schedule section.
7. Requirements: Could include education, experience, certifications (BLS), physical, drug test. But Qualifications already includes some. The metadata has Minimum Education Required, Minimum Experience Required, Physical Required, Drug Test Required, BLS certification. I can combine into a Requirements section with a list.
But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Requirements and Qualifications are separate? The posting has "Qualifications" and then metadata for education/experience. I'll create a "Requirements" section that includes education, experience, certifications, physical, drug test. And "Qualifications" for the skills/knowledge list. But that might be overlapping. The posting's "Qualifications" section lists: Prior computer experience required, Knowledge of medical terminology preferred, General knowledge of Accounts Receivable preferred, BLS certification. That's qualifications. The metadata has Minimum Education Required: High School Diploma or Equivalent; Minimum Experience Required: None. So I can create a "Requirements" section with education, experience, and other requirements (physical, drug test, BLS). And a "Qualifications" section for the skills/knowledge. But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine into one "Requirements & Qualifications" section? But the example headings include both Requirements and Qualifications. I'll keep them separate if both have content.
Let's see: Qualifications has 4 bullet points. Requirements (education, experience, physical, drug test) are also substantive. I'll create two sections: "Qualifications" for the skills/knowledge, and "Requirements" for education, experience, certifications, physical, drug test.
But BLS certification appears in both? In Qualifications it's listed as "BLS certification". In metadata, not explicitly but it's a qualification. I'll include BLS in Requirements as a certification.
Now, other metadata: Number of Openings: 1, Public Transportation Accessible: Yes, Veterans Encouraged to Apply: No, Postal Code: 55904, Requisition ID: PATIE003905. These are minor metadata. I'll fold them into a short paragraph in About the role or a separate "Details" paragraph. The rule says "fold minor metadata into a short
or drop it." I'll include a paragraph at the end of About the role or a separate "Position Details" section? But the rule says only include section if real content. A paragraph is not a section heading. I can just put a
after the About the role heading. Also, the EEO boilerplate should be removed. Now, let's structure the HTML. I'll start with