Elizabeth Dodd wrote:
>>>Option 2. Work on the Au fork of Gnumed to get that operational instead >> >>I don't know what this means. What's the objective of the Au fork? Basically an EHR project which focusses on Australian requirements, and in its design keeps itself within the meagre intellectual capacities of the programmers. I hope to have something to show at 1280cc. For others to help we first need to lock down and document not so much the external requirements, but the internal ones: database design policy, middleware and how data moves around, and GUI design policy, so different people can write compatible modules. It was the inability to make these decisions that paralysed gnumed for so long. (and we finally ended up with a (personally) rather daunting 'neither-fish-nor-fowl' solution) This technical decisionmaking is what I tried to get started on the ozdocit.org wiki, but we have heaps of wildly different solutions with no clear way of choosing a single one. Also, many people are indifferent to the amount of programmatic work their favourite solution represents. Richard and I are doing what we *can* do, which certainly isn't the best solution, but IMHO would still be better than most of the commerical offerings (mainly because we are like two little gnomes standing on the PostgreSQL giant's head) That still doesn't help the students: we're at least 6 months away from the above, I would advise looking at Wagtail as the requirements domain is much smaller and so it's easier to specify a doable project (such as a nice GUI, for example) > The backend wouldn't get ported; it is stable although written in MUMPS. An > Australian front end? VistA doesn't need to be 'ported' or'emulated': an open-source MUMPS engine already exists. The backend does need to be modified (storing provider numbers, medicare numbers instead of "Social Security Numbers' etc. This is hard as a lot of the VistA code isn't well commented etc. The frontend is *not* open-source and Windows-only, which (IMHO) is the big show-stopper for VistA: we can't modify it. Apparently there was a push to write a java frontend at one stage, does anyone know about this? Ian _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
