If you are allowed to see the file and field definitions you should be able to process the files directly into M whatever the format is. It's just a matter of knowing how the file is defined, which will determine how you open it and use it as well as how to parse it. Obviously you might need to do some translation for patient pointers or other coded fields. It's very doable in my opinion.
Kevin Toppenberg wrote:
OK, OK, I know this is a M list. But hear me out.The December our Mysis contract will expire, which is our old EMR.
The company says that it will be $5,000+ to get the old progress notes
exported. Recently our group voted not to do that, and to just go
forward with our paper printouts of that data (which are already in
our paper charts).But I can't help but wonder if I could get the data out myself. I
know that I can do it through printing to a disk instead of printer,
then running it all through a conversion program. But it is certainly
lacking.The underlying code is written in cobol -- either RM COBOL or
MicroFocus Cobol (or both). I don't know Cobol, but I gues I could go
learn it...So my question, does anyone know enough about cobol to tell me to give
it up now, its too hard. Or that it's just sitting there for easy
picking. Would the cobol be acting as the database itself (as M
does), or would it likely be using some other method of storing. This
technology is circa 1990.Thanks
Kevin-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
