Director – EDIFECS Healthcare EDI Core Admin Platform

We need to produce HTML fragment with sections: About the role (maybe "About the job"? The posting has "About the job" then "WHO WILL BE SUCCESSFUL IN THIS ROLE?" then "ROLE OVERVIEW". We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real, specific content. We have content for About the role (the description), Responsibilities (KEY RESPONSIBILITIES), Requirements/Qualifications (REQUIRED QUALIFICATIONS, PREFERRED QUALIFICATIONS maybe combine?), Skills (maybe not separate but we can include under Qualifications). There's no explicit Benefits, Pay, Schedule. So we should not include those sections. We need to preserve all substantive info, not invent. Remove boilerplate like location line? The location line "About the jobLocation: Remote – United StatesExperience: 15+ YearsDomain: Healthcare Payer / HealthPlanCore Technology: Edifecs | X12 EDI | J2EE | MongoDB | PostgreSQL | Oracle | AI-Assisted Development". This is metadata; we can fold minor metadata into a short

or drop it. Probably we can include a short paragraph summarizing location, experience, domain, core tech. But we must not repeat job title as heading. We can include a

with that info. We need to output only HTML fragment, no /, no markdown fences. Structure:

Remote – United States | 15+ Years Experience | Healthcare Payer / Health Plan | Core Technology: Edifecs, X12 EDI, J2EE, MongoDB, PostgreSQL, Oracle, AI-Assisted Development

Then sections:

About the role

with paragraphs from "WHO WILL BE SUCCESSFUL IN THIS ROLE?" and "ROLE OVERVIEW". Combine. We need to preserve all substantive info: The text under "WHO WILL BE SUCCESSFUL IN THIS ROLE?" includes description of ideal candidate. Then "ROLE OVERVIEW" includes description. We'll put them in

elements. Then

Responsibilities

with

• each bullet from KEY RESPONSIBILITIES. Then

  Qualifications

  maybe combine Required and Preferred. Could split into Required Qualifications and Preferred Qualifications as separate sections? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading and inside we can have required and preferred as paragraphs or lists. Probably better to have

  Qualifications

  then

  Required:

  then
  etc. But we must not create filler sections. We have content for qualifications. We could also have

  Requirements

  for required qualifications and

  Skills

  for preferred? But the instruction says prefer few substantive sections over many thin ones. So maybe one Qualifications section containing both required and preferred. We'll output:

  Qualifications

  Required:

  ...

  Preferred:

  ...
  But need to ensure we use

  for prose,

  • for lists. We must not repeat job title as heading. Good. We must not include Job ID/requisition numbers. We must not include boilerplate like EEO etc. Not present. Now extract content. Let's copy the relevant sections. About the job location line: "About the jobLocation: Remote – United StatesExperience: 15+ YearsDomain: Healthcare Payer / HealthPlanCore Technology: Edifecs | X12 EDI | J2EE | MongoDB | PostgreSQL | Oracle | AI-Assisted Development" We'll format as a paragraph. Now "WHO WILL BE SUCCESSFUL IN THIS ROLE?" text: "We are looking for a senior technology leader who has progressed into Director-level responsibilities without moving away from the technology. You should bring deep U.S. healthcare payer experience and current, hands-on Edifecs expertise. You must be equally comfortable leading client and executive conversations and getting into the details of Edifecs configurations, X12 transaction flows, integration issues, and technical designs. This role is best suited for someone who combines three strengths: deep healthcare payer knowledge, hands-on Edifecs expertise, and strong client-facing technology leadership." Then "ROLE OVERVIEW": "We are looking for a Director – EDIFECS to serve as the primary client-facing technology leader for the EDI integration layer of a large healthcare core administration platform.This is a hands-on technology leadership role, not a purely managerial position. You will own solution design and requirements translation with client business, compliance, and technical stakeholders while providing technical leadership to distributed onshore/offshore Edifecs teams. You will also be expected to personally understand, review, and validate the technical build." We'll combine into maybe two paragraphs. Now responsibilities list: - Serve as the primary client-facing technology leader for Edifecs-based EDI integration across claims, eligibility, enrollment, encounters, and remittance - Own end-to-end design of Edifecs trading-partner configurations, transaction maps, and validation rules for X12 transactions including 270/271, 834, 835/837, 275, and 276/277 - Lead requirements-gathering and solution-design sessions with client business, compliance, and technical stakeholders - Translate complex regulatory, payer, and trading-partner requirements into Edifecs technical specifications - Review and validate completed Edifecs configurations and technical builds before production go-live - Provide technical leadership and mentorship to distributed Edifecs teams, reviewing designs, code, and configurations for quality and compliance - Own escalation and resolution of complex production issues across Edifecs EDI flows - Coordinate across client, offshore, architecture, and platform teams to resolve technical and delivery challenges - Partner with architecture and platform teams to align Edifecs integration with the broader core administration platform and modernization roadmap - Define and enforce standards for Edifecs configuration management, version control, testing, and change management - Mentor Leads and Analysts to drive delivery excellence and technology growth - Serve as a trusted technology advisor to client stakeholders - Own status reporting and risk/issue communication to client stakeholders and program leadership - Drive responsible adoption of AI-assisted engineering practices across the Edifecs team Now required qualifications: - Bachelor's degree in Computer Science, Engineering, or a related field - 15+ years of healthcare EDI/integration experience - Deep, current, hands-on expertise with the Edifecs product suite, including SpecBuilder, XEngine, Transaction/EDI Gateway, and Encounter Management - Strong hands-on J2EE experience for customizing and extending Edifecs and related integration components - Strong experience with MongoDB, PostgreSQL, and Oracle databases supporting EDI/integration platforms - Deep working knowledge of HIPAA X12 transactions: 270/271 – Eligibility 834 – Enrollment 835/837 – Remittance Advice / Claims 275 – Claim Attachments 276/277 – Claim Status Inquiry / Response - Proven experience leading Edifecs implementations end-to-end, from requirements and solution design through production go-live - Significant experience within a U.S. healthcare payer / health-plan environment - Strong understanding of healthcare compliance and regulatory requirements affecting EDI transactions, including HIPAA and CAQH CORE operating rules - Experience directly managing client relationships and leading distributed onshore/offshore technical teams - Strong executive-level verbal and written communication skills, including presenting technical solutions, risks, and recommendations to client and compliance stakeholders Now AI Knowledge & AI-Assisted Development section: It's under "AI KNOWLEDGE & AI-ASSISTED DEVELOPMENT". This is additional qualification content. Should we include under Qualifications? Probably yes, as part of required qualifications. The text: "Practical experience with AI-assisted engineering is required.The successful candidate should be able to: • Use AI coding and assistant tools to accelerate Edifecs mapping/transformation development, J2EE customization, testing, and technical documentation • Critically review and validate AI-generated maps, code, and configurations for technical correctness and regulatory compliance before deployment • Define and enforce responsible AI usage standards across the team • Ensure PHI, member information, and other sensitive healthcare data are never entered into unauthorized external AI tools or prompts • Identify opportunities where AI-driven automation can improve EDI mapping, testing, documentation, and overall engineering efficiency • Champion appropriate AI-assisted approaches as part of broader platform modernization initiatives" We should include these bullet points under required qualifications (maybe as a sublist). We'll incorporate. Now preferred qualifications: - Direct experience working for or with a health plan/payer organization - Experience with healthcare core administration platforms such as Facets, QNXT, or HealthRules - CAQH CORE certification or strong hands-on operating-rule compliance experience - Experience integrating Edifecs with mainframe or cloud-based core administration platforms - Relevant Edifecs product certifications - Oracle or PostgreSQL certifications Now we need to output HTML. We'll have:

    Remote – United States | 15+ Years Experience | Healthcare Payer / Health Plan | Core Technology: Edifecs, X12 EDI, J2EE, MongoDB, PostgreSQL, Oracle, AI-Assisted Development

    About the role

    We are looking for a senior technology leader who has progressed into Director-level responsibilities without moving away from the technology. You should bring deep U.S. healthcare payer experience and current, hands-on Edifecs expertise. You must be equally comfortable leading client and executive conversations and getting into the details of Edifecs configurations, X12 transaction flows, integration issues, and technical designs. This role is best suited for someone who combines three strengths: deep healthcare payer knowledge, hands-on Edifecs expertise, and strong client-facing technology leadership.

    We are looking for a Director – EDIFECS to serve as the primary client-facing technology leader for the EDI integration layer of a large healthcare core administration platform. This is a hands-on technology leadership role, not a purely managerial position. You will own solution design and requirements translation with client business, compliance, and technical stakeholders while providing technical leadership to distributed onshore/offshore Edifecs teams. You will also be expected to personally understand, review, and validate the technical build.

    Responsibilities

    • Serve as the primary client-facing technology leader for Edifecs-based EDI integration across claims, eligibility, enrollment, encounters, and remittance
    • Own end-to-end design of Edifecs trading-partner configurations, transaction maps, and validation rules for X12 transactions including 270/271, 834, 835/837, 275, and 276/277
    • Lead requirements-gathering and solution-design sessions with client business, compliance, and technical stakeholders
    • Translate complex regulatory, payer, and trading-partner requirements into Edifecs technical specifications
    • Review and validate completed Edifecs configurations and technical builds before production go-live
    • Provide technical leadership and mentorship to distributed Edifecs teams, reviewing designs, code, and configurations for quality and compliance
    • Own escalation and resolution of complex production issues across Edifecs EDI flows
    • Coordinate across client,