Travel Pharmacist - $2,347 per week
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
- Do NOT put Job ID as heading - fold into short
or drop
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
- Include section ONLY when posting has real, specific content - never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment - no html/body, no markdown code fences
Let me structure this:
The posting has:
1. Job details (start date, duration, hours, shift, employment type) - could be "About the role" or "Schedule" but schedule is specific: 10 hours nights, 40 hours/week, 23 weeks, ASAP start. That's substantive schedule info.
2. Requested skill set - this is requirements/qualifications
3. Advanced skills needed - more requirements
4. Procedures performed on unit - responsibilities
5. Certifications required - qualifications
6. About TalentBurst - company info, but the rule says remove boilerplate? The "About TalentBurst" is company description, not boilerplate like EEO. But it's not about the role. The user said "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Company description might be considered boilerplate? However, it's part of the posting. The instruction: "Preserve ALL substantive information". The company description is substantive about the employer. But the rule also says "Prefer a few substantive sections over many thin ones." I think I should include it as a section maybe "About the Company" but the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Company" is not in the list. The list says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It says "e.g." so maybe other headings allowed? But better to stick to those. Could fold company info into a short p at the end? Or maybe not include because it's not about the role. The user said "reformat a job posting into clean, well-structured semantic HTML". The company description is part of the posting. But the rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Company description is not that. However, the example headings don't include "About the Company". I could include it as a section with h3 "About the Company" but the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid others, but says "e.g." meaning examples. I think it's okay to add "About the Company" if there's content. But the instruction also says "include a section ONLY when the posting has real, specific content for it". The company description is real and specific. However, the user might expect only those standard sections. Let me see the pay package: "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is not specific pay amount, it says "to be determined". That's placeholder/filler. So I should NOT create a Pay section. Similarly, Benefits not mentioned. Schedule is specific: 10 hours nights, 40 hours/week, 23 weeks, ASAP start. That's substantive schedule info. So I can have a Schedule section.
Now, the requested skill set and advanced skills and procedures and certifications are all requirements/qualifications. I could combine into "Requirements" and "Responsibilities". Procedures performed on unit are responsibilities. Requested skill set and advanced skills are requirements/qualifications. Certifications are qualifications.
Let me create sections:
- About the role: could include the job details (specialty, discipline, start date, duration, employment type) and maybe the shift/hours? But schedule separate.
Better:
- About the role: prose describing the role: travel pharmacist in Richmond, Virginia, complex patients, trauma/burn/critical care, peds, cardiac surgery, ECMO. That's from the skill set.
- Schedule: specific schedule details.
- Responsibilities: procedures performed on unit.
- Requirements: requested skill set (experience, systems), advanced skills, certifications.
- Qualifications: maybe same as requirements? Could combine.
The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Skills could be a separate section for the skill set. But the skill set is more like requirements. I'll use Requirements for the must-haves, and maybe Skills for the requested skill set? But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Skills is an allowed heading. The "Requested Skill Set" could be a Skills section. However, the content includes "Will experience complex patients - Trauma/Burn/Critical care, peds, cardiac surgery, ECMO" and "Dose Edge IV Experience Pyxis Experience Meditech Vigilanz" and "Must have : Hospital experience > 2years". That's a mix of experience and skills. Could be Requirements.
I think I'll do:
About the Role
Travel Pharmacist position in Richmond, Virginia. The role involves caring for complex patients including trauma/burn/critical care, pediatrics, cardiac surgery, and ECMO cases.
Schedule
- Start Date: ASAP
- Duration: 23 weeks
- Hours per Week: 40
- Shift: 10 hours, nights
- Employment Type: Travel
Responsibilities
- IV verification
- Medication verification
- IV compounding as needed
Requirements
- Virginia State Pharmacist license required
- Hospital experience > 2 years
- Experience with complex patients: trauma/burn/critical care, pediatrics, cardiac surgery, ECMO
- Dose Edge IV experience
- Pyxis experience
- Meditech Vigilanz experience
Qualifications
- Vancomycin AUC dosing experience
- Aminoglycoside dosing
- Renal dosing
- Warfarin management
- Enoxaparin management
- Electrolyte protocols
- Heparin management
- DOAC (Direct Oral Anticoagulant) experience
The "Advanced skills needed" are qualifications. The "Requested Skill Set" includes both requirements and skills. I split them.
Now, the company description: "About TalentBurst, Inc" - I could include as a section "About the Company" but not in the example list. The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I cannot use others, but to be safe, I'll omit it or fold into a short p at the end? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description is not boilerplate. But the user might want only the job details. However, "Preserve ALL substantive information". I'll include it as a section with heading "About the Company" but that's not in the example. Alternatively, I could put it under "About the Role" but that's not accurate. I think I'll include it as a separate section with h3 "About the Company" because it's substantive. But the rule says "include a section ONLY when the posting has real, specific content for it". It does. And "never emit a heading followed by filler/placeholder text". The company description is real. So I'll include.
But the example headings are given as e.g., so it's not exhaustive. I'll include.
Also, the Job ID: "TalentBurst, Inc Job ID #26-30109." Should fold into a short p or drop. I'll drop it as it's minor metadata.
Pay package: "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is not specific, so no Pay section.
Now, the "Posted job title: Travel Pharmacist" - do not repeat job title as heading.
Now, output only HTML fragment.
Let me write the HTML.
I'll structure:
About the Role
Travel Pharmacist position in Richmond, Virginia. The role involves caring for complex patients including trauma/burn/critical care, pediatrics, cardiac surgery, and ECMO cases.
Schedule
- Start Date: ASAP
- Duration: 23 weeks
- Hours per Week: 40
- Shift: 10 hours, nights
- Employment Type: Travel
Responsibilities
- IV verification
- Medication verification
- IV compounding as needed
Requirements
- Virginia State Pharmacist license required
- Hospital experience > 2 years
- Experience with complex patients: trauma/burn/critical care, pediatrics, cardiac surgery, ECMO
- Dose Edge IV experience
- Pyxis experience
- Meditech Vigilanz experience
Qualifications
- Vancomycin AUC dosing experience
- Aminoglycoside dosing
- Renal dosing
- Warfarin management
- Enoxaparin management
- Electrolyte protocols
- Heparin management
- DOAC (Direct Oral Anticoagulant) experience
About the Company
TalentBurst Health & Life Sciences is an established provider of healthcare workforce solutions, servicing healthcare facilities across the United States for over 15 years. As a Joint Commission Certified Agency, their commitment to quality, integrity, and exceptional service has
for prose - Do NOT repeat job title as heading - Do NOT put Job ID as heading - fold into short
or drop - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when posting has real, specific content - never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment - no html/body, no markdown code fences Let me structure this: The posting has: 1. Job details (start date, duration, hours, shift, employment type) - could be "About the role" or "Schedule" but schedule is specific: 10 hours nights, 40 hours/week, 23 weeks, ASAP start. That's substantive schedule info. 2. Requested skill set - this is requirements/qualifications 3. Advanced skills needed - more requirements 4. Procedures performed on unit - responsibilities 5. Certifications required - qualifications 6. About TalentBurst - company info, but the rule says remove boilerplate? The "About TalentBurst" is company description, not boilerplate like EEO. But it's not about the role. The user said "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Company description might be considered boilerplate? However, it's part of the posting. The instruction: "Preserve ALL substantive information". The company description is substantive about the employer. But the rule also says "Prefer a few substantive sections over many thin ones." I think I should include it as a section maybe "About the Company" but the allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Company" is not in the list. The list says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It says "e.g." so maybe other headings allowed? But better to stick to those. Could fold company info into a short p at the end? Or maybe not include because it's not about the role. The user said "reformat a job posting into clean, well-structured semantic HTML". The company description is part of the posting. But the rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Company description is not that. However, the example headings don't include "About the Company". I could include it as a section with h3 "About the Company" but the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid others, but says "e.g." meaning examples. I think it's okay to add "About the Company" if there's content. But the instruction also says "include a section ONLY when the posting has real, specific content for it". The company description is real and specific. However, the user might expect only those standard sections. Let me see the pay package: "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is not specific pay amount, it says "to be determined". That's placeholder/filler. So I should NOT create a Pay section. Similarly, Benefits not mentioned. Schedule is specific: 10 hours nights, 40 hours/week, 23 weeks, ASAP start. That's substantive schedule info. So I can have a Schedule section.
Now, the requested skill set and advanced skills and procedures and certifications are all requirements/qualifications. I could combine into "Requirements" and "Responsibilities". Procedures performed on unit are responsibilities. Requested skill set and advanced skills are requirements/qualifications. Certifications are qualifications.
Let me create sections:
- About the role: could include the job details (specialty, discipline, start date, duration, employment type) and maybe the shift/hours? But schedule separate.
Better:
- About the role: prose describing the role: travel pharmacist in Richmond, Virginia, complex patients, trauma/burn/critical care, peds, cardiac surgery, ECMO. That's from the skill set.
- Schedule: specific schedule details.
- Responsibilities: procedures performed on unit.
- Requirements: requested skill set (experience, systems), advanced skills, certifications.
- Qualifications: maybe same as requirements? Could combine.
The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Skills could be a separate section for the skill set. But the skill set is more like requirements. I'll use Requirements for the must-haves, and maybe Skills for the requested skill set? But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Skills is an allowed heading. The "Requested Skill Set" could be a Skills section. However, the content includes "Will experience complex patients - Trauma/Burn/Critical care, peds, cardiac surgery, ECMO" and "Dose Edge IV Experience Pyxis Experience Meditech Vigilanz" and "Must have : Hospital experience > 2years". That's a mix of experience and skills. Could be Requirements.
I think I'll do:
About the Role
About the Role
Travel Pharmacist position in Richmond, Virginia. The role involves caring for complex patients including trauma/burn/critical care, pediatrics, cardiac surgery, and ECMO cases.
Schedule
- Start Date: ASAP
- Duration: 23 weeks
- Hours per Week: 40
- Shift: 10 hours, nights
- Employment Type: Travel
Responsibilities
- IV verification
- Medication verification
- IV compounding as needed
Requirements
- Virginia State Pharmacist license required
- Hospital experience > 2 years
- Experience with complex patients: trauma/burn/critical care, pediatrics, cardiac surgery, ECMO
- Dose Edge IV experience
- Pyxis experience
- Meditech Vigilanz experience
Qualifications
- Vancomycin AUC dosing experience
- Aminoglycoside dosing
- Renal dosing
- Warfarin management
- Enoxaparin management
- Electrolyte protocols
- Heparin management
- DOAC (Direct Oral Anticoagulant) experience
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I cannot use others, but to be safe, I'll omit it or fold into a short p at the end? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description is not boilerplate. But the user might want only the job details. However, "Preserve ALL substantive information". I'll include it as a section with heading "About the Company" but that's not in the example. Alternatively, I could put it under "About the Role" but that's not accurate. I think I'll include it as a separate section with h3 "About the Company" because it's substantive. But the rule says "include a section ONLY when the posting has real, specific content for it". It does. And "never emit a heading followed by filler/placeholder text". The company description is real. So I'll include.
But the example headings are given as e.g., so it's not exhaustive. I'll include.
Also, the Job ID: "TalentBurst, Inc Job ID #26-30109." Should fold into a short p or drop. I'll drop it as it's minor metadata.
Pay package: "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is not specific, so no Pay section.
Now, the "Posted job title: Travel Pharmacist" - do not repeat job title as heading.
Now, output only HTML fragment.
Let me write the HTML.
I'll structure:
About the Role
Travel Pharmacist position in Richmond, Virginia. The role involves caring for complex patients including trauma/burn/critical care, pediatrics, cardiac surgery, and ECMO cases.
Schedule
- Start Date: ASAP
- Duration: 23 weeks
- Hours per Week: 40
- Shift: 10 hours, nights
- Employment Type: Travel
Responsibilities
- IV verification
- Medication verification
- IV compounding as needed
Requirements
- Virginia State Pharmacist license required
- Hospital experience > 2 years
- Experience with complex patients: trauma/burn/critical care, pediatrics, cardiac surgery, ECMO
- Dose Edge IV experience
- Pyxis experience
- Meditech Vigilanz experience
Qualifications
- Vancomycin AUC dosing experience
- Aminoglycoside dosing
- Renal dosing
- Warfarin management
- Enoxaparin management
- Electrolyte protocols
- Heparin management
- DOAC (Direct Oral Anticoagulant) experience
About the Company
TalentBurst Health & Life Sciences is an established provider of healthcare workforce solutions, servicing healthcare facilities across the United States for over 15 years. As a Joint Commission Certified Agency, their commitment to quality, integrity, and exceptional service has