I had an evening yesterday to do some coding for another GP Surgery and it made me understand it’s not a matter doing the best possible application which is loosely coupled, well designed and future proof but using the right tools for the job.
I’ve been reading up on the Onion Architecture and think it’s a nice way of organising your code leading on to Domain Driven Design. This is my first project for this way of developing and it’s on the back end of a request from a good friend of mine to address a specific problem.
There has been a lot of talk recently in UK health related IT sites around getting clinicians to code mainly catalysed by an article on Tim Kelsey’s opinion on the matter in E-Health Insider.
This subject has been very emotive for me for a little while. When I talk tech to fellow GPs, they tend to look at me with a glazed look unless I speak like a soft system designer. Developers on the other hand either don’t know how to handle me, or take me with a pinch of salt. You’re in this half way house and don’t quite fit into either world.
2 Blogs whose authors I have a great amount of respect for summed up the issues perfectly: