Corepoint Interface Analyst

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes: Start Date: ASAP, Duration: Contract (6 Months, Extension Possible), Daily Working Hours: Full-Time, Travel: Hybrid – Up to 20% travel required, Work authorization: Must be eligible to work in the U.S. without company sponsorship, No Third Parties Please. Also later: "When working with Quoris as a consultant, you are eligible for competitive benefits including Health, Dental, Vision, 401k, and a great culture/working environment." So benefits info present. Pay not mentioned. Schedule: Daily Working Hours: Full-Time (so schedule info). Travel info maybe part of schedule? Could be separate but we only have headings defined; we could put travel under Responsibilities? But better to include Schedule section for Daily Working Hours: Full-Time. Travel maybe also schedule? Could include under Schedule as well. Benefits section present. Pay not present, so omit Pay heading. We need sections: About the role (maybe from Position Summary and Project Scope). Responsibilities (Key Responsibilities). Requirements (maybe Qualifications? Actually they have Qualifications and Preferred Qualifications. Could combine into Requirements and Qualifications? The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: Project Scope and Position Summary -> About the role. Key Responsibilities -> Responsibilities. Qualifications (Bachelor's degree etc) -> Requirements? Or Qualifications? They have both Requirements and Qualifications headings. We could put mandatory qualifications under Requirements, and preferred qualifications under Qualifications? Or we could put all under Qualifications and leave Requirements empty? But we must not emit heading with filler. So we need to decide. We have: Qualifications (Bachelor's degree... Corepoint Certified Analyst required... Demonstrated FHIR proficiency... Ability to travel up to 20%). That's mandatory qualifications. Preferred Qualifications: Epic Bridges certification etc. Skills: maybe we can extract skills from responsibilities: FHIR fluency, HL7 v2.x, EDI X12, Corepoint, Epic, documentation, troubleshooting, etc. Could create Skills section. Benefits: from "When working with Quoris as a consultant, you are eligible for competitive benefits including Health, Dental, Vision, 401k, and a great culture/working environment." Schedule: Daily Working Hours: Full-Time, Travel: Hybrid – Up to 20% travel required. We also have Start Date: ASAP, Duration: Contract (6 Months, Extension Possible), Work authorization: Must be eligible to work in the U.S. without company sponsorship, No Third Parties Please. These could go under About the role maybe as metadata. But we should not create headings for them. Could embed in About the role paragraph. We must not repeat job title. Must not include boilerplate like EEO etc. There's none. We must preserve all substantive info. So we need to include details like specific FHIR resources: Patient, Coverage, Claim, ExplanationOfBenefit, Encounter. EDI X12 transactions: 835, 837, 270/271, 278. Also mention Corepoint integration engine, Epic, data warehouse, etc. We must not invent or summarize away detail. So we need to keep the exact phrasing? Not required to keep exact but must not lose detail. We can rephrase but must keep all info. We'll produce HTML fragment with sections as needed. Let's craft:

About the role

Project Scope: We are seeking a Corepoint Interface Analyst with strong FHIR fluency to support the expansion of an enterprise AI and analytics platform at a healthcare organization. This role will build, maintain, and document HL7 and FHIR-based interfaces connecting Epic to the platform and other downstream systems, working closely with Data Exchange and Epic application teams. Position Summary: The Corepoint Interface Analyst will serve as the primary integration resource responsible for designing, building, testing, and maintaining interfaces within the Corepoint integration engine. This individual will develop and support FHIR-based and traditional HL7 v2.x interfaces, own interface documentation, troubleshoot production issues, and partner with Epic application and data warehouse teams to validate field-level mapping and integrated workflows. The ideal candidate brings hands-on Corepoint experience, strong FHIR proficiency, and a solid understanding of healthcare interoperability standards in a hospital or health system environment. Start Date: ASAP. Duration: Contract (6 months, extension possible). Work authorization: Must be eligible to work in the U.S. without company sponsorship. No third parties.

Responsibilities

• Design, build, test, and maintain interfaces within the Corepoint integration engine connecting Epic to downstream and partner systems.
• Develop and support FHIR-based interfaces including Patient, Coverage, Claim, ExplanationOfBenefit, and Encounter resources alongside traditional HL7 v2.x messaging.
• Own and maintain the interface catalog and HL7/FHIR specification documentation for all in-scope integrations.
• Support EDI X12 healthcare transactions including 835, 837, 270/271, and 278 in partnership with data warehouse and application teams.
• Troubleshoot interface errors, monitor message integrity, and provide production support for interface incidents.
• Partner with Epic application teams to validate field-level mapping and write-back behavior for integrated workflows.
• Produce data flow diagrams and support integration test plans including SIT and UAT cycles.
• Apply PHI security controls, encryption standards, and audit logging consistently across all interfaces.

Requirements

• Bachelor's degree in Health Informatics, Computer Science, or a related field; or equivalent hands-on experience.
• Production experience building and supporting interfaces in Corepoint or a comparable integration engine such as Rhapsody, Cloverleaf, or Mirth in a hospital or health system setting.
• Strong working knowledge of HL7 v2.x messaging standards.
• Hands-on experience with FHIR resources and RESTful API-based interoperability in a healthcare setting.
• Familiarity with EDI X12 healthcare transactions including 835, 837, 270/271, and 278.
• Comfortable working directly with Epic application and data warehouse teams to troubleshoot and validate integration points.
• Corepoint Certified Analyst or equivalent Corepoint Integration Engine certification required.
• Demonstrated FHIR proficiency via HL7 FHIR Proficiency Certification or equivalent verifiable FHIR project experience required.
• Ability to travel up to 20% as required.

Skills

• FHIR fluency and understanding of modern interoperability standards.
• Expertise with Corepoint integration engine.
• Proficiency in HL7 v2.x messaging.
• Experience with EDI X12 transactions (835, 837, 270/271, 278).
• Ability to collaborate with Epic application and data warehouse teams.
• Skill in designing data flow diagrams and supporting SIT/UAT test plans.
• Knowledge of PHI security controls, encryption, and audit logging.
• Detail-oriented with strong documentation and troubleshooting abilities.

Benefits

When working with Quoris as a consultant, you are eligible for competitive benefits including Health, Dental, Vision, 401k, and a great culture/working environment.

Schedule

Daily Working Hours: Full-Time. Travel: Hybrid – Up to 20% travel required.

We need to ensure we didn't create Pay section (omitted). Good. Check that we didn't repeat job title. No. Check that we didn't include boilerplate. No. Check that we preserved all substantive info: we included start date, duration, work authorization, no third parties, responsibilities, qualifications, preferred qualifications? We omitted preferred qualifications. We need to include them somewhere. They are substantive. Could add under Qualifications section or Skills? Better to add a Qualifications section for preferred qualifications. But we already used Requirements for mandatory qualifications. We have Qualifications heading unused. We could put preferred qualifications under Qualifications. Let's adjust: move mandatory qualifications to Requirements, preferred qualifications to Qualifications. Thus:

Requirements

(mandatory)

Qualifications

(preferred) We need to include preferred qualifications list: Epic Bridges certification, Epic Interconnect experience or credential, HIMSS CAHIMS or equivalent interoperability credential, Additional HL7 v2 certification, Experience supporting revenue cycle AI or analytics platform integrations. Add as

. Also we have "Ideal Candidate Profile" which is more narrative; could be incorporated into About the role or Skills? Might be considered substantive. We could add a section "Ideal Candidate Profile" but not in allowed headings. Could incorporate into About the role or Skills. Probably incorporate into About the role as a paragraph. We have also "When working with Quoris as a consultant..." we already used for Benefits. Check we didn't miss any: "Corepoint Certified Analyst or equivalent Corepoint Integration Engine certification required." included in Requirements. "Demonstrated FHIR proficiency via HL7 FHIR Proficiency Certification or equivalent verifiable FHIR project experience required." included. "Ability to travel up to 20% as required." included in Requirements. Now check we didn't duplicate content: we have travel also in Schedule section. That's okay; we have travel mentioned both in Requirements and Schedule. Might be duplication but it's okay to keep both? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but maybe better to avoid duplication. However travel is a requirement and also schedule detail. Could keep in Schedule only and remove from Requirements. But the requirement "Ability to travel up to 20% as required." is a requirement. Could keep in Requirements and also mention in Schedule? Might be redundant but still preserves info. Might be okay. However to avoid thin sections, maybe we keep travel only in Schedule and note ability to travel as part of schedule. But the requirement list includes many items; removing travel may be okay as it's still covered elsewhere. Let's keep travel in Schedule only and remove from Requirements to avoid duplication. But we need to ensure we still have the ability to travel info somewhere. We'll keep in Schedule. Thus adjust Requirements: remove travel line. Now Requirements list: - Bachelor's degree... - Production experience... - Strong working knowledge... - Hands-on experience with FHIR... - Familiarity with EDI X12... - Comfortable working directly with Epic... - Corepoint Certified Analyst... - Demonstrated FHIR proficiency... Now Qualifications (preferred) list: - Epic Bridges certification. - Epic Interconnect experience or credential. - HIMSS CAHIMS or equivalent interoperability credential. - Additional HL7 v2 certification. - Experience supporting revenue cycle AI or analytics platform integrations. Now Skills section we already have. Now About the role paragraph includes start date, duration, work authorization, no third parties. Now Benefits section. Now Schedule section includes Daily Working Hours: Full-Time. Travel: Hybrid – Up to 20% travel required. Now check we didn't miss any info: "No Third Parties Please" included in About the