-----Original Message-----
FWIW, I think this python client (done this way) is
all wrong. Which is why I haven't replied. I'm working on trying
something else.
Your experience inside a hospital suggests that directly connecting to
the backend is going to be problematic.
I'd like to see a REST client and a REST backend.
I *would* suggest that we not make connectivity from the hospital a
first priority, for a couple of reasons:
1) my office is across the street from the hospital
2) it is not impossible that I could get the hospital to unblock some
ports, from at least aa couple of computer locations in the hospital
3) the machine I would use as a server has no competing need to host
port 443, the server's purpose woould be purely to support the aZEMR
(GNUmed) so if the GNUmed client would (via config file) go out
through the hospital's proxy on port 443 and that would then, on
hitting the server, get redirected to PostgreSQL, maybe that would
solve any need if #1 and #2 above would not.
Strategically (or at least tactically) the earlier interest is
identifying how we might get the Excelleris XML-wrapped HL7 lab data
into the GNUmed backend. It sounded like Richard might assist us with
that in a couple of weeks.
I gather REST has more to do with your contemplation of a full Java
and/or browser-based alternative to a Python client? Dunno whether
the following usefully captures the essence:
http://www.xfront.com/REST-Web-Services.html
_______________________________________________
Gnumed-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnumed-devel
