Back to search
Buds Technology Linkedin · Posted 3d ago

Senior Integration Engineer: Healthcare Data & AI Automation

Roswell, Georgia, United States

Linkedin
Continue to application Add your email once, then Caio opens the original posting.

Indexed description

Senior Integration Engineer: Healthcare Data & Al Automation

Engagement Type: Contract I Location: On-site/Hybrid I Experience: 5+ years

Focus: Post Acute (Hospice / Home Health) EMR and EHR Integration, Healthcare Data, APIs, python on Linux, Digitalocean, MySQL, Al Assisted Engineering.


ABOUT THE ROLE

We are seeking an experienced contract Senior Integration Engineer to build, troubleshoot, and maintain integrations between our healthcare SaaS platform and EMR/EHR systems. This is a hands-on role for someone who can work independently and take integrations from technical discovery through UAT and production launch. Our platform runs on DigitalOcean, with Python services on Linux and MySQL as the canonical data store. You will build the ingestion, transformation, and API layers between customer EMR data and our application and help turn them into a reusable integration platform of source adapters, canonical models, transformation rules, and validation components, so that onboarding each new EMR is faster than the last. Example source systems include Homecare Homebase (HCHB) via replicated or log shipped SQL, MatrixCare via Snowflake, and platforms such as WellSky, HospiceMD, Axxess, and Epic. Hands on familiarity with EMR data are a hard requirement. This is not a role where post-acute clinical data is learned on the job. You should already be comfortable with the shape of EMR data, including patients, admissions and episodes, visits, providers, orders, assessments, diagnoses, medications, and clinical narratives, and how inconsistent and incomplete it is in practice.


KEY RESPONSIBILITIES

Integration & Delivery

• Design, build, test, and maintain EMR/EHR integrations from technical discovery through UAT and production launch.

• Work directly with EMR vendors and customer technical teams to establish and validate data access.

• Ingest data through REST APIs, FHIR, HL7, webhooks, SFTP and file-based interfaces, and replicate or log shipped databases, and land it into our MySQL canonical schema.

• Write production Python services and pipelines that run on Linux and deploy to Digitalocean.

• Build reusable source adapters and standardized ingestion, normalization, transformation, validation, and API delivery patterns.

• Implement incremental processing, CDC, watermarking, retry, replay, and idempotency patterns.


Data Mapping & Canonical Model

• Map clinical and administrative data between EMRs and our platform, including patient, admission and episode, visit, provider, branch, diagnosis, certification and benefit period, CTI and face to face, medications, care plans, hospice elections, clinical narratives, and IDG/IDT data.

• Design and evolve MySQL schemas, indexes, and migrations that support both high-volume ingestion and low latency API reads.

• Resolve semantic differences between EMR platforms rather than relying solely on direct field-to- field mapping.

• Build reusable transformation functions for identity resolution, code translation, status normalization, one to many relationships, and aggregation.

• Maintain persistent crosswalks across identifier formats (GUIDS, integer 'Ds, MRNs, episode, admission, and provider IDs), preserve source lineage for every canonical record, and keep mapping specifications versioned.


Al Assisted Engineering, Not Vibe Coding

We expect you to use Al tools every day and to be fully accountable for what they produce. An Al assisted engineer uses models to move faster on work they could do themselves and can defend line by line; a vibe coder ships generated Output they do not fully understand. We are hiring the former.

• use LLM and agentic tools (Claude, ChatGPT, GitHub Copilot, Cursor) to analyze unfamiliar EMR schemas and identify candidate tables, fields, keys, and relationships.

• Generate initial source to target mappings from schemas, sample data, documentation, and API specifications, then convert them into reviewed, deterministic, production grade transformations.

• Review every Al generated change the way you would review a junior engineer's pull request: read it, test it against real source data, simplify it, and reject it when it is wrong.

• Be able to explain any line Of code you submit, including its behavior and failure modes, without going back to the tool that produced it.

• Recognize where Al does not belong to correctness; critical clinical logic requires deliberate design rather than autocomplete.

• Build reusable prompts, scripts, and internal tooling that make each subsequent EMR integration faster than the previous one.


Support, Quality & Documentation

• Troubleshoot API, authentication, data mapping, and production issues on Linux servers, including log analysis, query profiling, and performance tuning.

• Develop monitoring, logging, alerting, and dead letter handling for integration failures.

• Build validation and reconciliation checks for completeness, referential integrity, duplicates, required fields, and source to target record counts.

• Document APIs, data mappings, configurations, and troubleshooting procedures, and maintain code, mappings, and schemas in Git with automated regression testing.


Security & Collaboration

• Ensure appropriate handling Of PHI and compliance with HIPAA requirements, including least privilege access, secure secret management, encryption in transit and at rest, and audit logging.

• Follow our policy for Al tool usage with PHI: approved tools and workflows only, using de-identified or synthetic data for prompting wherever possible.

• Keep production Of PHI isolated from development and testing environments and apply sound Linux and cloud security practices including hardened servers, restricted database access, and firewall rules.

• Collaborate with our Engineering, Product, QA, and Implementation teams, and interact directly with customer and EMR/EHR technical teams as needed.


REQUIRED QUALIFICATIONS

• 5+ years Of software development, data engineering, healthcare IT, or systems integration experlence.

• Hands on experience with EMR/EHR data, whether building integrations against it or extracting, modeling, and reporting on it. You should be able to walk us through a real EMR data model you have worked with.

• Strong production Of python for data processing, APIs, and automation.

• Strong hands-on SQL, including joins, CTEs, window functions, aggregation, and incremental processing, with practical MySQL experience across schema design, indexing, and query tuning.

• Comfortable working on Linux: shell, services, cron and systemd, log analysis, and deployment.

• Experience running applications on cloud infrastructure; DigitalOcean or comparable virtual machine and managed database platforms.

• Strong experience with REST APIs, JSON/XML, authentication, and data mapping, and working knowledge Of FHIR and HL7.

• Experience designing ETL/ELT pipelines across heterogeneous data sources and troubleshooting complex integration and production issues.

• Disciplined, demonstrated use Of Al coding tools in day-to-day engineering, with the judgment to review, test, and correct what they produce.

• Experience with Git, automated testing, and CI/CD.

• Understanding Of HIPAA, PHI, and healthcare data security.

• Ability to work independently with third party APIs and vendor technical teams, with strong problem solving and communication skills.


PREFERRED EXPERIENCE

• Hospice, home health, senior living, skilled nursing, Or other post-acute care settings.

• Direct work (preferable) or related work with any of the EMR platforms named above.

• Python service and data libraries such as FastAPl, SQLAlchemy, Alembic, Pandas, and Celery.

• Docker, container-based deployment, and CI/CD pipelines targeting DigitalOcean.

• Replicated or log shipped to SQL Server databases, Snowflake, and similar reporting data stores.

• Workflow orchestration with Airflow, Prefect, Dagster, or equivalent.

• OpenAPl design, plus API versioning, throttling, and observability.

• Identity resolution, MDM, or persistent source system crosswalks, and data governance practices.


HOW WE EVALUATE Al ASSISTED ENGINEERING

Expect a working conversation rather than a whiteboard puzzle. We will ask you to walk us through something real you built with Al assistance: what you asked the model for, what it got wrong, what you changed, and how you verified the result. Specific, confident answers about your own code matter far more to us than the volume Of code you can generate.


CONTRACT ROLE EXPECTATIONS

We are looking for a contractor who can quickly get up to speed, work independently under the engineering leader's guidance, and own assigned integrations from discovery through production. Success is measured by reduced time to onboard a new EMR or hospice client, the share of mappings and tests that are reusable or generated automatically, the accuracy and traceability Of transformed healthcare data, and a decline in production integration defects. While this is initially NOT a full-time employee position, it could turn into a full-time role based On demonstrated success and the candidate's breadth of experience and technical skills. This is an on-site role based in our office in Roswell, GA. Work from home is available on an as needed basis, but the position requires regular in person interaction with our team and occasionally with client technical team(s).

Free. 20 seconds. No password. See every match in this search.

Create a free Caio profile to unlock more results and save your role and location preferences.

Unlock free search
Want help applying to roles like this? Search Caio for free. If repetitive applications get heavy, Managed Job Search adds supervised execution for $99/month.
View Managed Job Search