Epic ODBA

We need to output only HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate, navigation, legal, EEO, scam-warning, duplicated lines, application instructions. Also remove Job ID/requisition numbers as headings. We need to parse the posting. Key sections: - Description: includes description paragraph about role. Could be "About the role" heading. - Responsibilities: list of bullet points. - Qualifications: includes Required Qualifications and Preferred Qualifications. Could be "Qualifications" heading with sub-sections? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put Qualifications heading and include both required and preferred as lists. - Skills: there is a "Skills" line: "Database administrator". Also there is "Job Type & Location" and "Pay And Benefits". Also "Workplace Type". Also "Application Deadline". Also "About TEKsystems" etc. But we need to remove boilerplate like About TEKsystems, equal opportunity, etc. Also remove "Application Deadline". Also remove "Job Type & Location" maybe we can include location under a short paragraph? The instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So location and job type can be in a paragraph. - Pay And Benefits: includes pay range and benefits list. So we need Pay and Benefits sections? The instruction: Prefer a few substantive sections over many thin ones. We could combine Pay and Benefits into one section? But they have separate headings allowed: Pay, Benefits. We could make a Benefits section and Pay section. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay range and benefits list. So we can have Pay and Benefits sections. - Schedule: not mentioned. So we should not create Schedule section. - Requirements: maybe we can include under Qualifications? There's a separate "Requirements" heading allowed. The posting has "Required Qualifications" and "Preferred Qualifications". Could treat as Requirements. But we already have Qualifications heading. Could use Requirements for required qualifications and Qualifications for preferred? But better to follow typical: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. However we have both Required and Preferred qualifications. Could put Requirements heading for required qualifications, and Qualifications heading for preferred qualifications. Or combine. We need to preserve all substantive info. Let's extract substantive content: Description paragraph: "The Epic Operational Database Administrator (ODBA) is a mission-critical, hands-on role responsible for the installation, performance, and reliability of the Epic IRIS Operational Database (ODB) hosted in Microsoft Azure. Operating in a high-volume, national-scale diagnostic laboratory environment, the ODBA will transition the system through its initial implementation, stabilize it during steady-state operations, and continuously optimize database performance. This role works closely with infrastructure teams, integration engineers, and Epic Beaker analysts to ensure massive daily volumes of clinical testing data flow with zero interruption and strict adherence to healthcare compliance standards (HIPAA, CLIA)." Responsibilities list: each bullet. - Install, configure, and provision all Epic database environments (Production, Reporting, Disaster Recovery, Training, and Build) within the Azure cloud environment. - Infrastructure as Code (IaC): Collaborate with cloud engineers to deploy and manage the underlying Azure database infrastructure using tools like Terraform to ensure consistent, scalable builds. - Execute rigorous volume testing to ensure the database can handle burst-heavy, high-throughput HL7v2 and FHIR API transactions from automated lab analyzers and middleware. - DR Configuration: Implement and validate multi-region disaster recovery, failover clusters, and backup protocols to guarantee near-zero downtime and strict data recoverability prior to go-live. - Monitor daily database health, server performance, I/O, and journaling to proactively identify bottlenecks and maintain high availability. - Execute routine Epic version upgrades, system updates (SUs), and security patches across all environments according to strict change management processes. - Serve in a 24/7 on-call rotation to provide advanced troubleshooting for database abends, slow query responses, data corruption, or severe system degradation. - Execute daily operational tasks, including database space management, user access control, log rotation, and validation of automated database backups. - Act as the primary technical liaison with Epic Technical Support (Epic TS) and InterSystems to coordinate maintenance windows and drive resolution of critical incidents. - processes to optimize responsiveness for rapid specimen accessioning, auto-verification, and integrated LIS workflows. (This sentence seems incomplete; maybe it's part of previous bullet? Actually it's a fragment: "Processes to optimize responsiveness for rapid specimen accessioning, auto-verification, and integrated LIS workflows." We'll keep as is.) - Monitor storage consumption and transaction trends to accurately forecast resource needs and right-size Azure compute/storage resources for cost efficiency and performance. - Design and execute database partitioning and historical lab-result archiving strategies to manage the rapid, compounding data growth typical of a national reference lab. - Process Automation: Develop and refine automation scripts to streamline repetitive DBA tasks, system monitoring alerts, and failover validation processes. Qualifications Required: - Active Epic ODBA certification is required with a proven track record of maintaining certifications across multiple Epic release cycles. - Minimum 7+ years of hands-on database administration experience managing InterSystems Caché/IRIS database environments, with a strong focus on enterprise-scale production systems. - Demonstrated experience of managing, monitoring, and performance-tuning databases supporting high volume concurrent users and extremely high transaction volumes. - Minimum 4 years of deep operational experience hosting and managing mission-critical Epic database workloads within Microsoft Azure, including advanced knowledge of Azure storage performance tiers and VM clustering. - Expert level experience designing, configuring, and executing failovers for multi-node, geographically distributed high-availability database configurations and complex disaster recovery plans. - Advanced Unix/Linux system administration skills (specifically Red Hat Enterprise Linux) with the ability to write sophisticated, production-grade automation scripts (e.g., Python, Bash, PowerShell) to manage large environment fleets. - Proven experience designing and validating backup and restore strategies for massive databases, ensuring zero data loss and minimal recovery time objectives under pressure. - Exceptional root-cause analysis skills with a demonstrated ability to diagnose and resolve complex database corruption, severe performance degradation, or system abends in real-time. - Commitment to participating in a flexible, 24/7/365 tier-3 escalations on-call rotation for critical database incidents. Preferred Qualifications: - Large Diagnostic/Lab Network Experience: 10+ years of sr.-level Caché/IRIS DBA experience, with specific experience in a national reference laboratory, massive multi-tenant healthcare system, or highly integrated diagnostic network. - Deep technical knowledge of optimizing and tuning IRIS databases specifically to support high-throughput Epic Beaker (Clinical and Anatomic Pathology) workflows and massive interface transaction loads. - Advanced experience automating database environment provisioning and configuration management using Terraform, Ansible, or similar enterprise-grade CI/CD pipelines. - Proven experience designing and implementing advanced database partitioning, purging, and historical archiving strategies to manage aggressive, high-volume laboratory data growth. - Prior experience serving as the Lead ODBA for a major, enterprise-wide Epic Go-Live, successfully guiding the database environment from build to steady-state optimization. - Active, advanced Microsoft Azure certifications (e.g., Azure Database Administrator Associate, Azure Solutions Architect, or DevOps Engineer Expert). Technical Training Or Professional Licensing: - Active Epic Operational Database Administrator (ODBA) Certification: Must hold an active, non-expired Epic ODBA certification (Required) - Epic New Version Training (NVT): Must be fully current on all Epic NVTs up to the organization's target Epic release version to ensure they are qualified to manage and upgrade the environment immediately upon hire. (Required) - InterSystems System Administration Certification (Preferred) Education: - Bachelor’s degree in Computer Science, Information Technology, Healthcare Administration, or equivalent professional work experience. (Required) - Master's degree in a technical or IT-related field. (Preferred) Travel required: Less than 25% Skills: "Database administrator" Job Type & Location: "This is a Permanent position based out of Dallas, TX." Pay And Benefits: pay range $100000.00 - $130000.00/yr. Then list of benefits. Workplace Type: "This is a fully remote position." Application Deadline: "This position is anticipated to close on Sep 25, 2026." About TEKsystems etc: boilerplate to remove. We need to output HTML fragment with sections: About the role (description), Responsibilities (ul), Qualifications (maybe split into Required and Preferred?), Skills (maybe just a p), Benefits (ul), Pay (p), maybe Location/Job Type as p. We must not include Schedule. We must not include Application Deadline (maybe considered metadata, can be folded into short p? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Application deadline is minor metadata; we could include in a short p under maybe a generic "Details" but we don't have a heading for that. Safer to drop it. Similarly, "Travel required: Less than 25%" could be minor metadata; we could fold into a p. "Technical Training Or Professional Licensing" could be part of Qualifications. "Education" also part of Qualifications. We need to preserve ALL substantive information; we cannot drop required qualifications like education, certifications, etc. So we must include them somewhere. Thus we need to include all those details under Qualifications heading (maybe with subheadings? But we cannot use headings other than allowed list. We could use

to separate paragraphs, and

• for lists. Thus under Qualifications heading we can have multiple paragraphs: Required Qualifications (list), Preferred Qualifications (list), Technical Training/Licensing (list), Education (list), Travel (p). That preserves all. Skills heading: we have "Database administrator". Could be a

  under Skills. Benefits heading: list of benefits. Pay heading: pay range. Location/Job Type: maybe under a heading? Not in allowed list. Could be a

  after Pay or before Benefits. Since we cannot create a heading for it, we just include a short paragraph. We must not repeat job title as heading. We must not include boilerplate like About TEKsystems, EEO, etc. Now construct HTML. Start with

  About the role

  then

  description.

  Then

  Responsibilities

  with each responsibility as
  • . Then

    Qualifications

    then we need sub-sections. We can use

    Required Qualifications:

    then
    etc. Or we can just directly list but preserve meaning. Use

    for headings inside? The instruction only restricts using

    for section headings; we can use other tags like

    with bold. That's fine. Thus:

    Qualifications

    Required Qualifications:

    ...

    Preferred Qualifications:

    ...

    Technical Training / Professional Licensing:

    ...

    Education:

    ...

    Travel: Less than 25%

    Then

    Skills

    Database administrator

    Then

    Pay

    The pay range for this position is $100000.00 - $130