I don't know if you're being facetious or not, but I think that it's interesting that they trusted a very new language for doing health care related work.
The health industry is one of the last great bits of arcane magic. Everything about it is hand-wavey. You've got all kinds of regulations and tons of data and all of the carriers have their own little fiefdoms and everything is done a thousand different ways... Don't even get me started on actuaries.
I worked on a highly unsuccessful multi-billion dollar health system that was intended to solve all of these problems on a national level. I can tell you now that a small guy working from the bottom up with individual institutions is much better placed to solve real problems than a top-down bureaucracy. The only hurdle is convincing them that they can trust your system with confidential and life-critical data.
I work at a highly successful company thats working to solve some of the problems the health care industry faces(mainly the elder care community). We grow by 20% annually and we have goals of 28% when we only grow by 26 as opposed to 28 we see it as bad.
And yes the rules, and crazy laws, and hand waving are very very apparent. Its insane but we make plenty of money.
I'm a one-man startup working to solve problems in the clinical trial and research space. The sheer number of problems can be somewhat distracting and the rules daunting, but there are a lot of doctors out there with money to throw at solutions. It is amazing.
Am I profitable? Not yet. Obviously, I'm missing some necessary traits (read: co-founder.)
good to see some other people in the same space. I'm at an established small/medium sized company in the health industry. The health stuff is fulfilling and concrete (ie you're really solving someone's problem). There's plenty of scope for "cool stuff".
From the link above, it appears that they came up with an integration product that pretty much talks to all other systems at the customer site. Given this, I would speculate that the product probably does not deal with data that probably automates/affects/interferes with a patients diagnosis/procedure atleast as of now.
Yes, absolutely! I spent nearly 4 years working in a hospital on the EMR systems. Seeing your software in use when a patient is coding in the CCU is both humbling and exciting - the patient lived. It motivates you to tighten the UI and insure data quality beyond what you'll do for any other field. Having severe budget constraints - I believe - caused us to be more innovative than any other IT department or vendor I've worked for.
Isn't the lack of OO in Clojure a problem? As far as I know most game programmers like to program in C++ and OO is supposed to be especially suitable to making games.
I am certainly not an advanced programmer, I would like a pointer to some resources on the subject.
Clojure doesn't have objects, but it has hashmaps and (multiple distinct first class) synthetic hierarchies and multimethods. Compared to that, conventional OO looks a bit crude.
