Practice Liaison

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. We need to parse the description. Content: - Entity: Clinical Care Associates (CCA) - Penn Primary Care (PPC) and Penn Specialty Practices (PSP) of Penn Medicine Medical Group (PMMG) - Department: AR Project-Systems - Location: 150 Monument Road - Hours: Per Departmental Needs - Summary: The Practice Liaison supports the ambulatory practices in all aspects of Revenue Cycle to help ensure the long-term financial health of the entity. The Practice Liaison serves as the primary contact for all billing processes and accounts receivable issues. The practice liaison will assist in onboarding Revenue Cycle end users and play an integral role in Rev cycle end user professional development through the identification of workflow opportunities and optimization goal setting. The PL meets with each Rev Cycle user on a rolling quarterly basis to revenue Key Performance Indicators and assess practice level opportunities to establish short term and long term goals. In addition, the Practice Liaison must complete the Pennchart Professional Billing credentialing program and will be responsible to independently conduct Professional Billing Training classes as well as system update support via content updates and end user education and support. - Accountabilities: list many bullet-like sentences. We need to extract sections: maybe About the role (summary), Responsibilities (accountabilities), Requirements (education/experience), Qualifications (maybe preferred?), Skills (maybe not explicit), Benefits (some mention of benefits program), Pay (none), Schedule (Hours: Per Departmental Needs). We must only include sections with real specific content. Let's see: - About the role: we have Summary paragraph. That's good. - Responsibilities: we have Accountabilities list (many bullet points). Could treat as Responsibilities. - Requirements: Education/Experience: Required H.S. Diploma/GED and 2+ years’ experience in physician billing or healthcare industry; Preferred Bachelor's Degree. - Qualifications: maybe not separate; but we could combine with Requirements? The instruction says use headings for sections like Qualifications, Skills, etc. We could put Qualifications as maybe "Required and Preferred qualifications". But we already have Requirements. Might be okay to have both Requirements and Qualifications if content distinct. However we have only education/experience; no separate qualifications list. Could treat Requirements as the education/experience, and Qualifications maybe empty -> we should not include Qualifications heading if no specific content. So skip Qualifications. - Skills: Not explicitly listed; maybe implied but not explicit. Better to skip. - Benefits: There is a paragraph: "We believe that the best care for our patients starts with the best care for our employees. Our employee benefits programs help our employees get healthy and stay healthy. We offer a comprehensive compensation and benefits program that includes one of the finest prepaid tuition assistance programs in the region." That's specific enough? It mentions benefits program, prepaid tuition assistance. That's substantive. So we can include Benefits section with that paragraph. - Pay: No mention of salary/pay. So skip. - Schedule: Hours: Per Departmental Needs. That's specific. So include Schedule section with that sentence. Also we have Location and Department maybe could be part of About the role? But we could include them in About the role as metadata? The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include location, department, hours in a short paragraph under About the role or maybe as separate? Probably better to include them in About the role as a short paragraph after the summary. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from accountabilities etc. Must not lose any. We need to format lists with

• for any list of duties/requirements/benefits. So for Responsibilities (accountabilities) we need to turn each sentence into a list item. For Requirements (education/experience) we can list as list items. For Benefits we can list maybe as list items (though it's prose). Could also keep as

  . The rule: Use

  • for any list of duties/requirements/benefits, and

    for prose. So if we have a list, we must use ul/li. For benefits we have a paragraph describing benefits; not a list. Could keep as

    . For schedule we have a short sentence; could be

    . For location/department/hours we could include as

    . We must not repeat the job title as a heading. The job title is "Practice Liaison". Not used as heading. We must output only HTML fragment, no html/body tags, no markdown. Let's craft:

    About the role

    Entity: Clinical Care Associates (CCA) - Penn Primary Care (PPC) and Penn Specialty Practices (PSP) of Penn Medicine Medical Group (PMMG). Department: AR Project-Systems. Location: 150 Monument Road. Hours: Per Departmental Needs.

    The Practice Liaison supports the ambulatory practices in all aspects of Revenue Cycle to help ensure the long-term financial health of the entity. The Practice Liaison serves as the primary contact for all billing processes and accounts receivable issues. The practice liaison will assist in onboarding Revenue Cycle end users and play an integral role in Rev cycle end user professional development through the identification of workflow opportunities and optimization goal setting. The PL meets with each Rev Cycle user on a rolling quarterly basis to review Key Performance Indicators and assess practice level opportunities to establish short term and long term goals. In addition, the Practice Liaison must complete the Pennchart Professional Billing credentialing program and will be responsible to independently conduct Professional Billing Training classes as well as system update support via content updates and end user education and support.

    Responsibilities

    • Attends all required training sessions, maintains knowledge of systems, internally and externally as required.
    • Acts as a liaison between the practice and the Revenue Process department.
    • Provides support to 60 Accounts Receivable Representatives.
    • Responsible for knowing all issues affecting practice accounts receivable.
    • May travel to various practice locations in support of this goal.
    • Works with the Professional Billing Office and the Revenue Process department to maintain effective lines of communication regarding practice specific issues.
    • Facilitates resolution of billing office and practice/department issues to expedite claim submission and reimbursement.
    • Initiates Meet and Greets with all new Revenue Cycle Support Staff [10+ years]
    • Meets with each Revenue Cycle user quarterly to review department level [200+ departments].
    • Accounts receivable and denial data for quarterly department Revenue Cycle Meetings [60+/year].
    • Establishes short-term quarterly goals
    • Conducts and documents Shoulder to Shoulder Rev Cycle end user analysis to identify user strengths and opportunities – sets short term/long term goals [30+/year].
    • Monitors and/or analyzes practice accounts receivables.
    • Distribution of Monthly AR Facesheet Report
    • Provides support to gain a good understanding of the billing process.
    • Assists in performing analytical and statistical review of reimbursement trends, charge and payer mix through the use of EMR reports and other system tools for > 200 Epic departments, 300+ clinicians.
    • Serves as a resource to review, resolve and process complex accounts and disseminate the results to practice personnel.
    • Works carrier rebilling projects.
    • Maintains knowledge of the Revenue Process and makes recommendation for process improvement in accordance to changes in the healthcare industry.
    • Maintains knowledge of entity policies, billing procedures and health care industry standards.
    • Contribute and present to Rev Cycle Bi-Monthly Workshop agenda
    • Contribute to Rev Cycle Quarterly Newsletter publication
    • Epic APM Resolute PB trainer - conduct EPIC APM Resolute Professional Billing training classes - 60 classes per year approximately 75 learners per year.
    • Requires successful completion of the credentialed training program.
    • Responsible for training material updates and ongoing maintenance of classroom related materials consisting of five professional billing classes.
    • Facilitates EPIC APM Resolute Training Courses by supporting and mentoring PB Credential Training incumbents.
    • Is prepared for class and provides updated training material and documentation.
    • Assures efficient use of class time.
    • Presents suggestions for training material updates and collaborates with PBO training committee for approval and curriculum execution.

    Requirements

    • Required: H.S. Diploma/GED and 2+ years’ experience in physician billing or healthcare industry
    • Preferred: Bachelor's Degree

    Benefits

    We believe that the best care for our patients starts with the best care for our employees. Our employee benefits programs help our employees get healthy and stay healthy. We offer a comprehensive compensation and benefits program that includes one of the finest prepaid tuition assistance programs in the region.

    Schedule

    Hours: Per Departmental Needs

    Check we didn't miss any substantive info: The summary included "revenue Key Performance Indicators" originally had a typo "to revenue Key Performance Indicators". We corrected to "to review Key Performance Indicators". Must preserve original wording? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Changing "to revenue" to "to review" is altering meaning? The original: "The PL meets with each Rev Cycle user on a rolling quarterly basis to revenue Key Performance Indicators and assess practice level opportunities to establish short term and long term goals." Likely a typo; but we should keep as is? It says "to revenue Key Performance Indicators". That seems odd but it's part of the posting. We should preserve it exactly. So we should not "correct". Keep original phrase. Thus we need to keep that sentence exactly: "The PL meets with each Rev Cycle user on a rolling quarterly basis to revenue Key Performance Indicators and assess practice level opportunities to establish short term and long term goals." Also other bullet points: "Initiates Meet and Greets with all new Revenue Cycle Support Staff [10+ years]" keep as is. "Meets with each Revenue Cycle user quarterly to review department level [200+ departments]." keep. "Accounts receivable and denial data for quarterly department Revenue Cycle Meetings [60+/year]." keep. "Establishes short-term quarterly goals" keep. "Conducts and documents Shoulder to Shoulder Rev Cycle end user analysis to identify user strengths and opportunities – sets short term/long term goals [30+/year]." keep. "Distribution of Monthly AR Facesheet Report" keep. "Provides support to gain a good understanding of the billing process." keep. "Assists in performing analytical and statistical review of reimbursement trends, charge and payer mix through the use of EMR reports and other system tools for > 200 Epic departments, 300+ clinicians." keep. "Serves as a resource to review, resolve and process complex accounts and disseminate the results to practice personnel." keep. "Works carrier rebilling projects." keep. "Maintains knowledge of the Revenue Process and makes recommendation for process improvement in accordance to changes in the healthcare industry." keep. "Maintains knowledge of entity policies, billing procedures and health care industry standards." keep. "Contribute and present to Rev Cycle Bi-Monthly Workshop agenda" keep. "Contribute to Rev Cycle Quarterly Newsletter publication" keep. "Epic APM Resolute PB trainer -