Travel Emergency Room RN - $2,147 per week
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. 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.
We need to extract substantive content: The posting includes:
- Access Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Muskegon, Michigan.
- Job Description & Requirements
- Specialty: ED - Emergency Department
- Discipline: RN
- Start Date: 10/12/2026
- Duration: 12 weeks
- 36 hours per week
- Shift: 12 hours, nights
- Employment Type: Travel
- Access Healthcare Job ID #80484861.
- Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
- About Access Healthcare: description.
We need to decide sections: Possibly "About the role" (description of role), "Responsibilities" (none given), "Requirements" (maybe specialty, discipline, shift, etc.), "Qualifications" (maybe none), "Skills" (none), "Benefits" (maybe none explicit), "Pay" (pay package info), "Schedule" (shift and hours). The instructions: only include sections when posting has real, specific content. So we can include:
- About the role: maybe the description of the job (travel nurse RN ED in Muskegon, Michigan). Could be a paragraph.
- Requirements: could list Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type.
- Pay: mention pay package based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
- Schedule: shift 12 hours, nights; 36 hours per week.
But note that schedule and pay may overlap with requirements. However we can separate.
We must not include placeholder like "tax-free stipend amount to be determined" is specific enough? It says amount to be determined, but still it's mention of pay package. It's not placeholder like "commensurate with experience". It's specific that it's based on 12 hour shifts and 36 hours per week, subject to confirmation, with tax-free stipend amount to be determined. That's substantive enough.
We must not include Job ID as heading; we can fold into a short
maybe.
We must not include duplicated lines.
We must not include boilerplate like "About Access Healthcare aims to provide superior service..." That's substantive, we can include as "About Access Healthcare" maybe as a section? The allowed headings list includes "About the role", not "About Access Healthcare". But we could use "About the role" for the role description, and maybe "About Access Healthcare" is not in the list; but we could incorporate that into a paragraph under "About the role" or maybe we can create a section "About the company"? Not in list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, but we should stick to those headings? Likely we should only use those headings. So we should not create a heading like "About Access Healthcare". Instead we could put that info under "About the role" or maybe under a generic paragraph without heading? But we need to use headings for sections. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings; maybe we can also use other headings if needed? But they gave examples; likely they expect us to use those headings only. So we need to map content to those headings.
Thus:
- About the role: could include the job seeking statement, location, and maybe the description of Access Healthcare? Actually "About the role" is about the role, not the company. So we can put the job description: "Access Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Muskegon, Michigan." plus maybe the shift details? But shift details could go under Schedule.
- Responsibilities: not provided, so we skip.
- Requirements: could list Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type.
- Qualifications: not provided.
- Skills: not provided.
- Benefits: not provided explicitly (they mention benefits package in About Access Healthcare but not specific). So we skip Benefits.
- Pay: include the pay package statement.
- Schedule: include shift and hours.
We also need to include the About Access Healthcare description somewhere. Could we put it under "About the role"? That might be odd but acceptable as it's about the company, not role. But maybe we can put it under a paragraph without a heading? The instruction says use for section headings for those categories; but we can still have
paragraphs outside headings? The output should be only HTML fragment; we can have
elements not under a heading? Probably yes, but they'd like sections. However we can include a
about Access Healthcare after the heading sections, maybe as a general paragraph. But they said "Prefer a few substantive sections over many thin ones." So maybe we combine About Access Healthcare into About the role section.
Thus About the role section could contain two paragraphs: one about the job seeking, another about Access Healthcare description.
Let's craft:
About the role
Access Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Muskegon, Michigan.
Access Healthcare aims to provide superior service to our nursing family by providing around the clock support, competitive pay packages and an unmatched benefits package! Unlike other agencies, we offer a true family feel and work with you to find the placement that is right for you. We offer one of the top leading pay packages in the industry and we are ready to get you the money you deserve! Access Healthcare was founded by two travel nurses, Danielle and Diego, who had a dream and a shared vision of creating an agency which all nurses would want to work with. Our passion has led us to where we are today as one of the top 10 agencies in our home state of New Jersey, with access to contracts in all 50 states! We encourage you to join our team and we cannot wait to get to know you!
Then Requirements:
Requirements
- Specialty: ED - Emergency Department
- Discipline: RN
- Start Date: 10/12/2026
- Duration: 12 weeks
- 36 hours per week
- Shift: 12 hours, nights
- Employment Type: Travel
Pay:
Pay
Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
Schedule:
Schedule
Shift: 12 hours, nights; 36 hours per week.
We might also include Job ID somewhere; maybe as a short paragraph after Requirements? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. So we can add a
after the heading sections maybe:
Job ID: #80484861
. But is that minor metadata? Yes. We can include it as a short p.
We must not repeat the job title as a heading; we didn't.
We must not include boilerplate like EEO etc. Not present.
We must not include application instructions; none.
Now check for any placeholder text: "tax-free stipend amount to be determined" is not placeholder like "TBD"? It says amount to be determined, but it's still specific that it's tax-free stipend amount to be determined. Might be considered placeholder? 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. The Pay section we have includes "tax-free stipend amount to be determined". That is somewhat vague but it's still stating that there is a tax-free stipend, amount to be determined. It's not exactly "not specified" but similar. However the posting explicitly says that, so we must preserve ALL substantive information. So we keep it.
Now check if any section is thin: Requirements has many items, good. About the role has two paragraphs. Pay has one sentence. Schedule has one sentence. Could we combine Pay and Schedule into Requirements? But they said prefer few substantive sections over many thin ones. Pay and Schedule are each one sentence; maybe we could combine them into a "Compensation & Schedule" section but not in allowed headings. However we could keep them as separate sections; they are thin but still substantive. The instruction says prefer a few substantive sections over many thin ones; but we already have About the role and Requirements as substantive; Pay and Schedule are thin but still needed to preserve info. Could we merge Pay and Schedule into Requirements? That would make Requirements longer but then we lose separate headings. However the instruction says use those headings for sections; we can still have Pay and Schedule sections if they have real specific content. They do. So it's okay.
Now ensure we didn't include any duplicated lines. The posting had "Access Healthcare Job ID #80484861." and also "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." No duplication.
Now output only HTML fragment, no /, no markdown fences.
Thus final output:
About the role
Access Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Muskegon, Michigan.
Access Healthcare aims to provide superior service to our nursing family by providing around the clock support, competitive pay packages and an unmatched benefits package! Unlike other agencies, we offer a true family feel and work with you to find the placement that is right for you. We offer one of the top leading pay packages in the industry and we are ready to get you the money you deserve! Access Healthcare was founded by two travel nurses, Danielle and Diego, who had a dream and a shared vision of creating an agency which all nurses would want to work with. Our passion has led us to where we are today as one of the top 10 agencies in our home state of New Jersey, with access to contracts in all 50 states! We encourage you to join our team and we cannot wait to get to know you!
Requ
for prose. 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. 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. We need to extract substantive content: The posting includes: - Access Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Muskegon, Michigan. - Job Description & Requirements - Specialty: ED - Emergency Department - Discipline: RN - Start Date: 10/12/2026 - Duration: 12 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Access Healthcare Job ID #80484861. - Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - About Access Healthcare: description. We need to decide sections: Possibly "About the role" (description of role), "Responsibilities" (none given), "Requirements" (maybe specialty, discipline, shift, etc.), "Qualifications" (maybe none), "Skills" (none), "Benefits" (maybe none explicit), "Pay" (pay package info), "Schedule" (shift and hours). The instructions: only include sections when posting has real, specific content. So we can include: - About the role: maybe the description of the job (travel nurse RN ED in Muskegon, Michigan). Could be a paragraph. - Requirements: could list Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type. - Pay: mention pay package based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Schedule: shift 12 hours, nights; 36 hours per week. But note that schedule and pay may overlap with requirements. However we can separate. We must not include placeholder like "tax-free stipend amount to be determined" is specific enough? It says amount to be determined, but still it's mention of pay package. It's not placeholder like "commensurate with experience". It's specific that it's based on 12 hour shifts and 36 hours per week, subject to confirmation, with tax-free stipend amount to be determined. That's substantive enough. We must not include Job ID as heading; we can fold into a short
maybe. We must not include duplicated lines. We must not include boilerplate like "About Access Healthcare aims to provide superior service..." That's substantive, we can include as "About Access Healthcare" maybe as a section? The allowed headings list includes "About the role", not "About Access Healthcare". But we could use "About the role" for the role description, and maybe "About Access Healthcare" is not in the list; but we could incorporate that into a paragraph under "About the role" or maybe we can create a section "About the company"? Not in list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, but we should stick to those headings? Likely we should only use those headings. So we should not create a heading like "About Access Healthcare". Instead we could put that info under "About the role" or maybe under a generic paragraph without heading? But we need to use headings for sections. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings; maybe we can also use other headings if needed? But they gave examples; likely they expect us to use those headings only. So we need to map content to those headings.
Thus:
- About the role: could include the job seeking statement, location, and maybe the description of Access Healthcare? Actually "About the role" is about the role, not the company. So we can put the job description: "Access Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Muskegon, Michigan." plus maybe the shift details? But shift details could go under Schedule.
- Responsibilities: not provided, so we skip.
- Requirements: could list Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type.
- Qualifications: not provided.
- Skills: not provided.
- Benefits: not provided explicitly (they mention benefits package in About Access Healthcare but not specific). So we skip Benefits.
- Pay: include the pay package statement.
- Schedule: include shift and hours.
We also need to include the About Access Healthcare description somewhere. Could we put it under "About the role"? That might be odd but acceptable as it's about the company, not role. But maybe we can put it under a paragraph without a heading? The instruction says use for section headings for those categories; but we can still have
for section headings for those categories; but we can still have
paragraphs outside headings? The output should be only HTML fragment; we can have
elements not under a heading? Probably yes, but they'd like sections. However we can include a
about Access Healthcare after the heading sections, maybe as a general paragraph. But they said "Prefer a few substantive sections over many thin ones." So maybe we combine About Access Healthcare into About the role section. Thus About the role section could contain two paragraphs: one about the job seeking, another about Access Healthcare description. Let's craft:
About the role
Access Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Muskegon, Michigan.
Access Healthcare aims to provide superior service to our nursing family by providing around the clock support, competitive pay packages and an unmatched benefits package! Unlike other agencies, we offer a true family feel and work with you to find the placement that is right for you. We offer one of the top leading pay packages in the industry and we are ready to get you the money you deserve! Access Healthcare was founded by two travel nurses, Danielle and Diego, who had a dream and a shared vision of creating an agency which all nurses would want to work with. Our passion has led us to where we are today as one of the top 10 agencies in our home state of New Jersey, with access to contracts in all 50 states! We encourage you to join our team and we cannot wait to get to know you!
Then Requirements:Requirements
- Specialty: ED - Emergency Department
- Discipline: RN
- Start Date: 10/12/2026
- Duration: 12 weeks
- 36 hours per week
- Shift: 12 hours, nights
- Employment Type: Travel
Pay
Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined.
Schedule:Schedule
Shift: 12 hours, nights; 36 hours per week.
We might also include Job ID somewhere; maybe as a short paragraph after Requirements? But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. So we can add a
after the heading sections maybe:
Job ID: #80484861
. But is that minor metadata? Yes. We can include it as a short p. We must not repeat the job title as a heading; we didn't. We must not include boilerplate like EEO etc. Not present. We must not include application instructions; none. Now check for any placeholder text: "tax-free stipend amount to be determined" is not placeholder like "TBD"? It says amount to be determined, but it's still specific that it's tax-free stipend amount to be determined. Might be considered placeholder? 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. The Pay section we have includes "tax-free stipend amount to be determined". That is somewhat vague but it's still stating that there is a tax-free stipend, amount to be determined. It's not exactly "not specified" but similar. However the posting explicitly says that, so we must preserve ALL substantive information. So we keep it. Now check if any section is thin: Requirements has many items, good. About the role has two paragraphs. Pay has one sentence. Schedule has one sentence. Could we combine Pay and Schedule into Requirements? But they said prefer few substantive sections over many thin ones. Pay and Schedule are each one sentence; maybe we could combine them into a "Compensation & Schedule" section but not in allowed headings. However we could keep them as separate sections; they are thin but still substantive. The instruction says prefer a few substantive sections over many thin ones; but we already have About the role and Requirements as substantive; Pay and Schedule are thin but still needed to preserve info. Could we merge Pay and Schedule into Requirements? That would make Requirements longer but then we lose separate headings. However the instruction says use those headings for sections; we can still have Pay and Schedule sections if they have real specific content. They do. So it's okay. Now ensure we didn't include any duplicated lines. The posting had "Access Healthcare Job ID #80484861." and also "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." No duplication. Now output only HTML fragment, no /, no markdown fences. Thus final output:About the role
Access Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Muskegon, Michigan.
Access Healthcare aims to provide superior service to our nursing family by providing around the clock support, competitive pay packages and an unmatched benefits package! Unlike other agencies, we offer a true family feel and work with you to find the placement that is right for you. We offer one of the top leading pay packages in the industry and we are ready to get you the money you deserve! Access Healthcare was founded by two travel nurses, Danielle and Diego, who had a dream and a shared vision of creating an agency which all nurses would want to work with. Our passion has led us to where we are today as one of the top 10 agencies in our home state of New Jersey, with access to contracts in all 50 states! We encourage you to join our team and we cannot wait to get to know you!