HL7 Architect || Remote role

HL7 Architect

Remote role

Long term contract

1 interview

Job Description

Must be capable of designing, developing, and supporting HL7/FHIR interfaces between Epic and third-party applications (e.g., Philips PACS)."

Job Overview:
Must be capable of designing, developing, and supporting HL7/FHIR interfaces between Epic and third-party applications (e.g., Philips PACS)."

Company Job Description:
The HL7 Interface Developer is responsible for designing, developing, implementing, and supporting integration solutions across the hospital's clinical and administrative systems. This role focuses on the creation and maintenance of HL7 interfaces that enable seamless data exchange between EHRs, ancillary systems (lab, radiology, pharmacy), medical devices, and external healthcare partners. The developer ensures interoperability, data integrity, and compliance with healthcare data standards.

Key Responsibilities
-Interface Development & Integration
-Design, develop, test, and deploy HL7 interfaces using integration engines (e.g., Cloverleaf, InterSystems Ensemble/IRIS).
-Translate functional requirements into technical specifications for interface development.
-Build and maintain real-time, batch, and API-based integrations adhering to HL7 standards (v2.x, v3, FHIR).
-Develop robust workflows for ADT, ORM, ORU, SIU, MDM, DFT, and other standard HL7 message types.
-Operational Support & Troubleshooting
-Monitor interface performance and proactively resolve errors, message failures, and data discrepancies.
-Optimize existing interfaces for performance, reliability, and maintainability.
-Document interface specifications, mapping logic, change logs, and operational procedures.
-Maintain data integrity standards and ensure accuracy of exchanged health information.

Qualifications:
-Must be Epic Bridges certified.
-Must be experienced in developing interfaces in IRIS (formally known as Ensemble) which is an Intersystem integration engine.
-Must have experience in data conversion, converting historical clinical data into Epic.
-Must have the ability to build interfaces between Epic and third-party applications. (example is Phillips PACS)
-Need to be able to hit the ground running. So don't want us to send over anyone that just received their Certification
-2+ years of experience developing HL7 interfaces within a healthcare environment.
-Exposure to EHR platforms (Epic, Cerner, Meditech, Allscripts, etc.).
-Strong knowledge of HL7 v2.x messaging structure, segments, fields, and workflows.