Travel Physical Therapist - $1,756 per week
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. 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 boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key details:
- Job: Travel Physical Therapist (PT) at Fusion Medical Staffing, location Elkton, VA.
- Specialty: Physical Therapist
- Discipline: Therapy
- Start Date: ASAP
- Duration: 13 weeks
- 40 hours per week
- Shift: 8 hours, days
- Employment Type: Travel
- Required Qualifications:
- Valid Physical Therapy license in compliance with state regulations
- Current BLS certification (AHA/ARC)
- Preferred Qualifications:
- Doctorate degree in physical therapy
- Physical Therapy experience, but New Grads are welcome to apply
- Other certifications or licenses may be required for this position
- Summary: description of PT role.
- Essential Work Functions: list of duties (multiple bullet points). We'll need to put them in
- .
- Required Essential Skills: list of skills (critical thinking, service excellence, good interpersonal communication skills; ability to read/write/communicate in English; ability to read/comprehend written instructions, follow verbal instructions, proficiency in PC skills; Physical Abilities - must be able to remain stationary, move about, move equipment (50-100lbs), push, pull, bend; Interpersonal Skills - must be able to work effectively with variety of personnel; Technical/Motor Skills - ability to grasp, fine manipulation, push/pull, move about; Mental Requirements - cope with frequent contact, meet deadlines under pressure, work under close supervision occasionally, work without assistance, contend with irregular activity schedules occasionally, continuous concentration to detail; Sensory - visual acuity and ability to effectively communicate). This is a list; we can put in
- .
- Benefits Include: list of benefits (highly competitive pay for travel professionals; comprehensive medical, dental, vision insurance with first day coverage; Paid Time Off (PTO) after 1560 hours; Life and Short-term disability offered; 401(k) matching; Aggressive Refer-a-friend Bonus Program; 24/7 recruiter support; Reimbursement for licensure and CEUs). Also later "Benefits" section repeats: Benefits start day 1; Medical benefits; Dental benefits; Vision benefits; Referral bonus; Mileage reimbursement; License and certification reimbursement; Weekly pay; Cancelation protection; Guaranteed Hours; Employee assistance programs; Continuing Education. We need to combine and avoid duplication. We should preserve all substantive info, but not duplicate lines. So we need to merge similar items.
- Pay: The posting mentions "competitive pay", "highly competitive pay for travel professionals", "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." There's no specific numeric pay. So we cannot create a Pay section with actual numbers; but we can include a Pay section is allowed only if posting actually states them. It states "competitive pay" and "highly competitive pay". That's vague but still states pay exists. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay (competitive pay). So we can include a Pay section with the statement about competitive pay and tax-free stipend TBD. But we must avoid filler like "commensurate with experience" etc. The phrase "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's specific enough? It mentions basis but not actual amount. It's not a placeholder like "TBD"? It says "tax-free stipend amount to be determined." That's somewhat TBD but still mentions it's to be determined. Might be considered placeholder. Safer to not create a Pay section if it's just vague. However we could include a short
about pay being competitive and based on 8hr shifts, 40hr/week, tax-free stipend TBD. That is substantive? It's not a number but it's info. The instruction says "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "tax-free stipend amount to be determined" is essentially TBD. So maybe we should avoid Pay section. However we could still mention pay in Benefits or elsewhere? The Benefits section includes "Highly competitive pay for travel professionals". That is a benefit statement. So we could keep that under Benefits. So we may not need a separate Pay section.
- Schedule: The posting states "40 hours per week", "Shift: 8 hours, days". That's schedule info. So we can create a Schedule section with those details. It's specific: 40 hrs/week, 8hr day shifts. So we can include Schedule.
- Benefits: we have list. We'll create Benefits section with
- items.
- About the role: maybe we can include a short paragraph summarizing role (the Summary and maybe the "Why Choose Fusion?" etc). But we need to avoid duplication. The posting includes a Summary paragraph about PT role. Also "Why Choose Fusion?" is marketing fluff but still substantive? It may be considered boilerplate? It's not EEO/legal but it's promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Choose Fusion?" might be considered promotional but not boilerplate; it's substantive about company. However we might keep a short "About the role" section using the Summary paragraph. Or we could incorporate that into Responsibilities? Actually Responsibilities are the Essential Work Functions. So we can have sections: Responsibilities (essential work functions), Requirements (required qualifications), Preferred Qualifications (maybe under Requirements or separate Qualifications), Skills (essential skills), Benefits, Schedule. Possibly also About the role (summary). But we need to prefer few substantive sections over many thin ones. So we could combine some.
Let's decide sections:
- Responsibilities: Essential Work Functions (list)
- Requirements: Required Qualifications (list) + maybe Preferred Qualifications? Could separate but we can combine under Requirements with subheadings? But we only allowed
for section headings; we cannot have subheadings unless we use again. Could have separate sections: Requirements and Preferred Qualifications. But that may be thin. However we have enough content for each.
- Skills: Required Essential Skills (list)
- Benefits: Benefits Include list + later Benefits list (combined)
- Schedule: 40 hours per week, Shift: 8 hours, days
- About the role: Summary paragraph (maybe also include Start Date, Duration, Location). Could incorporate location and start date etc. But location is already known from job heading? The page already shows job title; location maybe not shown. We could include location in a short paragraph under About the role.
We must not repeat job title as heading. So we can have About the role
with paragraph containing location, start date, duration, etc.
We must not include Job ID/requisition numbers as headings; we can drop them or put in a short
. We'll drop.
We must remove boilerplate like "Other Duties Disclaimer", "Start your rewarding career... Apply now!", "*Fusion is an EOE/E-Verify Employer", "Fusion Medical Staffing-Therapy Job ID #1999587.", "About Fusion Medical Staffing-Therapy" (that's promotional but maybe we can keep some? It's lengthy; might be considered boilerplate? It's about the company; could be considered relevant but maybe we can keep a short snippet? The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Fusion Medical Staffing-Therapy" section is not exactly boilerplate but it's promotional; still might be considered okay to keep? However we should prefer few substantive sections; we could incorporate a brief note about company mission in About the role.
But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot discard substantive info like "Benefits start day 1", "Medical benefits", etc. Those are substantive. So we need to keep them.
Thus we need to include all benefits items.
Let's extract all benefits from the text:
From "Benefits Include:" list:
- Highly competitive pay for travel professionals
- Comprehensive medical, dental, and vision insurance with first day coverage
- Paid Time Off (PTO) after 1560 hours
- Life and Short-term disability offered
- 401(k) matching
- Aggressive Refer-a-friend Bonus Program
- 24/7 recruiter support
- Reimbursement for licensure and CEUs
Later "Benefits" section:
- Benefits start day 1
- Medical benefits
- Dental benefits
- Vision benefits
- Referral bonus
- Mileage reimbursement
- License and certification reimbursement
- Weekly pay
- Cancelation protection
- Guaranteed Hours
- Employee assistance programs
- Continuing Education
We need to combine and avoid duplicates. Overlap: medical/dental/vision benefits already covered; referral bonus; license and certification reimbursement; weekly pay (maybe same as competitive pay); etc.
We'll create a unified list, ensuring each item appears once.
Let's list unique benefits:
- Highly competitive pay for travel professionals (or weekly pay)
- Comprehensive medical, dental, and vision insurance with first day coverage
- Paid Time Off (PTO) after 1560 hours
- Life and Short-term disability offered
- 401(k) matching
- Aggressive Refer-a-friend Bonus Program
- 24/7 recruiter support
- Reimbursement for licensure and CEUs
- Mileage reimbursement
- Cancelation protection
- Guaranteed Hours
- Employee assistance programs
- Continuing Education
- Benefits start day 1 (maybe redundant with first day coverage; but we can keep as "Benefits start day 1")
- Weekly pay (maybe same as competitive pay)
- Referral bonus (same as Aggressive Refer-a-friend Bonus Program)
- License and certification reimbursement (same as reimbursement for licensure and CEUs)
- etc.
We need to decide what to keep. To preserve ALL substantive information, we should not discard any distinct benefit items. However some are duplicates; we can merge similar but keep distinct phrasing? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we merge duplicates, we are not losing info; we are just combining similar statements. That's acceptable as long as we don't lose any distinct info. For example, "Comprehensive medical, dental, and vision insurance with first day coverage" and later "Medical benefits", "Dental benefits", "Vision benefits", "Benefits start day 1" are subsets; we can keep the comprehensive statement and maybe note that benefits start day 1 is already implied. But to preserve all, we could keep both but that would be
for prose. Do NOT repeat job title as heading. 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 boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key details: - Job: Travel Physical Therapist (PT) at Fusion Medical Staffing, location Elkton, VA. - Specialty: Physical Therapist - Discipline: Therapy - Start Date: ASAP - Duration: 13 weeks - 40 hours per week - Shift: 8 hours, days - Employment Type: Travel - Required Qualifications: - Valid Physical Therapy license in compliance with state regulations - Current BLS certification (AHA/ARC) - Preferred Qualifications: - Doctorate degree in physical therapy - Physical Therapy experience, but New Grads are welcome to apply - Other certifications or licenses may be required for this position - Summary: description of PT role. - Essential Work Functions: list of duties (multiple bullet points). We'll need to put them in
- .
- Required Essential Skills: list of skills (critical thinking, service excellence, good interpersonal communication skills; ability to read/write/communicate in English; ability to read/comprehend written instructions, follow verbal instructions, proficiency in PC skills; Physical Abilities - must be able to remain stationary, move about, move equipment (50-100lbs), push, pull, bend; Interpersonal Skills - must be able to work effectively with variety of personnel; Technical/Motor Skills - ability to grasp, fine manipulation, push/pull, move about; Mental Requirements - cope with frequent contact, meet deadlines under pressure, work under close supervision occasionally, work without assistance, contend with irregular activity schedules occasionally, continuous concentration to detail; Sensory - visual acuity and ability to effectively communicate). This is a list; we can put in
- .
- Benefits Include: list of benefits (highly competitive pay for travel professionals; comprehensive medical, dental, vision insurance with first day coverage; Paid Time Off (PTO) after 1560 hours; Life and Short-term disability offered; 401(k) matching; Aggressive Refer-a-friend Bonus Program; 24/7 recruiter support; Reimbursement for licensure and CEUs). Also later "Benefits" section repeats: Benefits start day 1; Medical benefits; Dental benefits; Vision benefits; Referral bonus; Mileage reimbursement; License and certification reimbursement; Weekly pay; Cancelation protection; Guaranteed Hours; Employee assistance programs; Continuing Education. We need to combine and avoid duplication. We should preserve all substantive info, but not duplicate lines. So we need to merge similar items.
- Pay: The posting mentions "competitive pay", "highly competitive pay for travel professionals", "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." There's no specific numeric pay. So we cannot create a Pay section with actual numbers; but we can include a Pay section is allowed only if posting actually states them. It states "competitive pay" and "highly competitive pay". That's vague but still states pay exists. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay (competitive pay). So we can include a Pay section with the statement about competitive pay and tax-free stipend TBD. But we must avoid filler like "commensurate with experience" etc. The phrase "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's specific enough? It mentions basis but not actual amount. It's not a placeholder like "TBD"? It says "tax-free stipend amount to be determined." That's somewhat TBD but still mentions it's to be determined. Might be considered placeholder. Safer to not create a Pay section if it's just vague. However we could include a short
about pay being competitive and based on 8hr shifts, 40hr/week, tax-free stipend TBD. That is substantive? It's not a number but it's info. The instruction says "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". The phrase "tax-free stipend amount to be determined" is essentially TBD. So maybe we should avoid Pay section. However we could still mention pay in Benefits or elsewhere? The Benefits section includes "Highly competitive pay for travel professionals". That is a benefit statement. So we could keep that under Benefits. So we may not need a separate Pay section. - Schedule: The posting states "40 hours per week", "Shift: 8 hours, days". That's schedule info. So we can create a Schedule section with those details. It's specific: 40 hrs/week, 8hr day shifts. So we can include Schedule. - Benefits: we have list. We'll create Benefits section with
- items.
- About the role: maybe we can include a short paragraph summarizing role (the Summary and maybe the "Why Choose Fusion?" etc). But we need to avoid duplication. The posting includes a Summary paragraph about PT role. Also "Why Choose Fusion?" is marketing fluff but still substantive? It may be considered boilerplate? It's not EEO/legal but it's promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Choose Fusion?" might be considered promotional but not boilerplate; it's substantive about company. However we might keep a short "About the role" section using the Summary paragraph. Or we could incorporate that into Responsibilities? Actually Responsibilities are the Essential Work Functions. So we can have sections: Responsibilities (essential work functions), Requirements (required qualifications), Preferred Qualifications (maybe under Requirements or separate Qualifications), Skills (essential skills), Benefits, Schedule. Possibly also About the role (summary). But we need to prefer few substantive sections over many thin ones. So we could combine some.
Let's decide sections:
- Responsibilities: Essential Work Functions (list)
- Requirements: Required Qualifications (list) + maybe Preferred Qualifications? Could separate but we can combine under Requirements with subheadings? But we only allowed
for section headings; we cannot have subheadings unless we use
again. Could have separate sections: Requirements and Preferred Qualifications. But that may be thin. However we have enough content for each. - Skills: Required Essential Skills (list) - Benefits: Benefits Include list + later Benefits list (combined) - Schedule: 40 hours per week, Shift: 8 hours, days - About the role: Summary paragraph (maybe also include Start Date, Duration, Location). Could incorporate location and start date etc. But location is already known from job heading? The page already shows job title; location maybe not shown. We could include location in a short paragraph under About the role. We must not repeat job title as heading. So we can have
About the role
with paragraph containing location, start date, duration, etc. We must not include Job ID/requisition numbers as headings; we can drop them or put in a short. We'll drop. We must remove boilerplate like "Other Duties Disclaimer", "Start your rewarding career... Apply now!", "*Fusion is an EOE/E-Verify Employer", "Fusion Medical Staffing-Therapy Job ID #1999587.", "About Fusion Medical Staffing-Therapy" (that's promotional but maybe we can keep some? It's lengthy; might be considered boilerplate? It's about the company; could be considered relevant but maybe we can keep a short snippet? The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Fusion Medical Staffing-Therapy" section is not exactly boilerplate but it's promotional; still might be considered okay to keep? However we should prefer few substantive sections; we could incorporate a brief note about company mission in About the role. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot discard substantive info like "Benefits start day 1", "Medical benefits", etc. Those are substantive. So we need to keep them. Thus we need to include all benefits items. Let's extract all benefits from the text: From "Benefits Include:" list: - Highly competitive pay for travel professionals - Comprehensive medical, dental, and vision insurance with first day coverage - Paid Time Off (PTO) after 1560 hours - Life and Short-term disability offered - 401(k) matching - Aggressive Refer-a-friend Bonus Program - 24/7 recruiter support - Reimbursement for licensure and CEUs Later "Benefits" section: - Benefits start day 1 - Medical benefits - Dental benefits - Vision benefits - Referral bonus - Mileage reimbursement - License and certification reimbursement - Weekly pay - Cancelation protection - Guaranteed Hours - Employee assistance programs - Continuing Education We need to combine and avoid duplicates. Overlap: medical/dental/vision benefits already covered; referral bonus; license and certification reimbursement; weekly pay (maybe same as competitive pay); etc. We'll create a unified list, ensuring each item appears once. Let's list unique benefits: - Highly competitive pay for travel professionals (or weekly pay) - Comprehensive medical, dental, and vision insurance with first day coverage - Paid Time Off (PTO) after 1560 hours - Life and Short-term disability offered - 401(k) matching - Aggressive Refer-a-friend Bonus Program - 24/7 recruiter support - Reimbursement for licensure and CEUs - Mileage reimbursement - Cancelation protection - Guaranteed Hours - Employee assistance programs - Continuing Education - Benefits start day 1 (maybe redundant with first day coverage; but we can keep as "Benefits start day 1") - Weekly pay (maybe same as competitive pay) - Referral bonus (same as Aggressive Refer-a-friend Bonus Program) - License and certification reimbursement (same as reimbursement for licensure and CEUs) - etc. We need to decide what to keep. To preserve ALL substantive information, we should not discard any distinct benefit items. However some are duplicates; we can merge similar but keep distinct phrasing? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we merge duplicates, we are not losing info; we are just combining similar statements. That's acceptable as long as we don't lose any distinct info. For example, "Comprehensive medical, dental, and vision insurance with first day coverage" and later "Medical benefits", "Dental benefits", "Vision benefits", "Benefits start day 1" are subsets; we can keep the comprehensive statement and maybe note that benefits start day 1 is already implied. But to preserve all, we could keep both but that would be
- items.
- About the role: maybe we can include a short paragraph summarizing role (the Summary and maybe the "Why Choose Fusion?" etc). But we need to avoid duplication. The posting includes a Summary paragraph about PT role. Also "Why Choose Fusion?" is marketing fluff but still substantive? It may be considered boilerplate? It's not EEO/legal but it's promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Choose Fusion?" might be considered promotional but not boilerplate; it's substantive about company. However we might keep a short "About the role" section using the Summary paragraph. Or we could incorporate that into Responsibilities? Actually Responsibilities are the Essential Work Functions. So we can have sections: Responsibilities (essential work functions), Requirements (required qualifications), Preferred Qualifications (maybe under Requirements or separate Qualifications), Skills (essential skills), Benefits, Schedule. Possibly also About the role (summary). But we need to prefer few substantive sections over many thin ones. So we could combine some.
Let's decide sections:
- Responsibilities: Essential Work Functions (list)
- Requirements: Required Qualifications (list) + maybe Preferred Qualifications? Could separate but we can combine under Requirements with subheadings? But we only allowed
- .
- Benefits Include: list of benefits (highly competitive pay for travel professionals; comprehensive medical, dental, vision insurance with first day coverage; Paid Time Off (PTO) after 1560 hours; Life and Short-term disability offered; 401(k) matching; Aggressive Refer-a-friend Bonus Program; 24/7 recruiter support; Reimbursement for licensure and CEUs). Also later "Benefits" section repeats: Benefits start day 1; Medical benefits; Dental benefits; Vision benefits; Referral bonus; Mileage reimbursement; License and certification reimbursement; Weekly pay; Cancelation protection; Guaranteed Hours; Employee assistance programs; Continuing Education. We need to combine and avoid duplication. We should preserve all substantive info, but not duplicate lines. So we need to merge similar items.
- Pay: The posting mentions "competitive pay", "highly competitive pay for travel professionals", "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." There's no specific numeric pay. So we cannot create a Pay section with actual numbers; but we can include a Pay section is allowed only if posting actually states them. It states "competitive pay" and "highly competitive pay". That's vague but still states pay exists. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay (competitive pay). So we can include a Pay section with the statement about competitive pay and tax-free stipend TBD. But we must avoid filler like "commensurate with experience" etc. The phrase "Pay package is based on 8 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's specific enough? It mentions basis but not actual amount. It's not a placeholder like "TBD"? It says "tax-free stipend amount to be determined." That's somewhat TBD but still mentions it's to be determined. Might be considered placeholder. Safer to not create a Pay section if it's just vague. However we could include a short