Cert. Medical Assistant-UMCEPH Pain and Spine Center
` for section headings: 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.
3. **Map Input Content to Output Structure:**
Let's parse the input:
- "Summary Job Summary Works under the direction of Licensed Healthcare Professionals. Schedules appointments, maintains medical records information for insurance purposes. Takes and records vital signs, prepares patients for examination, draws blood, and administers medications. Enters medical and social histories and performs intakes and discharges on all patients to assist healthcare providers."
→ This is the "About the role" or job summary content. I'll use it under an appropriate heading. The rules say use `
` for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to decide which heading fits. The summary describes the role's purpose and duties, so "About the role" seems fitting, or maybe "Responsibilities". I'll check the exact wording: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I think I can use "About the role" for the summary, or combine. Let's see.
- "Work Experience One year of Medical Assistant experience preferred."
→ This is a requirement/qualification. Goes under "Requirements" or "Qualifications". The rules have both "Requirements" and "Qualifications" as possible headings. I'll need to distinguish. Typically, "Requirements" might be mandatory, "Qualifications" preferred/desired. But the rule says include a section ONLY when the posting has real, specific content. I'll put this under "Requirements" or maybe "Qualifications". Let's see the input: "License/Registration/Certification Certified Medical Assistant Certificate required. Current BLS training required." → These are requirements. "Education and Training High School Education or equivalent. Completion of a Medical Assistant course required." → Also requirements/qualifications. "Skills Knowledge of ICD10, CPT4 and HCPCS coding... Highly effective communication skills. CRT proficiency and ability to type. Knows vaccine requirements... Bilingual English/Spanish preferred THS/ CHIP EMR" → Skills.
- Structure mapping:
- "About the role": The job summary paragraph.
- "Responsibilities": Could include the duties from the summary, but the summary already blends role and duties. I might put the detailed duties under "Responsibilities" or merge into "About the role". The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll use headings that match content present.
- "Requirements": License/certification, education, experience, BLS.
- "Qualifications": Might overlap. I'll see. The input has "One year of Medical Assistant experience preferred." → This is preferred, so maybe "Qualifications". But I could also put it under "Requirements". I need to be careful not to create thin sections. I'll group logically.
- "Skills": The skills section.
- No "Benefits", "Pay", "Schedule" since not present.
Let's re-read the input carefully:
Summary Job Summary Works under the direction of Licensed Healthcare Professionals. Schedules appointments, maintains medical records information for insurance purposes. Takes and records vital signs, prepares patients for examination, draws blood, and administers medications. Enters medical and social histories and performs intakes and discharges on all patients to assist healthcare providers.
Work Experience One year of Medical Assistant experience preferred.
License/Registration/Certification Certified Medical Assistant Certificate required. Current BLS training required.
Education and Training High School Education or equivalent. Completion of a Medical Assistant course required.
Skills Knowledge of ICD10, CPT4 and HCPCS coding related to clinic procedures and physician billing. Highly effective communication skills. CRT proficiency and ability to type. Knows vaccine requirements for patients, newborns through adulthood for assigned areas. Knowledge of the patient flow process, applicable per clinic. Bilingual English/Spanish preferred THS/ CHIP EMR
I need to extract all substantive info and map to headings. The headings available: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's decide:
- "About the role": The first paragraph describing what the job is, works under direction, schedules appointments, maintains records, takes vitals, prepares patients, draws blood, administers medications, enters histories, intakes/discharges. This is a good fit for "About the role" or "Responsibilities". I'll use "About the role" for the summary paragraph, as it describes the role's purpose and core activities.
- "Responsibilities": Could be separate, but the summary already covers duties. To avoid thin sections, I might either include duties in "About the role" or use "Responsibilities" for the same. The rule says "Prefer a few substantive sections over many thin ones." I'll combine role description and duties under "About the role", or use "Responsibilities" if there's distinct content. Looking at the input, there's no separate "Responsibilities" section beyond the summary. I'll put the summary under "About the role".
- "Requirements": License/Registration/Certification (Certified Medical Assistant Certificate required, Current BLS training required), Education and Training (High School Education or equivalent, Completion of a Medical Assistant course required), Work Experience (One year of Medical Assistant experience preferred). I'll put experience preferred under "Requirements" or maybe "Qualifications". I'll see. The rule has "Requirements" and "Qualifications" as separate headings. Typically, requirements are mandatory, qualifications are preferred/desired. I'll put mandatory stuff under "Requirements", preferred under "Qualifications". But the rule says only include sections with real content. Both are real. I'll use "Requirements" for mandatory, and maybe "Qualifications" for preferred. However, I need to check if the posting distinguishes. It says "Work Experience One year of Medical Assistant experience preferred." "License/Registration/Certification Certified Medical Assistant Certificate required." "Education and Training High School Education or equivalent. Completion of a Medical Assistant course required." So I'll create "Requirements" with the mandatory items, and maybe "Qualifications" with the preferred one. But the rule says "include a section ONLY when the posting has real, specific content for it". Both have content. I'll structure: "Requirements" for mandatory cert/education/experience? Actually, experience is "preferred", so maybe not "Requirements". I'll put mandatory license/education under "Requirements", and preferred experience under "Qualifications". Or I could put all under "Requirements" but note preferred. Let's read the rule again: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists them as examples. I can use a subset. I'll use "Requirements" for mandatory stuff, "Qualifications" for preferred/desired. But to keep it simple and avoid thin sections, I might combine into one "Requirements" section, but the heading list includes both, suggesting I should use them appropriately. I'll check the exact input: "Work Experience One year of Medical Assistant experience preferred." It's a single line. I'll put it under "Qualifications" or "Requirements". I think "Qualifications" fits "preferred" better. But the rule says "never emit a heading followed by filler/placeholder text". So if I create "Qualifications", I must have specific content. I have specific content: "One year of Medical Assistant experience preferred." That's fine.
Let's map each input piece to a heading:
- Paragraph 1 (Summary): "About the role"
- Work Experience (preferred): Could go under "Qualifications" or "Requirements". I'll use "Qualifications" since it's preferred. But wait, the heading "Qualifications" might be expected to list qualifications. I'll put it there.
- License/Registration/Certification (required): "Requirements"
- Education and Training (required): "Requirements" (could be separate, but I'll group under Requirements)
- Skills: "Skills"
However, the rule says: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I must use all, or in a specific order. I'll use the ones that have content.
Let's re-evaluate: The input has these categories: Job Summary, Work Experience, License/Registration/Certification, Education and Training, Skills. I need to map these to the allowed headings. I'll decide:
- "About the role" → Job Summary paragraph
- "Requirements" → License/Registration/Certification and Education and Training (since they are requirements)
- "Qualifications" → Work Experience (preferred) - but maybe I should include it in Requirements? The rule has both, I'll use both if content justifies. But "Work Experience One year of Medical Assistant experience preferred." is a single line. I'll put it under "Qualifications".
- "Skills" → Skills section
Wait, the rule says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Not relevant here.
"Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The input doesn't seem to have those, except maybe "Summary Job Summary" is a label. I'll ignore the "Summary" prefix, just use the content.
"Preserve ALL substantive information; do NOT invent or summarize away detail." I need to include all the text verbatim or nearly so, but formatted.
"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." So I won't create those.
"Prefer a few substantive sections over many thin ones." I'll combine where sensible.
Let
` 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. 3. **Map Input Content to Output Structure:** Let's parse the input: - "Summary Job Summary Works under the direction of Licensed Healthcare Professionals. Schedules appointments, maintains medical records information for insurance purposes. Takes and records vital signs, prepares patients for examination, draws blood, and administers medications. Enters medical and social histories and performs intakes and discharges on all patients to assist healthcare providers." → This is the "About the role" or job summary content. I'll use it under an appropriate heading. The rules say use `
` for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to decide which heading fits. The summary describes the role's purpose and duties, so "About the role" seems fitting, or maybe "Responsibilities". I'll check the exact wording: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I think I can use "About the role" for the summary, or combine. Let's see.
- "Work Experience One year of Medical Assistant experience preferred."
→ This is a requirement/qualification. Goes under "Requirements" or "Qualifications". The rules have both "Requirements" and "Qualifications" as possible headings. I'll need to distinguish. Typically, "Requirements" might be mandatory, "Qualifications" preferred/desired. But the rule says include a section ONLY when the posting has real, specific content. I'll put this under "Requirements" or maybe "Qualifications". Let's see the input: "License/Registration/Certification Certified Medical Assistant Certificate required. Current BLS training required." → These are requirements. "Education and Training High School Education or equivalent. Completion of a Medical Assistant course required." → Also requirements/qualifications. "Skills Knowledge of ICD10, CPT4 and HCPCS coding... Highly effective communication skills. CRT proficiency and ability to type. Knows vaccine requirements... Bilingual English/Spanish preferred THS/ CHIP EMR" → Skills.
- Structure mapping:
- "About the role": The job summary paragraph.
- "Responsibilities": Could include the duties from the summary, but the summary already blends role and duties. I might put the detailed duties under "Responsibilities" or merge into "About the role". The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll use headings that match content present.
- "Requirements": License/certification, education, experience, BLS.
- "Qualifications": Might overlap. I'll see. The input has "One year of Medical Assistant experience preferred." → This is preferred, so maybe "Qualifications". But I could also put it under "Requirements". I need to be careful not to create thin sections. I'll group logically.
- "Skills": The skills section.
- No "Benefits", "Pay", "Schedule" since not present.
Let's re-read the input carefully:
Summary Job Summary Works under the direction of Licensed Healthcare Professionals. Schedules appointments, maintains medical records information for insurance purposes. Takes and records vital signs, prepares patients for examination, draws blood, and administers medications. Enters medical and social histories and performs intakes and discharges on all patients to assist healthcare providers.
Work Experience One year of Medical Assistant experience preferred.
License/Registration/Certification Certified Medical Assistant Certificate required. Current BLS training required.
Education and Training High School Education or equivalent. Completion of a Medical Assistant course required.
Skills Knowledge of ICD10, CPT4 and HCPCS coding related to clinic procedures and physician billing. Highly effective communication skills. CRT proficiency and ability to type. Knows vaccine requirements for patients, newborns through adulthood for assigned areas. Knowledge of the patient flow process, applicable per clinic. Bilingual English/Spanish preferred THS/ CHIP EMR
I need to extract all substantive info and map to headings. The headings available: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's decide:
- "About the role": The first paragraph describing what the job is, works under direction, schedules appointments, maintains records, takes vitals, prepares patients, draws blood, administers medications, enters histories, intakes/discharges. This is a good fit for "About the role" or "Responsibilities". I'll use "About the role" for the summary paragraph, as it describes the role's purpose and core activities.
- "Responsibilities": Could be separate, but the summary already covers duties. To avoid thin sections, I might either include duties in "About the role" or use "Responsibilities" for the same. The rule says "Prefer a few substantive sections over many thin ones." I'll combine role description and duties under "About the role", or use "Responsibilities" if there's distinct content. Looking at the input, there's no separate "Responsibilities" section beyond the summary. I'll put the summary under "About the role".
- "Requirements": License/Registration/Certification (Certified Medical Assistant Certificate required, Current BLS training required), Education and Training (High School Education or equivalent, Completion of a Medical Assistant course required), Work Experience (One year of Medical Assistant experience preferred). I'll put experience preferred under "Requirements" or maybe "Qualifications". I'll see. The rule has "Requirements" and "Qualifications" as separate headings. Typically, requirements are mandatory, qualifications are preferred/desired. I'll put mandatory stuff under "Requirements", preferred under "Qualifications". But the rule says only include sections with real content. Both are real. I'll use "Requirements" for mandatory, and maybe "Qualifications" for preferred. However, I need to check if the posting distinguishes. It says "Work Experience One year of Medical Assistant experience preferred." "License/Registration/Certification Certified Medical Assistant Certificate required." "Education and Training High School Education or equivalent. Completion of a Medical Assistant course required." So I'll create "Requirements" with the mandatory items, and maybe "Qualifications" with the preferred one. But the rule says "include a section ONLY when the posting has real, specific content for it". Both have content. I'll structure: "Requirements" for mandatory cert/education/experience? Actually, experience is "preferred", so maybe not "Requirements". I'll put mandatory license/education under "Requirements", and preferred experience under "Qualifications". Or I could put all under "Requirements" but note preferred. Let's read the rule again: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists them as examples. I can use a subset. I'll use "Requirements" for mandatory stuff, "Qualifications" for preferred/desired. But to keep it simple and avoid thin sections, I might combine into one "Requirements" section, but the heading list includes both, suggesting I should use them appropriately. I'll check the exact input: "Work Experience One year of Medical Assistant experience preferred." It's a single line. I'll put it under "Qualifications" or "Requirements". I think "Qualifications" fits "preferred" better. But the rule says "never emit a heading followed by filler/placeholder text". So if I create "Qualifications", I must have specific content. I have specific content: "One year of Medical Assistant experience preferred." That's fine.
Let's map each input piece to a heading:
- Paragraph 1 (Summary): "About the role"
- Work Experience (preferred): Could go under "Qualifications" or "Requirements". I'll use "Qualifications" since it's preferred. But wait, the heading "Qualifications" might be expected to list qualifications. I'll put it there.
- License/Registration/Certification (required): "Requirements"
- Education and Training (required): "Requirements" (could be separate, but I'll group under Requirements)
- Skills: "Skills"
However, the rule says: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I must use all, or in a specific order. I'll use the ones that have content.
Let's re-evaluate: The input has these categories: Job Summary, Work Experience, License/Registration/Certification, Education and Training, Skills. I need to map these to the allowed headings. I'll decide:
- "About the role" → Job Summary paragraph
- "Requirements" → License/Registration/Certification and Education and Training (since they are requirements)
- "Qualifications" → Work Experience (preferred) - but maybe I should include it in Requirements? The rule has both, I'll use both if content justifies. But "Work Experience One year of Medical Assistant experience preferred." is a single line. I'll put it under "Qualifications".
- "Skills" → Skills section
Wait, the rule says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists them as examples. I can use a subset. I'll use "Requirements" for mandatory stuff, "Qualifications" for preferred/desired. But to keep it simple and avoid thin sections, I might combine into one "Requirements" section, but the heading list includes both, suggesting I should use them appropriately. I'll check the exact input: "Work Experience One year of Medical Assistant experience preferred." It's a single line. I'll put it under "Qualifications" or "Requirements". I think "Qualifications" fits "preferred" better. But the rule says "never emit a heading followed by filler/placeholder text". So if I create "Qualifications", I must have specific content. I have specific content: "One year of Medical Assistant experience preferred." That's fine.
Let's map each input piece to a heading:
- Paragraph 1 (Summary): "About the role"
- Work Experience (preferred): Could go under "Qualifications" or "Requirements". I'll use "Qualifications" since it's preferred. But wait, the heading "Qualifications" might be expected to list qualifications. I'll put it there.
- License/Registration/Certification (required): "Requirements"
- Education and Training (required): "Requirements" (could be separate, but I'll group under Requirements)
- Skills: "Skills"
However, the rule says: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I must use all, or in a specific order. I'll use the ones that have content.
Let's re-evaluate: The input has these categories: Job Summary, Work Experience, License/Registration/Certification, Education and Training, Skills. I need to map these to the allowed headings. I'll decide:
- "About the role" → Job Summary paragraph
- "Requirements" → License/Registration/Certification and Education and Training (since they are requirements)
- "Qualifications" → Work Experience (preferred) - but maybe I should include it in Requirements? The rule has both, I'll use both if content justifies. But "Work Experience One year of Medical Assistant experience preferred." is a single line. I'll put it under "Qualifications".
- "Skills" → Skills section
Wait, the rule says: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Not relevant here. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The input doesn't seem to have those, except maybe "Summary Job Summary" is a label. I'll ignore the "Summary" prefix, just use the content. "Preserve ALL substantive information; do NOT invent or summarize away detail." I need to include all the text verbatim or nearly so, but formatted. "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." So I won't create those. "Prefer a few substantive sections over many thin ones." I'll combine where sensible. Let