LPN/Medical Assistant/EMT
HealthPartners · Woodbury, MN · 1 mo ago
HealthcareFull-time
We need to output HTML fragment with sections: headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real specific content. The posting includes: About Us (maybe "About the role"? Actually "About Us" is about organization, not role. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have job description: HealthPartners hiring for full-time LPN/Medical Assistant/EMT at Woodbury clinic Primary Care. Sign on bonus eligible. Then required qualifications for LPN position, then required qualifications for Medical Assistant/EMT position. Then responsibilities for LPN position, then responsibilities for Medical Assistant/EMT position. Then a paragraph about physical requirements. Then "About Us" paragraph. Then "Benefits Designed To Support Your Total Health". Then EEO statement (should be removed as boilerplate). Also mention sign on bonus eligible (maybe under Benefits? It's a bonus, could be part of Benefits or maybe a separate note). Since Benefits section should be included only if posting actually states them. It does: "Benefits Designed To Support Your Total Health" with description. So we include Benefits heading.
Pay: not mentioned besides sign on bonus eligible (maybe mention sign-on bonus). No explicit pay rate. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does not state pay amount or schedule. It mentions full-time, but not schedule details. Should we include Schedule? It says full-time, but not specific schedule. Might be considered schedule info? It says full-time, but not specific hours. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time (schedule type). Could be considered schedule content. However they said "full-time" is schedule info. Might be okay to include Schedule section with that detail. But they also said prefer a few substantive sections over many thin ones. Might combine schedule into About the role? But we have headings list; we could include Schedule with "Full-time". However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state full-time, so we can include Schedule. But we need to see if they want schedule details like shift, hours. Since only full-time is given, we could include that.
Pay: they mention sign-on bonus eligible, which is a form of pay. Could be considered Pay section content: "Sign-on bonus eligible". Might be appropriate to include Pay heading with that detail. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state sign-on bonus eligible, which is a pay-related detail. So we could include Pay section with that.
But we need to avoid filler like "commensurate with experience". Sign-on bonus eligible is specific enough.
Thus we could have sections: About the role (maybe summarizing the job title, location, department, full-time, sign-on bonus). Responsibilities (LPN and MA/EMT). Requirements (maybe combine qualifications). Qualifications (maybe separate? Actually they have Required Qualifications for LPN and for MA/EMT. Could combine under Requirements or Qualifications. The instruction list includes both Requirements and Qualifications as possible headings. We need to decide which to use. Since they have qualifications, we could use Qualifications heading. Or we could use Requirements. Probably better to use Qualifications for the licensure/education requirements, and maybe Skills for communication skills etc. But they also have skills like communication, manual dexterity, etc. Could put those under Skills.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include all qualification details, responsibilities, physical requirements, about us, benefits, sign-on bonus.
We must not repeat job title as heading. So no
? Not allowed? Only headings allowed are h3 for section headings. Could use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings only. So we can have Qualifications heading and inside we can have paragraphs distinguishing LPN and MA/EMT.
Similarly Responsibilities heading with paragraphs for LPN and MA/EMT.
Skills heading: maybe include communication skills, manual dexterity, English proficiency, etc. But those are already in qualifications or responsibilities. Could combine.
Better to have sections: About the role, Responsibilities, Qualifications, Benefits, Schedule, Pay. That covers.
We need to ensure we don't create empty sections.
Let's extract content:
About the role: "HealthPartners is hiring for a full-time LPN/Medical Assistant/EMT working at the Woodbury clinic in the Primary Care department. ***SIGN ON BONUS ELIGIBLE***"
Thus About the role paragraph: full-time position at Woodbury clinic Primary Care department, sign-on bonus eligible.
Responsibilities: Need to include both LPN and MA/EMT responsibilities as listed.
Qualifications: LPN qualifications and MA/EMT qualifications.
Skills: Could include "Demonstrated verbal and written communication skills including appropriate use of English grammar and spelling." Also "Must possess speech, hearing, and sight skills to perform the functions of the position. Manual dexterity required. Must be able to speak, read and write English proficiently. Proficiency in other languages may be required." Also maybe "Maintain CPR certification." But that's more qualification.
But we could put communication skills under Qualifications as they are listed there. Might be okay to not have Skills section if it's thin. The instruction: prefer a few substantive sections over many thin ones. So maybe we skip Skills and include those details within Qualifications or Responsibilities.
Benefits: The Benefits Described To Support Your Total Health paragraph.
Schedule: full-time (maybe mention full-time). Could also mention that it's full-time.
Pay: sign-on bonus eligible.
We need to ensure we don't include boilerplate: remove EEO statement, navigation, legal, etc. Also remove "About Us" maybe? It's not a required heading but could be considered "About the role"? Actually About Us is about organization, not role. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). About Us is not in list, but we could incorporate that info into About the role or maybe omit as boilerplate? It's not boilerplate; it's substantive about the organization. Could be placed under About the role? But About the role is about the job, not the organization. However we could add another heading like "About HealthPartners" but not in list. The instruction says use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real specific content. The posting includes: About Us (maybe "About the role"? Actually "About Us" is about organization, not role. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have job description: HealthPartners hiring for full-time LPN/Medical Assistant/EMT at Woodbury clinic Primary Care. Sign on bonus eligible. Then required qualifications for LPN position, then required qualifications for Medical Assistant/EMT position. Then responsibilities for LPN position, then responsibilities for Medical Assistant/EMT position. Then a paragraph about physical requirements. Then "About Us" paragraph. Then "Benefits Designed To Support Your Total Health". Then EEO statement (should be removed as boilerplate). Also mention sign on bonus eligible (maybe under Benefits? It's a bonus, could be part of Benefits or maybe a separate note). Since Benefits section should be included only if posting actually states them. It does: "Benefits Designed To Support Your Total Health" with description. So we include Benefits heading.
Pay: not mentioned besides sign on bonus eligible (maybe mention sign-on bonus). No explicit pay rate. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does not state pay amount or schedule. It mentions full-time, but not schedule details. Should we include Schedule? It says full-time, but not specific schedule. Might be considered schedule info? It says full-time, but not specific hours. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time (schedule type). Could be considered schedule content. However they said "full-time" is schedule info. Might be okay to include Schedule section with that detail. But they also said prefer a few substantive sections over many thin ones. Might combine schedule into About the role? But we have headings list; we could include Schedule with "Full-time". However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state full-time, so we can include Schedule. But we need to see if they want schedule details like shift, hours. Since only full-time is given, we could include that.
Pay: they mention sign-on bonus eligible, which is a form of pay. Could be considered Pay section content: "Sign-on bonus eligible". Might be appropriate to include Pay heading with that detail. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state sign-on bonus eligible, which is a pay-related detail. So we could include Pay section with that.
But we need to avoid filler like "commensurate with experience". Sign-on bonus eligible is specific enough.
Thus we could have sections: About the role (maybe summarizing the job title, location, department, full-time, sign-on bonus). Responsibilities (LPN and MA/EMT). Requirements (maybe combine qualifications). Qualifications (maybe separate? Actually they have Required Qualifications for LPN and for MA/EMT. Could combine under Requirements or Qualifications. The instruction list includes both Requirements and Qualifications as possible headings. We need to decide which to use. Since they have qualifications, we could use Qualifications heading. Or we could use Requirements. Probably better to use Qualifications for the licensure/education requirements, and maybe Skills for communication skills etc. But they also have skills like communication, manual dexterity, etc. Could put those under Skills.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include all qualification details, responsibilities, physical requirements, about us, benefits, sign-on bonus.
We must not repeat job title as heading. So no LPN/Medical Assistant/EMT
. We'll start with maybe About the role
containing info: full-time position at Woodbury clinic Primary Care department, sign-on bonus eligible.
Then Qualifications
containing LPN qualifications and MA/EMT qualifications. Could separate with LPN
? Not allowed? Only headings allowed are h3 for section headings. Could use LPN Qualifications
but that's still h3. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings only. So we can have Qualifications heading and inside we can have paragraphs distinguishing LPN and MA/EMT.
Similarly Responsibilities heading with paragraphs for LPN and MA/EMT.
Skills heading: maybe include communication skills, manual dexterity, English proficiency, etc. But those are already in qualifications or responsibilities. Could combine.
Better to have sections: About the role, Responsibilities, Qualifications, Benefits, Schedule, Pay. That covers.
We need to ensure we don't create empty sections.
Let's extract content:
About the role: "HealthPartners is hiring for a full-time LPN/Medical Assistant/EMT working at the Woodbury clinic in the Primary Care department. ***SIGN ON BONUS ELIGIBLE***"
Thus About the role paragraph: full-time position at Woodbury clinic Primary Care department, sign-on bonus eligible.
Responsibilities: Need to include both LPN and MA/EMT responsibilities as listed.
Qualifications: LPN qualifications and MA/EMT qualifications.
Skills: Could include "Demonstrated verbal and written communication skills including appropriate use of English grammar and spelling." Also "Must possess speech, hearing, and sight skills to perform the functions of the position. Manual dexterity required. Must be able to speak, read and write English proficiently. Proficiency in other languages may be required." Also maybe "Maintain CPR certification." But that's more qualification.
But we could put communication skills under Qualifications as they are listed there. Might be okay to not have Skills section if it's thin. The instruction: prefer a few substantive sections over many thin ones. So maybe we skip Skills and include those details within Qualifications or Responsibilities.
Benefits: The Benefits Described To Support Your Total Health paragraph.
Schedule: full-time (maybe mention full-time). Could also mention that it's full-time.
Pay: sign-on bonus eligible.
We need to ensure we don't include boilerplate: remove EEO statement, navigation, legal, etc. Also remove "About Us" maybe? It's not a required heading but could be considered "About the role"? Actually About Us is about organization, not role. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). About Us is not in list, but we could incorporate that info into About the role or maybe omit as boilerplate? It's not boilerplate; it's substantive about the organization. Could be placed under About the role? But About the role is about the job, not the organization. However we could add another heading like "About HealthPartners" but not in list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Could we add another heading like "About HealthPartners"? Possibly but they said use those examples; better to stick to those. So we could omit About Us or fold into About the role? Might be okay to include a brief paragraph about the organization under About the role? Might be stretching.
Better to include a section "About HealthPartners" as About HealthPartners
but not in examples. The instruction: "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 use other headings as long as they are . But to be safe, we could incorporate About Us into a section like "About the organization" but maybe not needed. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the About Us paragraph. So we need a heading for it. Could use About HealthPartners
. That seems reasonable.
Thus sections: About the role, About HealthPartners, Responsibilities, Qualifications, Benefits, Schedule, Pay.
Check if any content duplicated: The "Sign on bonus eligible" appears in About the role; we could also put under Pay. But we should not duplicate. We'll put it under Pay.
Now craft HTML.
We'll need About the role
About HealthPartners
but not in examples. The instruction: "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 use other headings as long as they are . But to be safe, we could incorporate About Us into a section like "About the organization" but maybe not needed. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the About Us paragraph. So we need a heading for it. Could use About HealthPartners
. That seems reasonable.
Thus sections: About the role, About HealthPartners, Responsibilities, Qualifications, Benefits, Schedule, Pay.
Check if any content duplicated: The "Sign on bonus eligible" appears in About the role; we could also put under Pay. But we should not duplicate. We'll put it under Pay.
Now craft HTML.
We'll need About the role
About HealthPartners
. That seems reasonable. Thus sections: About the role, About HealthPartners, Responsibilities, Qualifications, Benefits, Schedule, Pay. Check if any content duplicated: The "Sign on bonus eligible" appears in About the role; we could also put under Pay. But we should not duplicate. We'll put it under Pay. Now craft HTML. We'll needAbout the role
...
ThenAbout HealthPartners
...
ThenResponsibilities
... maybe we need to separate LPN and MA/EMT responsibilities within
- ? The responsibilities are long sentences; we could keep as
but they are lists of duties. Better to use
- for each duty. The instruction: Use
- for any list of duties/requirements/benefits. So we should convert each responsibility line into list items.
Thus under Responsibilities heading, we could have two subheadings? Not allowed? Could just have one list combining both sets, but we need to differentiate. Could have
LPN Position Responsibilities
but not h3. Might be okay to useas subheading? The instruction only mentions h3 for section headings; doesn't forbid other headings. Safer to use
for main sections and maybe or
to indicate subcategory. But we could also split into two separate sections: Responsibilities for LPN and Responsibilities for MA/EMT each as
Responsibilities
? That would duplicate heading name, not ideal. We could keep responsibilities as paragraphs () but the instruction says use
- for any list of duties/requirements/benefits. The responsibilities are a list of duties, so we should use list.
Thus we could do:
Responsibilities
- LPN: Identify common and recurring nursing needs of the patient....
- LPN: Recognize the need for and perform routine office procedures... ... etc for all LPN responsibilities.
- Medical Assistant/EMT: Room patients and complete vital signs... ... etc.
Qualifications
- LPN: Graduate of an accredited school of nursing.... etc. We need to ensure we preserve all details exactly as given, not summarizing. We must be careful to not lose any detail. Let's extract LPN qualifications: - Graduate of an accredited school of nursing. - Current LPN licensure in Minnesota. - Current BLS provider status in accordance with American Heart Association (AHA) guidelines. - On-line BLS certification is not acceptable. - Demonstrated verbal and written communication skills including appropriate use of English grammar and spelling. - One year working experience as an LPN is preferred. MA/EMT qualifications: - High school diploma or GED. - Graduated of an accredited Medical Assistant program OR Graduate of an accredited EMT program and current EMT License. - Current BLS provider status in accordance with American Heart Association (AHA) guidelines. - On-line BLS certification is not acceptable. - Demonstrated verbal and written communication skills, including appropriate use of English
- for any list of duties/requirements/benefits. The responsibilities are a list of duties, so we should use list.
Thus we could do:
- for any list of duties/requirements/benefits. So we should convert each responsibility line into list items.
Thus under Responsibilities heading, we could have two subheadings? Not allowed? Could just have one list combining both sets, but we need to differentiate. Could have
- for each duty. The instruction: Use