I see an awful lot of well-meaning, hard-working people in clinical labs and clinical lab-related areas, trying to do too much with too few resources. I enjoy providing software which actually makes their jobs easier and gets their results to the clinician more reliably with less delay.
Clinical Lab Background
I have been working with clinical laboratories since 2000. My projects usually plug gaps in the client's information infrastructure or automate their processes where it is safe and productive to do so.
My LinkedIn profile is here: http://www.linkedin.com/in/brendanhemingway/
I have been working with hospitals since 1984 and with Diagnosis Related Groups (DRGs) since about the same time. One of my business ventures is entirely DRG-centered: DRGGroupers.com. For more information, visit our web site at this URL: http://www.drggroupers.com.
I am also a principal in a Medical IT consulting firm, M+H Consulting, LLC. That web site is here: http://www.mhconsulting.com.
In addition to clinical labs, I have consulted to hospitals, ambulance companies and medical practices.
Currently, late 2013, I am working to launch a new cloud-based lab-related venture which is still in the early stages.
Software Development Environments I Use
While I do lots of coding, but I am not primarily a coder. I code as a means to an end, not as an end in itself. We used to say "I provide solutions, not just software."
I am not a software development environment absolutist. I have used a wide variety of environments. I try to use whatever works best, but often the client's requirements are the determining factor. However, since I am so often asked which programming tools I have used, here is an incomplete-but-representative list:
- Ruby on Rails under Linux
- PHP under Linux
- Perl under Linux
- Java under Linux
- Visual BASIC under Windows
- BASIC, C and FORTRAN under VMS
- ANSI C under MS-DOS
- ANSI C under Unix
- Watfiv (FORTRAN), PL/1 under CMS
- SQL Server