Jobs · Administrative · Virginia

Physician Practice Coordinator - Ortho Trauma - Full Time First Shift

Valley Health · Winchester, VA · 4 days ago
Administrative$22.71–$34.06/hrFull-time
The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - About the role (the job description) - Responsibilities (from the job description) - Requirements/Qualifications (education, experience, certifications, qualifications) - Benefits (clearly listed) - Pay (mentioned as "Pay Range $22.71 - $34.06") - Schedule (mentioned as "Work Shift" but no details given, just "Work Shift" label) The job title is "Physician Practice Coordinator" but I should not repeat it as a heading per instructions. The department and worker sub type and job ID are metadata - I should fold minor metadata into a short

or drop it. The job ID "209596" and department "Ortho Trauma PBB" could be in a brief paragraph. The pay range is given: $22.71 - $34.06. That's specific, so I should include a Pay section. Schedule: "Work Shift" is listed but no details (like day/night, hours). The posting says "Work Shift" but no actual shift info. Might be a label without value. I should not create a Schedule section unless actual schedule info is present. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." For Pay, it states a range. For Schedule, it just says "Work Shift" with no details. I'll omit Schedule section. Benefits are clearly listed, so include Benefits section. Now, structure: - About the role: the introductory paragraph about Valley Health and the role summary. - Responsibilities: bullet points from the job description. - Requirements: could combine Education, Experience, Certification & Licensures, Qualifications into one section or separate. The rules say use headings like Requirements, Qualifications, Skills. I'll create a "Requirements" section with sub-lists for Education, Experience, Certifications, and other Qualifications. But the rule: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I can have separate headings for Education, Experience, etc., but they are sub-sections. However, the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into "Requirements" with sub-lists using
    but not sub-headings. But the rule says use

    for section headings. Could use

    for "Requirements" and then within that, use
      with nested lists? But the rule says use
      • for any list of duties/requirements/benefits. It doesn't forbid nested lists. However, to keep it simple, I'll create a "Requirements" section with bullet points covering education, experience, certifications, and qualifications. But the qualifications are a list of knowledge/skills. Might be better to have "Qualifications" as separate heading. Let's see the example headings: Requirements, Qualifications, Skills. They are separate. The posting has "Education", "Experience", "Certification & Licensures", "Qualifications". I'll map: - Education -> part of Requirements - Experience -> part of Requirements - Certification & Licensures -> part of Requirements - Qualifications -> separate "Qualifications" heading (since it's a list of knowledge/skills) But the rule: "include a section ONLY when the posting has real, specific content for it". All have content. I'll do: - About the role - Responsibilities - Requirements (with subsections for Education, Experience, Certifications) - Qualifications (the list under Qualifications) - Benefits - Pay Also, there's a brief intro about Valley Health. That could be part of About the role. Now, metadata: Department Ortho Trauma PBB - 209596 Worker Sub Type Regular Work Shift Pay Range $22.71 - $34.06. I'll put the department and worker type in a short paragraph at the top or bottom. Since the page already shows job title, maybe include a

        with "Department: Ortho Trauma PBB | Worker Sub Type: Regular | Job ID: 209596". But the rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So I'll include a

        with that metadata. Now, write HTML. Let's draft:

        Department: Ortho Trauma PBB | Worker Sub Type: Regular | Job ID: 209596

        About the role

        As one of the nation's Top 15 Health Systems, recognized by Premier and Modern Healthcare, Valley Health is a place where excellence, compassion, and purpose come together. This distinction reflects our commitment to exceptional patient care, clinical quality, and the caregivers who make it all possible.

        The Physician Practice Coordinator is an entry-level managerial role to physician practices, with a primary responsibility of assisting the Practice Manager in the day-to-day operations of the physician practice to maximize patient access and provider efficiency for their assigned practice locations. The position requires the Coordinator to assist as the liaison between management and clerical and clinical staff in the physician office. In coordination with the Practice Manager, will maintain a stable work environment for all staff and handle duties as outlined, oversight of daily operations of office and staffing, participate in the establishment and maintenance of the operating budget, resolution of patient complaints, coordination of office meetings, participate in the annual staff performance appraisals, as well as training and coaching of staff, assist with orientation/training of new staff and assist with building and maintaining a cohesive and positive work environment. The Coordinator will assist with patient care as designated by the provider(s) and as licensed and/or certified in a clinical role. The Coordinator will be proficient in EPIC processes to assist in training and maintain efficient medical practice operations. The Coordinator will represent and be a role model for other employees in attendance, handling and having difficult conversations, leadership and handling multiple priorities at any given time.

        Responsibilities

        • Assist the Practice Manager in day-to-day operations of the physician practice to maximize patient access and provider efficiency
        • Serve as liaison between management and clerical/clinical staff
        • Maintain a stable work environment for all staff
        • Oversee daily operations of office and staffing
        • Participate in establishment and maintenance of the operating budget
        • Resolve patient complaints
        • Coordinate office meetings
        • Participate in annual staff performance appraisals
        • Train and coach staff
        • Assist with orientation and training of new staff
        • Build and maintain a cohesive and positive work environment
        • Assist with patient care as designated by providers and as licensed/certified
        • Maintain proficiency in EPIC processes to assist in training and maintain efficient operations
        • Represent and role model attendance, handling difficult conversations, leadership, and managing multiple priorities

        Requirements

        Education

        • High School Diploma or GED required
        • Associate or Bachelor's degree preferred

        Experience

        • 1-3 years of previous supervisory experience strongly preferred
        • Experience in a medical office setting strongly preferred

        Certifications & Licensures

        • Licensed Practical Nurse or Certified Medical Assistant preferred
        But the rule says use

        for section headings. It doesn't mention

        . Should I use

        for each subsection? The example headings list includes "Requirements, Qualifications, Skills". It doesn't say we can't use

        . But to be safe, maybe keep only

        headings. Could make "Education", "Experience", "Certifications & Licensures" as

        headings. But that would create many thin sections. The rule: "Prefer a few substantive sections over many thin ones." So better to keep "Requirements" as

        and use
          with nested lists or just bullet points with labels. However, the rule says "use
          • for any list of duties/requirements/benefits". It doesn't forbid using

            . But the instruction: "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies only those are section headings. So I should not create additional

            headings beyond those categories. But I can have subsections within Requirements using

            ? The instruction doesn't explicitly forbid, but says "use

            for section headings". It might be okay to use

            for sub-sections. However, to be safe, I'll keep only

            headings for the main sections, and within Requirements, I'll use a single list with categorized items, maybe using labels. But the rule says use
            • for any list. I can do:

              Requirements

              • Education: High School Diploma or GED required; Associate or Bachelor's degree preferred
              • Experience: 1-3 years of previous supervisory experience strongly preferred; Experience in a medical office setting strongly preferred
              • Certifications & Licensures: Licensed Practical Nurse or Certified Medical Assistant preferred
              That's clean. Then Qualifications section:

              Qualifications

              • Knowledge of basic patient care and ability to properly and safely handle medical equipment and supplies used
              • Ability to perform and/or have knowledge of basic clerical skills
              • Knowledge of Microsoft Office strongly preferred
              • Exceptional communication, both verbal and written
              • Excellent customer service skills for interaction with patients, visitors, and staff
              • Professional appearance required
              • Ability to function independently and as a team member
              • Flexible, dependable, and maintain a professional image
              • Tactful, maintain confidentiality, and handle stressful situations professionally
              Benefits:

              Benefits

              At Valley Health, we believe everyone is a caregiver, and our goal is to create an environment where our caregivers thrive physically, financially, and emotionally. In addition to a competitive salary, our most popular benefits for full-time employees include:

              • Zero-Deductible Health Plan
              • Dental and vision insurance
              • Generous Paid Time Off
              • Tuition Assistance
              • Retirement Savings Match
              • Robust Employee Assistance Program for emotional wellbeing
              • Membership to Healthy U: An Incentive-Based Wellness Program

              Valley Health also offers a health savings account & flexible spending account for childcare, life insurance, short-term and long-term disability, and professional development. Additional perks include discounts to on-campus dining and more. Visit valleyhealthbenefits.com for the full scale of benefits.

              Pay:

              Pay

              Pay Range: $22.71 - $34.06 per hour

              Note: The pay range is given as "$22.71 - $34.06" without specifying hourly/annual. Likely hourly. I'll include as is. Now, ensure no boilerplate, no EEO,

Similar jobs