Python is one of the leading professional programming languages in use today. It was the official programming language of my previous employer and, boy, am I glad I had the chance to learn it! C++ is not much of a web language these days. Many people use Java, PHP and Perl for their web programming. These are all fine languages but it is my personal opinion that they are all inferior to Python for this project.
I have three main reasons to use Python:
1. loosely-typed language
For those non-technical, a loosely-typed (or duck-typed) language forgoes many programming formalities and allows you to make changes to code more quickly. In an atmosphere where I plan to make many changes to accommodate my customer, ease-of change is essential.
2. Readablity
The code for many other programming languages (ahem, PERL) tends to end up messy, with indentation irregularities and differences in formatting. But with Python, indentation is part of the logic flow and the code is more readable from the get-go. Sure, with Python you can make code illegible, but it is much easier to do so in most other languages.
3. Existing libraries
The Django web framework is written in Python. Django is a well-tested, comprehensive and exhaustively documented web framework which, to me is just magical. I have worked with several web frameworks and none is as flexible and easy to use as Django.
Django abstracts many of the mundane and error-prone link table creation out into a fantastic Python API. Django is also sufficiently performant to support numerous production Internet sites. See the Django Website for more information.
Showing posts with label EMR. Show all posts
Showing posts with label EMR. Show all posts
Friday, December 25, 2009
Thursday, December 24, 2009
Productivity first, electronic records second
A few months back, Carolina Oncology Specialists(COS) purchased a product named Varian and implemented it in the office. This program performed its duties as a comprehensive data repository but ultimately, it lacked flexibility and was not productive for COS. There was also no benefit to the patient experience. In fact, the experience was so counter-productive that the staff at COS demanded to return to paper charts. Kudos to salesmanship.
But the client base (unfortunately) at COS is growing and it is clear that a paper charting system will not scale. If an EMR system was not needed now, it would be soon. This is where I come in.
Before I began the implementation of any type of EMR system, I conducted interviews with the staff and did some research into the oncology EMR products on the market. There are innumerable products, each claiming to be 'easy to use' and completely interoperable with other products. Some by large vendors, some by small open-source communities. We signed up for a few interactive demos and had phone conferences with sales people but none could offer the features needed by a medium-sized oncology practice like COS.
The Oncology clinical workflow is different from most medical workflows. Not only do drugs need to be ordered and labs reviewed, but entire treatment schedules need to be managed. Many of the patients are in-patients and need to be monitored not only between office visits, but during one, as well.
Busy Doctors, nurses and administrative staff just don't have time to fiddle with clunky interfaces ill-designed for minute-by-minute patient tracking. My job has become to help this office not just convert their charting data to an electronic format but also to provide a product that will _improve_ their office efficiency, quality of service and patient throughput .
COS (and Oncology practices, in general) need more than an EMR, they need an patient tracking engine.
But the client base (unfortunately) at COS is growing and it is clear that a paper charting system will not scale. If an EMR system was not needed now, it would be soon. This is where I come in.
Before I began the implementation of any type of EMR system, I conducted interviews with the staff and did some research into the oncology EMR products on the market. There are innumerable products, each claiming to be 'easy to use' and completely interoperable with other products. Some by large vendors, some by small open-source communities. We signed up for a few interactive demos and had phone conferences with sales people but none could offer the features needed by a medium-sized oncology practice like COS.
The Oncology clinical workflow is different from most medical workflows. Not only do drugs need to be ordered and labs reviewed, but entire treatment schedules need to be managed. Many of the patients are in-patients and need to be monitored not only between office visits, but during one, as well.
Busy Doctors, nurses and administrative staff just don't have time to fiddle with clunky interfaces ill-designed for minute-by-minute patient tracking. My job has become to help this office not just convert their charting data to an electronic format but also to provide a product that will _improve_ their office efficiency, quality of service and patient throughput .
COS (and Oncology practices, in general) need more than an EMR, they need an patient tracking engine.
Wednesday, December 23, 2009
Oncology EMR - Lofty Goals
Speaking in a pseudo-panic, I called the lead physician at Carolina Oncology Specialists and asked this question.
"Why do you need this EMR software?"
I had been commissioned to write an electronic medical records program for this medium-sized oncology office in Western North Carolina, but had suddenly become unconvinced that what I was writing was 1. necessary and 2, relevant. COS has had a long history of success and prestige in its market and although its customer base was rapidly expanding, its paper charting system was working well. Why fix what ain't broke?
I didn't want this project to become a case study in wasted development and poor planning; I needed validation that this software would truly improve the lives of the patients and employees of COS. The lead physician, Dr Orlowski (My Father) eased my panic and we concretized our previously nebulous goals. The on-going pursuit of these goals will be the foundation of further discussion on this blog:
The goals we outlined are:
1. Improve patient safety -- dosing precautions, tracking allergies, etc.
2. Increase office productivity -- less time looking for charts/patients
3. Reduce patient waiting time
4. Record an up-to-the-minute accounting of office events
5. Create auditable data trails for reporting and potential future government quality assesments
6. Provide backwards-compatability with the current paper chart system.
and...
7. Call it an EMR
We agreed that "having an EMR" was not enough. It had to actually make life better for the people who used it. What good is having an EMR if it grinds your office to a halt?
"Why do you need this EMR software?"
I had been commissioned to write an electronic medical records program for this medium-sized oncology office in Western North Carolina, but had suddenly become unconvinced that what I was writing was 1. necessary and 2, relevant. COS has had a long history of success and prestige in its market and although its customer base was rapidly expanding, its paper charting system was working well. Why fix what ain't broke?
I didn't want this project to become a case study in wasted development and poor planning; I needed validation that this software would truly improve the lives of the patients and employees of COS. The lead physician, Dr Orlowski (My Father) eased my panic and we concretized our previously nebulous goals. The on-going pursuit of these goals will be the foundation of further discussion on this blog:
The goals we outlined are:
1. Improve patient safety -- dosing precautions, tracking allergies, etc.
2. Increase office productivity -- less time looking for charts/patients
3. Reduce patient waiting time
4. Record an up-to-the-minute accounting of office events
5. Create auditable data trails for reporting and potential future government quality assesments
6. Provide backwards-compatability with the current paper chart system.
and...
7. Call it an EMR
We agreed that "having an EMR" was not enough. It had to actually make life better for the people who used it. What good is having an EMR if it grinds your office to a halt?
Subscribe to:
Posts (Atom)
Posts
