A Locums Electrophysiologist Is Needed in OR
Weatherby Healthcare · Springfield, OR · 1 mo ago
On-siteHealthcareFull-time
We need to extract substantive content, format as HTML with headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if there is real content. Remove boilerplate like "Interested? Give Weatherby a call..." etc. Also remove navigation, legal, EEO, etc. The posting includes:
- "Interested? Give Weatherby a call today and speak with one of our specialty-specific consultants for available dates and details." (application instruction, remove)
- "M-F 8am-5pm, 2-3 weeks per month ongoing" (schedule? maybe schedule)
- "Mon-Tue clinic 14-16 patients per day"
- "Wed-Thu EP lab 2-5 cases per day"
- "Inpatient and outpatient setting"
- "Pacemakers, ICDs, primary focus ablations A-fib"
- "ACLS certification required."
- "Paid malpractice insurance; pre-paid travel and housing expenses"
- "Assignment details and time entry in online portal"
- "Competitive compensation"
- "24-hour access to your Weatherby Healthcare consultant"
- "Charter member of NALTO"
- Then a paragraph about Weatherby Healthcare: "Since 1995, Weatherby Healthcare has established itself as an expert in locum tenens staffing for physicians, physician assistants, and nurse practitioners. The company employs nearly 600 employees committed to filling locum tenens assignments in large-scale healthcare networks, hospitals, and clinics nationwide. Learn more at http://weatherbyhealthcare.com"
We need to preserve all substantive info, but remove boilerplate like "Learn more at ..."? That's maybe okay as it's part of description but could be considered navigation? It's a link; maybe we keep as part of About the role? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more at ..." is not exactly boilerplate but could be considered navigation? It's a link to the company site; maybe we keep as part of About the role? However it's not essential job detail; but it's about the company. Might be okay to keep as part of About the role.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
Content:
- Schedule: "M-F 8am-5pm, 2-3 weeks per month ongoing" (that's schedule). Also maybe "Mon-Tue clinic 14-16 patients per day" and "Wed-Thu EP lab 2-5 cases per day" are responsibilities/duties.
- Responsibilities: clinic patient volume, EP lab cases, inpatient/outpatient setting, pacemakers, ICDs, primary focus ablations A-fib.
- Requirements: ACLS certification required.
- Qualifications: maybe none explicit besides ACLS? Could be implied: specialty-specific consultants? Not sure.
- Skills: maybe none.
- Benefits: Paid malpractice insurance; pre-paid travel and housing expenses; 24-hour access to your Weatherby Healthcare consultant; Assignment details and time entry in online portal; Competitive compensation (maybe Pay). Also Charter member of NALTO maybe a benefit? Could be under Benefits.
- Pay: "Competitive compensation" is vague; but we should not create Pay section if content is vague like "competitive compensation" (not specific). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation". That's a statement but it's vague; is that considered stating? It says "Competitive compensation". It's not a number but it's stating compensation exists. The instruction says: 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. "Competitive compensation" is not filler like those examples; it's a statement. Might be acceptable to include Pay section with that line. However they said prefer a few substantive sections over many thin ones. Could combine Pay into Benefits? But we have separate headings.
We could make Benefits section include: Paid malpractice insurance; pre-paid travel and housing expenses; 24-hour access to your Weatherby Healthcare consultant; Assignment details and time entry in online portal; Competitive compensation; Charter member of NALTO.
Schedule section: M-F 8am-5pm, 2-3 weeks per month ongoing.
Responsibilities: Mon-Tue clinic 14-16 patients per day; Wed-Thu EP lab 2-5 cases per day; Inpatient and outpatient setting; Pacemakers, ICDs, primary focus ablations A-fib.
Requirements: ACLS certification required.
About the role: maybe the paragraph about Weatherby Healthcare? Or we could have About the role describing the role: It's a locum tenens assignment for EP? Actually the role is likely an Electrophysiology (EP) physician? The posting mentions EP lab, pacemakers, ICDs, ablations A-fib. So About the role could be a brief description: Locum tenens EP position providing inpatient/outpatient care, clinic and EP lab duties. But we must not invent or summarize away detail. We can rephrase but must preserve all substantive info. We could create About the role using the given details: The role involves clinic (Mon-Tue) seeing 14-16 patients per day, EP lab (Wed-Thu) performing 2-5 cases per day, inpatient and outpatient setting, focusing on pacemakers, ICDs, and primary focus ablations for atrial fibrillation. ACLS certification required. That's basically responsibilities and requirements. Might be redundant.
Better: Use About the role for a general description: Locum tenens assignment for an Electrophysiology physician providing clinic and EP lab services, inpatient/outpatient, focusing on device implants and ablations. Then Responsibilities list specifics. But we must not invent details not in posting. The posting does not explicitly say "Electrophysiology physician" but implied by EP lab, pacemakers, ICDs, ablations. It's safe to infer? Might be considered inventing. Safer to not create About the role if we would be inventing. Instead we could put the company description under About the role? That's not about the role. The instruction: Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if there is real content. Remove boilerplate like "Interested? Give Weatherby a call..." etc. Also remove navigation, legal, EEO, etc. The posting includes:
- "Interested? Give Weatherby a call today and speak with one of our specialty-specific consultants for available dates and details." (application instruction, remove)
- "M-F 8am-5pm, 2-3 weeks per month ongoing" (schedule? maybe schedule)
- "Mon-Tue clinic 14-16 patients per day"
- "Wed-Thu EP lab 2-5 cases per day"
- "Inpatient and outpatient setting"
- "Pacemakers, ICDs, primary focus ablations A-fib"
- "ACLS certification required."
- "Paid malpractice insurance; pre-paid travel and housing expenses"
- "Assignment details and time entry in online portal"
- "Competitive compensation"
- "24-hour access to your Weatherby Healthcare consultant"
- "Charter member of NALTO"
- Then a paragraph about Weatherby Healthcare: "Since 1995, Weatherby Healthcare has established itself as an expert in locum tenens staffing for physicians, physician assistants, and nurse practitioners. The company employs nearly 600 employees committed to filling locum tenens assignments in large-scale healthcare networks, hospitals, and clinics nationwide. Learn more at http://weatherbyhealthcare.com"
We need to preserve all substantive info, but remove boilerplate like "Learn more at ..."? That's maybe okay as it's part of description but could be considered navigation? It's a link; maybe we keep as part of About the role? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more at ..." is not exactly boilerplate but could be considered navigation? It's a link to the company site; maybe we keep as part of About the role? However it's not essential job detail; but it's about the company. Might be okay to keep as part of About the role.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
Content:
- Schedule: "M-F 8am-5pm, 2-3 weeks per month ongoing" (that's schedule). Also maybe "Mon-Tue clinic 14-16 patients per day" and "Wed-Thu EP lab 2-5 cases per day" are responsibilities/duties.
- Responsibilities: clinic patient volume, EP lab cases, inpatient/outpatient setting, pacemakers, ICDs, primary focus ablations A-fib.
- Requirements: ACLS certification required.
- Qualifications: maybe none explicit besides ACLS? Could be implied: specialty-specific consultants? Not sure.
- Skills: maybe none.
- Benefits: Paid malpractice insurance; pre-paid travel and housing expenses; 24-hour access to your Weatherby Healthcare consultant; Assignment details and time entry in online portal; Competitive compensation (maybe Pay). Also Charter member of NALTO maybe a benefit? Could be under Benefits.
- Pay: "Competitive compensation" is vague; but we should not create Pay section if content is vague like "competitive compensation" (not specific). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation". That's a statement but it's vague; is that considered stating? It says "Competitive compensation". It's not a number but it's stating compensation exists. The instruction says: 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. "Competitive compensation" is not filler like those examples; it's a statement. Might be acceptable to include Pay section with that line. However they said prefer a few substantive sections over many thin ones. Could combine Pay into Benefits? But we have separate headings.
We could make Benefits section include: Paid malpractice insurance; pre-paid travel and housing expenses; 24-hour access to your Weatherby Healthcare consultant; Assignment details and time entry in online portal; Competitive compensation; Charter member of NALTO.
Schedule section: M-F 8am-5pm, 2-3 weeks per month ongoing.
Responsibilities: Mon-Tue clinic 14-16 patients per day; Wed-Thu EP lab 2-5 cases per day; Inpatient and outpatient setting; Pacemakers, ICDs, primary focus ablations A-fib.
Requirements: ACLS certification required.
About the role: maybe the paragraph about Weatherby Healthcare? Or we could have About the role describing the role: It's a locum tenens assignment for EP? Actually the role is likely an Electrophysiology (EP) physician? The posting mentions EP lab, pacemakers, ICDs, ablations A-fib. So About the role could be a brief description: Locum tenens EP position providing inpatient/outpatient care, clinic and EP lab duties. But we must not invent or summarize away detail. We can rephrase but must preserve all substantive info. We could create About the role using the given details: The role involves clinic (Mon-Tue) seeing 14-16 patients per day, EP lab (Wed-Thu) performing 2-5 cases per day, inpatient and outpatient setting, focusing on pacemakers, ICDs, and primary focus ablations for atrial fibrillation. ACLS certification required. That's basically responsibilities and requirements. Might be redundant.
Better: Use About the role for a general description: Locum tenens assignment for an Electrophysiology physician providing clinic and EP lab services, inpatient/outpatient, focusing on device implants and ablations. Then Responsibilities list specifics. But we must not invent details not in posting. The posting does not explicitly say "Electrophysiology physician" but implied by EP lab, pacemakers, ICDs, ablations. It's safe to infer? Might be considered inventing. Safer to not create About the role if we would be inventing. Instead we could put the company description under About the role? That's not about the role. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We could include About the role with the company description? That seems off.
Maybe we can treat the paragraph about Weatherby Healthcare as About the role? Actually it's about the company, not the role. But we could still put it under About the role as a description of the employer. Might be acceptable.
Alternatively, we could omit About the role and just have Responsibilities, Requirements, Benefits, Schedule. The instruction: Prefer a few substantive sections over many thin ones. So we could have Responsibilities, Requirements, Benefits, Schedule. That's four sections.
Let's extract:
Responsibilities:
- Mon-Tue clinic: 14-16 patients per day
- Wed-Thu EP lab: 2-5 cases per day
- Inpatient and outpatient setting
- Pacemakers, ICDs, primary focus ablations A-fib
Requirements:
- ACLS certification required
Benefits:
- Paid malpractice insurance
- Pre-paid travel and housing expenses
- 24-hour access to your Weatherby Healthcare consultant
- Assignment details and time entry in online portal
- Competitive compensation
- Charter member of NALTO (maybe not a benefit but we can include)
Schedule:
- M-F 8am-5pm, 2-3 weeks per month ongoing
We should not repeat the job title as heading. No job title given.
We need to output only HTML fragment, no /. Use for each section heading, then content: either
for each section heading, then content: either
for prose or
- for lists.
We need to decide which content is prose vs list. For responsibilities, requirements, benefits, schedule we can use lists.
Schedule: maybe a single line; could be
but list also fine. Let's craft:
Responsibilities
- Mon-Tue clinic: 14-16 patients per day
- Wed-Thu EP lab: 2-5 cases per day
- Inpatient and outpatient setting
- Pacemakers, ICDs, primary focus ablations A-fib
Requirements
- ACLS certification required
Benefits
- Paid malpractice insurance
- Pre-paid travel and housing expenses
- 24-hour access to your Weatherby Healthcare consultant
- Assignment details and time entry in online portal
- Competitive compensation
- Charter member of NALTO
Schedule
M-F 8am-5pm, 2-3 weeks per month ongoing
We should also include maybe About the role? Not needed. Check for any leftover boilerplate: We removed "Interested? Give Weatherby a call today..." etc. Also removed "Learn more at http://weatherbyhealthcare.com". That's part of company description; we omitted it. Is that substantive? It's a link to learn more; maybe not essential. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more at..." is not exactly those but could be considered navigation? It's a link to the company site; might be considered navigation. Safer to remove. We also removed the "Charter member of NALTO" from the company description? Actually we kept it as benefit. It's in the posting after the paragraph: "Charter member of NALTO". That's a statement about the company; we kept as benefit. Now ensure we didn't miss any substantive info: "Since 1995, Weatherby Healthcare has established itself as an expert in locum tenens staffing for physicians, physician assistants, and nurse practitioners. The company employs nearly 600 employees committed to filling locum tenens assignments in large-scale healthcare networks, hospitals, and clinics nationwide." That's company info; we omitted. Is that substantive? It's about the company, not the role. The instruction says preserve ALL substantive information; does that include company description? Probably yes, as it's part of the posting. However we might consider it boilerplate? It's not navigation/legal/EEO; it's descriptive. Could be considered substantive. Should we include it? We could put it under About the role or maybe a separate section like About the company. But we only have allowed headings list; we could use About the role for this company description. That would be appropriate: About the role could include description of the employer. The instruction: Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with that company description. Thus we add:
About the role
Since 1995, Weatherby Healthcare has established itself as an expert in locum tenens staffing for physicians, physician assistants, and nurse practitioners. The company employs nearly 600 employees committed to filling locum tenens assignments in large-scale healthcare networks, hospitals, and clinics nationwide.
We should not include the "Learn more at..." link. Now check for any other content: "Assignment details and time entry in online