Welcome back! I hope you had a wonderful holiday season. Things have certainly gone well for me. I had hoped to spend a week or so planning the next iteration of EHR Science and performing backend maintenance. Well, I managed to do a lot more!
Downtime always gets my creative juices flowing, and the last few weeks have proven to be wonderfully productive. Plans for EHR Science have been finalized, and you will begin to see changes within six to eight weeks. I decided to add a splash of color with a new logo and make modest changes to the layout. The photographs on the main page have been a hit. They will change every season (at least) and, occasionally, more often. Let me know if you have a favorite; I’ll make sure that it makes it into the yearly line-up.
New content sections will be added that address key topics related to biomedical informatics and electronic health records. I am cataloging resources collected over the years and will make them, or links to them, available through the site. In a way, I am resurrecting the old Computing for Clinicians site that was up from 1998-2004, only with a wider variety of content.
Work on the blog spilled over to my business, NTM Informatics, Inc. While looking at trends in programming, the EHR market, security, and other areas that are frequent blog topics, I began to rethink the business focus of the company. Fortuitously, the same information gathered for writing blog posts proved to be great background research for strategic planning. NTM Informatics, Inc. turned seven on January 5th, and the new strategic plan was the perfect serendipitous birthday gift.
Those who have been following the blog know that my renewed interest in programming played a major role in the creation of EHR Science. I have a long way to go before becoming an expert OOP architect, but I am satisfied with my progress. In my previous attempts to master object-oriented programming, I had no problem understanding the fundamental principles: inheritance, polymorphism, encapsulation, and data abstraction. For me, the problem was learning how to use them to design quality software. The OOP books I read were good at explaining fundamental principles but offered simplistic examples of their practical application. Looking back, I realize those books focused on teaching syntax and language features; however, building a working program requires an understanding of software architecture and object-oriented analysis/design–completely different issues. Happily, I now have the resources needed to get me to the next level.
There is a lot more to tell, but I’ll save the rest for future posts.
Happy New Year!