Designing a New Electronic Medical Record(techcrunch.com) |
Designing a New Electronic Medical Record(techcrunch.com) |
I don't really have time but if I wanted my submission to be considered I would try to cheat that way by creating working JavaScript code that processed XML and spit out different formatted versions for phones vs. larger screens and also different languages.
Anything else we are missing?
You're looking for an output design that is effective as a physical document. Please consider a follow-up challenge for EMR input UI/UX.
There's a new effort to merge both systems onto a new one called OSEHRA (Open Source ...), which should be interesting, but I hope it looks more like VistA and less like AHLTA. I suspect MEDCOM is more powerful politically than the VA, though.
ps. got an api?
[edit] forgot to read the profile
Maybe I'm wrong, or I'm overseeing something but I think that "Patient has inherited malicious BRCA1 mutation" information should be IN patients medical record.
So if I understand correctly, you are basically doing what you have been told to do? Good for you - call that corporate software development, but not design, creation, startup of whatever.
Regarding your reply, it's not about the "right" way to represent genetics data, but having any way at all to input that - which seems "absent" in the current model, but maybe I haven't dug deep enough.
Also, $50k for the design that will be used for 6 millions potential clients? Hmm it's like 0.0083 cent per client. If you make a piece of software that successful, it's like selling it for 1 cent apiece on the applestore.
So I guess I'll pass on this one.
BTW there is something funny in the article: "You might even end up working with big EMR startups like Practice Fusion."
Well, yey :-/
I'd rather like to create a new EMR company - the one that'll put the others out of business :-)
Good luck to all entrants anyway.
There's no way a records presentation system would be useful if it didn't take standards like HL7, ICD9 codes, etc. on the input. There has been a huge effort over the past few years to get small practices onto EHR/EMR (for a variety of reasons...patient care quality and billing/admin cost savings), so anything which didn't work with those standards would be a huge step backward on those efforts as well.
The nice thing is most of these ugly protocols have decent libraries available (some open source, some commercial), so you can build a HIS/EHR/EMR/PACS/LIS/etc. with general software engineering talent and a limited amount of specialty knowledge, but you really do need some experience in the clinical environment (at least as a tech or doing tech support), I think, to build a credible overall system. And to actuall sell larger systems, an MD on the team is really helpful (at least for PACS, a rad or ortho).
That said, being able to 'pretty print' a medical record (on paper, or maybe some kind of interactive format) for patient use or portability outside the system doesn't require a huge amount of clinical knowledge, but it's not enough to replace an EHR.