Jobs · Healthcare · Missouri

Patient Access Representative -PT

Southeast Hospital · Cape Girardeau, MO · 3 wk ago
HealthcarePart-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the description. Given text: "JOB_DESCRIPTION.SHARE.HTML CAROUSEL_PARAGRAPH JOB_DESCRIPTION.SHARE.HTML Cape Girardeau, MissouriSupport ServicesSupport ServicesRegularPart-timeMercy Hospital SoutheastJR271707 mail_outline Get future jobs matching this search or Job Description Find your calling at Mercy! The Patient Access Representative is often the first point of contact for our patients and therefore must represent Mercy with the highest standard of customer service, compassion and perform all duties in a manner consistent with our mission, values and Mercy Service Standards. The Patient Access Representative will facilitate all components of the patient's entrance into any Mercy facility. This may include scheduling, registration, benefit verification, pre-certification and financial clearance including pre-visit collection. The Patient Access Representative will be responsible for ensuring that the most accurate patient data is obtained and populated into the patient record. This co-worker must have an exceptional attention to detail and maintain knowledge and competence with insurance carriers, Medicare guidelines as well as federal, state and accreditation agencies. Position Details Mercy Patient Access Representative, Part-Time (20 hrs week) Shifts: Weekends, Holidays, Varies/Rotating Experience And Education Requirements 1-3 years clerical experience and customer service experience preferred. Experience with medical terminology and insurance plans preferred. High School diploma required; some college helpful. Minimum Skills, Knowledge And Ability Requirements Ability to communicate effectively both orally and in writing, excellent telephone etiquette required. Ability to establish and maintain positive working relationships with patients, physicians, clinical and non-clinical hospital staff and insurance companies. Strong organizational skills; attention to detail. Ability to work under stress, meet deadlines and perform all daily assignments with a high level of accuracy. Knowledgeable and experienced with various computers systems; Ability to use a 10-key calculator and computer keyboard. Physical Requirements Position requires the ability to push, pull, and/or lift 50 lbs on a regular basis. Position requires prolonged standing and walking during each shift. Position requires the ability to grip, reach, bend, kneel, twist, and squat to perform duties. Why Mercy? From day one, Mercy offers outstanding benefits - including medical, dental, and vision coverage, paid time off, tuition support, and matched retirement plans for team members working 32+ hours per pay period. Join a caring, collaborative team where your voice matters. At Mercy, you'll help shape the future of healthcare through innovation, technology, and compassion. As we grow, you'll grow with us. keyword(s): PAR, PSR, Customer Service, Scheduler" We need to extract sections. We have: - About the role: maybe the introductory paragraph: "Find your calling at Mercy! The Patient Access Representative is often the first point of contact..." That's about role. - Responsibilities: list of duties: facilitating patient entrance: scheduling, registration, benefit verification, pre-certification, financial clearance including pre-visit collection; ensuring accurate patient data; etc. - Requirements: Experience and Education Requirements: 1-3 years clerical experience and customer service experience preferred; experience with medical terminology and insurance plans preferred; High School diploma required; some college helpful. - Qualifications? Might be same as requirements. But we can combine. - Skills: Minimum Skills, Knowledge And Ability Requirements: communication, telephone etiquette, relationships, organizational skills, attention to detail, work under stress, meet deadlines, accuracy, computer systems, 10-key calculator. - Physical Requirements: push/pull/lift 50 lbs, prolonged standing/walking, grip, reach, bend, kneel, twist, squat. - Benefits: "Why Mercy? From day one, Mercy offers outstanding benefits - including medical, dental, and vision coverage, paid time off, tuition support, and matched retirement plans for team members working 32+ hours per pay period." - Pay: Not specified. No pay info. So we should NOT include Pay section. - Schedule: "Position Details Mercy Patient Access Representative, Part-Time (20 hrs week) Shifts: Weekends, Holidays, Varies/Rotating". That's schedule info. So we can include Schedule section. We must not include placeholder like "varies" as filler? The schedule includes "Varies/Rotating". That's actual content. It's okay. We need to output only HTML fragment, no /, no markdown. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. So we won't put "Patient Access Representative" as heading. We need to not put Job ID/requisition numbers as headings; we can drop them. We need to include a section only when posting has real specific content; never emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". For schedule we have specifics: Part-Time (20 hrs week) Shifts: Weekends, Holidays, Varies/Rotating. That's specific enough. For benefits we have specifics. For pay we have none, so omit. Now craft sections. Potential sections: - About the role (maybe "About the role") with prose. - Responsibilities (list) - Experience and Education Requirements (maybe "Requirements") list. - Skills (list) - Physical Requirements (list) - Benefits (list) - Schedule (maybe prose or list? Could be prose.) We need to decide headings exactly as per allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role", "Responsibilities", "Requirements", "Skills", "Physical Requirements" (but not in list; maybe we can treat as "Requirements" includes physical? But we have separate physical requirements; we could put under "Requirements" or create a separate "Physical Requirements" but not in allowed headings. The allowed headings list does not include Physical Requirements. However we can still include a section if we think it's needed? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings; we can create other headings if needed but better to map physical requirements under "Requirements" or "Skills". Physical requirements could be under "Requirements". We'll include them as part of Requirements list. Similarly, we might not need Qualifications separate; we can combine with Requirements. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. We need to ensure we don't create empty sections. Now extract content. About the role: "Find your calling at Mercy! The Patient Access Representative is often the first point of contact for our patients and therefore must represent Mercy with the highest standard of customer service, compassion and perform all duties in a manner consistent with our mission, values and Mercy Service Standards." We could also include the sentence about facilitating components? That's more responsibilities. So keep about role as that. Responsibilities: list: - Facilitate all components of the patient's entrance into any Mercy facility (scheduling, registration, benefit verification, pre-certification, financial clearance including pre-visit collection) - Ensure that the most accurate patient data is obtained and populated into the patient record We could also include "maintain knowledge and competence with insurance carriers, Medicare guidelines as well as federal, state and accreditation agencies." That's more requirement? Might be responsibility? It's about knowledge. Could be under Requirements. We'll keep responsibilities as those two bullet points. Requirements: list: - 1-3 years clerical experience and customer service experience preferred - Experience with medical terminology and insurance plans preferred - High School diploma required; some college helpful - Ability to communicate effectively both orally and in writing, excellent telephone etiquette required - Ability to establish and maintain positive working relationships with patients, physicians, clinical and non-clinical hospital staff and insurance companies - Strong organizational skills; attention to detail - Ability to work under stress, meet deadlines and perform all daily assignments with a high level of accuracy - Knowledgeable and experienced with various computer systems; Ability to use a 10-key calculator and computer keyboard - Maintain knowledge and competence with insurance carriers, Medicare guidelines as well as federal, state and accreditation agencies But note some of these overlap with Skills. We need to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all info, but we can organize logically; duplication may be okay if it's in original? The original had separate sections: Experience And Education Requirements, Minimum Skills, Knowledge And Ability Requirements, Physical Requirements. So we should reflect those. Thus we can have: - Requirements (Experience and Education) list: 1-3 years clerical experience and customer service experience preferred; Experience with medical terminology and insurance plans preferred; High School diploma required; some college helpful. - Skills list: Ability to communicate effectively both orally and in writing, excellent telephone etiquette required; Ability to establish and maintain positive working relationships with patients, physicians, clinical and non-clinical hospital staff and insurance companies; Strong organizational skills; attention to detail; Ability to work under stress, meet deadlines and perform all daily assignments with a high level of accuracy; Knowledgeable and experienced with various computers systems; Ability to use a 10-key calculator and computer keyboard. - Physical Requirements list: Position requires the ability to push, pull, and/or lift 50 lbs on a regular basis; Position requires prolonged standing and walking during each shift; Position requires the ability to grip, reach, bend, kneel, twist, and squat to perform duties. But the allowed headings do not include Physical Requirements; we could incorporate physical requirements under Requirements or Skills. However to preserve all info, we need to include them somewhere. We could add a section "Physical Requirements" even if not in the example list; the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list; we can use other headings if needed. But better to follow the pattern: we could put physical requirements under "Requirements" as a sub-list? But we need to use
    • for any list. We could have a

      Requirements

      then inside have multiple
        groups? That's okay. We can structure:

        About the role

        ...

        Responsibilities

        • ...
        • ...

        Requirements

        Experience and Education

        ... but we cannot use

        unless allowed? Not prohibited but we should stick to

        for section headings. Could use

        for subheadings? Might be okay to just list all requirements in one list, mixing experience, skills, physical. But that may lose clarity but still preserves all info. Better to keep separate sections: Requirements (Experience and Education), Skills, Physical Requirements, Benefits, Schedule. But the instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It does not forbid other headings; it's just examples. So we

Similar jobs