Python Developer​/Programmer

Public Health Data Integration Developer - Austin, TX iSphere is looking for a Public Health Data Integration Developer for a 10+ month hybrid opportunity in Austin. Candidates must live in the Austin area. This one is about taking electronic case reporting data and making it actually useful inside an existing public health surveillance system. The client needs someone who can look at the current workflow, figure out what needs to happen for eICR data to move into TBIRDS, automate as much of that process as possible, and reduce the amount of manual review people are doing today.

You will be working with program, epidemiology, and technical teams to assess requirements, document workflows, build integration logic, create dashboards, validate the data, and troubleshoot the places where automation does not behave the way everyone hoped it would.

What we need:

8+ years developing, testing, maintaining, and troubleshooting with SAS, Python, R, or similar tools 8+ years working with system integration, automation, and dashboard development Strong experience with structured or semi-structured healthcare, public health, or other complex administrative data Strong database and querying experience Experience translating business and program needs into technical requirements and workable solutions Experience testing and validating automated data integration processes Strong technical documentation skills for code, workflows, requirements, and procedures Strong analytical and problem-solving skills Ability to work comfortably with both technical and nontechnical teams A big part of the work will be automating how eICR data is extracted, validated, linked, and used inside TBIRDS.

That includes building and maintaining programs, supporting dashboards, testing data quality, documenting the process, and making sure the automation is actually reducing work instead of just creating a new place for people to babysit data.

Experience with electronic case reporting (eCR/eICR), Electronic Health Records, Health Information Exchange, HL7, XML, FHIR, SNOMED CT, or other clinical terminology standards would be a strong plus. SQL, relational databases, public health surveillance systems, registries, data linkage and matching, and automated ETL or data pipeline experience would also get our attention. If you have spent years working at the intersection of healthcare data, automation, integration, and analytics and you know how to turn messy workflows into something much more usable, we should talk.