Health IT and Electronic Health
Activate your FREE membership today |
Log-in
Medical records data
Data migration, Electronic Health Record (EHR), health information technology, Health records storage management and systems, medical records
Many, if not most, of the electronic medical records applications are not true relational databases. Consequently, physicians cannot analyze their patient data to look at health outcomes and health management issues. How can those of us who know what kinds of questions health care providers will want to pose sit down with those who design these electronic medical records applications and help them to make them true relational databases that can be easily used by physicians who are not necessarily computer-savvy to help them manage their patients in the most cost-efficient and most medically sound ways?
Software/Hardware used:
Software/Hardware used:
ASKED:
May 17, 2011 6:55 PM
UPDATED:
May 23, 2011 2:17 am
Answer Wiki:
I am glad I saw this question, because I did wonder few times what was the developer thinking when they created some of these databases we see out there. But fortunately there are a lot of great products out there that have done an incredible job at architecture their solution and properly their entity relationships. I think it would be fair to assume that products who have done a poor job at designing their database, probably have done a poor job designing the rest of the product. With meaningful use in the picture several of the product vendors are paying more attention to this side of their system and since they understand the product they made, they are creating queries and reporting capabilities that may allow physicians to easily view where they are.
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
