EDI Implementation Analyst II

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections where posting has real specific content. We need to extract content: The job description includes many paragraphs. We need to separate into sections: About the role (maybe overview), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID. We need to remove boilerplate: cookie/navigation/legal/EEO etc. There's none obvious. Also remove duplicated lines, application instructions, etc. The posting includes "Next steps: After you apply..." and interview process details, camera usage etc. Those are application instructions; we should remove them. Also "Sponsorship, in any form, is not available for this position." Might be considered metadata; but it's not a heading; we can keep as short p maybe. We need to preserve all substantive information. So we need to include details about role, responsibilities, qualifications, etc. We need to decide sections: - About the role: could be introductory paragraph about Availity and role overview. The posting starts with description of Availity, mission, then "Reporting to the Manager, Health Plan Implementation Analysts, the EDI Implementation Analyst II role is technical..." That's about the role. So we can put that in About the role. - Responsibilities: list of duties. The posting has many bullet-like sentences under "Key responsibilities include, but are not limited to a) managing internal and external relationships..." then later sections: "What You Will Be Doing Solutions Integration Implementation Planning", "Implementation Tracking And Execution", "Resource Coordination", "Customer Relationship Management", "Operations Support Process Documentation And Improvement", "Customer Support and Issue Resolution". Those are responsibilities. We can combine into a

• list. - Requirements: maybe "To Be Qualified For The Role, You Have ..." includes bullet list of qualifications: Bachelor's degree or equivalent work experience, 4+ years related experience, etc. That's requirements. - Qualifications: maybe overlapping with requirements; but we could separate "Qualifications" as the list of knowledge/skills: Knowledge of health care industry, HIPAA, X12 transactions, ability to create test plans, documentation, etc. The posting includes many "Ability to..." statements. Those could be Skills. - Skills: maybe the "Ability to..." and "Experience with Submitters..." etc. - Benefits: The posting includes "Why Work On This Team" and "Availity Culture And Benefits" describing benefits: competitive salary, bonus structure, generous HSA company contribution, healthcare, vision, dental benefits, 401k match, unlimited PTO, 9 paid holidays, wellness reimbursement up to $250/year, education reimbursement, Paid Parental Leave, community involvement. Also mentions certified Great Place to Work etc. So we can include Benefits section. - Pay: Not explicitly stated; only "competitive salary". That's vague; we should not create Pay section unless posting actually states them. It says "competitive salary" but no numbers. The instruction: 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. "competitive salary" is vague but still states something; but it's not a specific number. Might be considered placeholder? The instruction says avoid filler like "commensurate with experience". "competitive salary" is similar vague. Safer to not include Pay section. - Schedule: Not mentioned; remote US. No schedule specifics. So omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications (maybe combine with Requirements?), Skills, Benefits. We need to avoid duplication. Let's extract content precisely. First, About the role: combine the introductory paragraphs up to "Reporting to the Manager, Health Plan Implementation Analysts, the EDI Implementation Analyst II role is technical in nature and requires a strong understanding of the interaction between the Availity systems and Availity customers, primarily from a receiver perspective." Also maybe include mission statement. We'll keep substantive. Responsibilities: gather all duty sentences. Let's list responsibilities from text: - managing internal and external relationships with payers and vendors to meet integration objectives set by Program Management; - creating appropriate documented deliverables, managing deliverables, gaining agreement from internal and external partners; - coordinating partner awareness on Availity functionality as requested by Program Management and production issues as requested by internal teams, including but not limited to Operations support team and/or Information Technology team. Then under "What You Will Be Doing Solutions Integration Implementation Planning": - Accountable for all complexity level implementations, including but not limited to submitters, partners, and vendors; to exchange all transaction types through methods such as EDI, B2B, web transactions, API, and others as defined implementations. - Tasks involve managing client timelines and deliverables, issue resolution, file transmission, response reporting, testing and results delivery based on customer requirements using Availity processes and tools - Acts under the guidance of the Level III EDI Implementation Analysts - Will be responsible for Analyst level tasks of all implementations. Including, but not limited to, developing the implementation plan for all new implementation requests (direct receiver/payer, and partner and vendor), initiating implementation plan with customer, creating all tickets required to execute implementation plan completely. Implementation Tracking And Execution: - Manages multiple moderate to complex implementations, including timelines, issue resolution and results delivery using Availity standard tools and processes - Assesses and analyzes moderately complex standard and non-standard implementations, including HIPAA rules and Availity standards and options and follows processes accordingly - In partnership with external and internal stakeholders, the EDI Implementation Analyst II conducts pre-production functional testing protocols, including creating and executing test plans for the implementation - Tracks progress of specific implementation projects via Availity tools including JIRA, Confluence and Salesforce Resource Coordination: - Mentors EDI Implementation Analysts to ensure projects are completed on a timely basis and ensures Availity standards are followed. - Interacts with Payer/Trading Partner, Vendor and Provider Marketing, Business Development, Business Technology Solutions, Product Management, Finance, and Operations - Communication and coordination between all Availity platforms- (HEW, Patient Access, RCM) - The EDI Implementation Analyst II will be engaged in providing estimates of work for implementations for submitters, partners and vendors when required. - The EDI Implementation Analyst II is responsible for managing the workflow of moderate to complex implementations and any other responsibilities of the EDI Implementation Analyst II and ensuring all commitments are maintained. Customer Relationship Management: - Interacts with business, technical, internal and external resources on new and existing implementation solutions and partners. - The EDI Implementation Analyst II will be required to represent the company in a professional manner to external customers with supervision as needed. - Assists the Channels Sales, Account Management, and Payer Solutions staff in finalizing opportunities by providing technical guidance to external stakeholders. - Ensures market validation (utilization) of solution by driving clean hand off to account management or operational support teams. - Communicates new implementations and all related changes including detailed specifications - Monitors customer communications (submitter, payer, trading partners, etc) to be apprised of any changes that may impact business operations (new edits, connectivity updates, system downtime) - Interacts closely with other technology teams and development staff to ensure requirements able to be met accurately and executed within the expected timeline for the implementations. Operations Support Process Documentation And Improvement: - Leads in the development of Availity support documentation (such as production issues, impact and solutions as it relates to the responsibilities of the EDI Implementation Analyst II). - Documents moderately complex standard processes (such as standard testing procedures) as necessary for continuous process improvement - Responsible for documenting all information related to assigned implementations. Including but not limited to submitter and partner and vendor implementations, such as requirements, test plans, contact information, escalation procedures, etc. - Supports process improvement of workflow, endeavors to stay current with technology trends, industry standards, and Availity strategy – specifically driving close to cash process for faster and higher quality connectivity solutions. Customer Support and Issue Resolution: - This role is required to provide support to EDI Implementation Analyst II for operational issues where assistance is needed. - Supports organization through researching, resolving and documenting operational issues. - Must be able to communicate simple to medium business, technical, and HIPAA issues and resolutions - Supports and maintains implementations by execution of customer maintenance requests including but not limited to change requests, connectivity changes, and edit and enrichment enhancements. - Responsibilities of support for an EDI Implementation Analyst II include but are not limited to the migration of clearinghouse partner configurations, migration of clearinghouse partner specification documentation, configuration of alternate routes for submitters. - EDI Implementation Analyst IIs will also be responsible for updating and maintaining payer routing and the payer list to ensure data is accurate. Including validation of payer routes to guarantee satisfaction. We'll turn each bullet into
• . Now Requirements: "To Be Qualified For The Role, You Have Bachelor’s degree or the equivalent work experience 4+ years of related experience in a technology (information exchange) and/or healthcare environment 4+ years of experience with managing simple to moderately complex implementations and delivering results with speed, accountability, and trust Knowledge of the health care industry specifically claims processing systems, provider office operations, and customer service processes in a health care company Understanding of HIPAA implementation guides for claim and other transactions Knowledge of the health care industry HIPAA mandated ANSI transaction formats. Must have a working knowledge of X12 transactions specifically 837P, 837I, 835, 270/271, 276/277, 278, CCR/CCD Ability to create and execute test plans Ability to create documentation such as training resources and reference materials Ability to establish and maintain effective working relationships, supporting internal and external partners Excellent written and verbal communication skills including strong presentation skills and the ability to present executive summaries in a concise manner Ability to effectively manage multiple priorities in a fast-paced environment Flexibility and ability to embrace change Ability to prepare documented customer requirements Experience with Submitters, Vendors and/or Receivers/Payers is a plus Customer service and/or relationship management experience is a plus Experience in software implementations is a plus" We need to separate into Requirements (maybe mandatory) and Qualifications (maybe knowledge) and Skills (abilities). But we can combine. Given instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including qualifications and skills), Benefits. But we need to use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those we have content for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We must not create empty sections. Thus we need to split the content into these categories. Let's define: - About the role: overview of company and role. - Responsibilities: list of duties (as above). - Requirements: mandatory qualifications: Bachelor's degree or equivalent work experience, 4+ years related experience in technology/healthcare, 4+ years experience managing simple to moderately complex implementations, knowledge of healthcare industry claims processing etc., understanding of HIPAA implementation guides, knowledge of HIPAA mandated ANSI transaction formats, working knowledge of X12 transactions list. - Qualifications: maybe the "Ability to create and execute test plans", "Ability to create documentation such as training resources and reference materials", "Ability to establish and maintain effective working relationships", "Excellent written and verbal communication skills...", "Ability to effectively manage multiple priorities...", "Flexibility and ability to embrace change", "Ability to prepare documented customer requirements". These are abilities/qualifications. - Skills: maybe the "Experience with Submitters, Vendors and/or Receivers/Payers is a plus", "Customer service and/or relationship management experience is a plus", "Experience in software implementations is