Andy Bird Email & Phone Number

• Developed the backend for a patient facing app using Docker Swarm and AWS technologies. This included database design and development, docker configuration and deployment, and api development. Amongst the technologies used were PostgreSQL, Linux, Docker, git, Traefik, Apache, PHP, AWS.• Developed and tested numerous HL7, and JSON webservice based interfaces interfaces in a Rhapsody integration engine, as part of a re-architecture effort for a badly architected environment. This resulted in far fewer support issues, and a corresponding increase in customer satisfaction, and reduction in support overhead.• Developed a client-side Java app to send data securely to a webservice on a rhapsody engine, along with a database and web-front end for a medical report distribution system. This utilised Rhapsody 6, MS-SQL, PHP, and IIS. I also ensured that it was cross-platform compatible with a LAMP stack.• Troubleshot and bug fixed a number of interfaces, thus reducing support overhead, improving efficiency, and improving performance on the integration engine.• Liaised with clients (both with technical and non-technical staff) to clarify the requirements of interfaces, and perform testing and go-lives.

• Developed and tested (including unit testing, and end-to-end integration testing) numerous interfaces. This included ftp interfaces, HL7 TCP/IP, JSON and XML webservice based interfaces, and Database interfaces. Some of these interfaces were highly complex in nature.• Developed an in-house, web based, monitoring system to monitor multiple integration engines. This software directly resulted in faster and more effective fixes to issues, and a much more pro-active approach to monitoring and problem resolution than had previously been possible. Department expenditure on support services was lowered, and customer satisfaction improved due to this system.Although originally developed using PHP, MySQL and Javascipt, the database was later converted to MS SQL to stay in line with corporate standards. Perl was also used on certain of the integration engine hosts to provide monitoring capabilities. At its most diverse, 26 engines were monitored via this system, comprising 7 varieties of integration engine. • Was a key member of a migration project to move interfaces from eGate to rhapsody. Approximately 600 interfaces were migrated during a 6 month period.• Liaised with in-house and third party technical staff to clarify the requirements of interfaces, and perform testing.• Provided 3rd line support.