On Fri, 2004-10-08 at 07:16, Alberto Odor wrote:
> Hi Tim:
> I'm really excited for the paper being accepted for the congress (I have
> four additional papers accepted).
Sounds like a busy conference.
Speaking of.....anyone here going to http://www.WONCA2004.org ? I have
session on Friday at 1:30pm in room W240c but will be there all week.
> What I have stated in the abstract is that
> we have done en extensive comparison of both comercial and Open Source apps
> to be used in this Telemedicine effort. The project is sponsored by the
> National Council of Science and Technology in Mexico and will link Mexico's
> major hospitals with 32 State General Hospitals and 32 State Rehabilitation
> Center throughout the country, to serve mainly as a second opinion and
> consultation with specialists.
Sounds like a major project. Is the infrastructure already in place
> What I need for the initial part of the project, and for the presentation in
> Buenos Aires, is:
> a) Have the Zope and Plone main interfaces in Spanish (or switchable between
> Spanish and English)
> b) Have the EMR part of TORCH with the cosmetic and functional modifications
> you stated in a previous message.
> c) Have the scheduling part of TORCH
Ok. I will attempt to migrate TORCH 1.3.2 to a newer version of Zope
(2.7.2) and Plone (2.0.4) so as to take advantage of the PloneiCalendar
product. It's great.
> d) Have basic Reporting capacity
Already there....needs documenting better.
> e) Have the capability of uploading images (X-Ray, pathology, clinical,
> f) I would need some kind of simple "Clearinghouse" system which once a case
> is uploaded, depending on the specialities required, could send emails to
> the appropriate specialists and to the system's coordinator, to control that
> a consultation request is answerd in 24-48 hrs or transmitted to an other
> specialist. This part can be manually done at the begining and developed
So this makes me think there is going to be ONE installation of TORCH
for the cases to be uploaded into? This makes sense I just hadn't
thought about that type of usage before. <g>
> other things in TORCH like: charges, billing, formulary, ICD and other
> codes, etc.... are not esential at the moment.
> Having your help to do this customization would be great, specially as it
> requires to be done as "fast track". The paper will be published in the
> Journal of Internet Medical Resaerch and it would be an honor to coauthor it
> with you.
> As I told you, I have an empty server which can be used for testing, (not a
> great server, dual 600MHz pentium, 1 MB RAM and 3 36GB harddisks), but in a
Is that really 1MB of RAM?
> couple of weeks I'll get a brand new Dell 2600 server (dual intel Xeon, 4 GB
> RAM, 4 73MB SCSI disks). The thing is I would like to have the new server
> under Windows 2003, as I'll be using it also for multimedia streaming and
> most apps I already have run under Windows.
This is fine.....though I prefer Linux or FreeBSD....it'll work fine on
Windows except for the spell checker.
> First question would be:
> 1) should I stick with Torch 1.3.2? or should I start with Torch 2?
Stick with 1.3.x The state of TORCH2 is still evolving too much.
With this and other recent interest in TORCH 1.3.2 I have decided that
it is worthwhile to continue working on it in parallel with TORCH 2.x
and then develop a migration strategy from TORCH 1.x to TORCH 2.x at the