[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] re: server-side object
From: |
sjtan |
Subject: |
[Gnumed-devel] re: server-side object |
Date: |
Wed, 09 Jun 2004 19:19:33 +1000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 |
a xml-rpc application server that has
1.get_brief_demographics_and_id_by_name( list of names)
2.get_patient_demographic_and_clinical_record_and_document_references(
id , days_old)
3.get_patient_clinical_record_extract(id, period)
4.get_documents( list of reference_id)
5.save_demographic_extract( id, extract)
6.save_clinical_extract( id, extractr)
7.save_document(id, doc)
that returns xml with dtd documents would be fairly cross-application
compatible, be usable
on a WAN, as well as LAN.
It wouldn' t be difficult to do a version of the current gui - business
object -|- postgres setup to become
gui - business-object-proxy - xml-(de)serializer - xml-rpc-client -|-
xml-server - xml-(de)serializer - business-object - postgres
substitute xml for "gnumed human-and-computer-parsable home-grown wire
protocol" , if you like.
The LAN version is fine;
in fact, xml-rpc wouldn't be necessary if every client had it's own LAN
postgres server(s), and there was
a messaging system federating the LANs regulating WAN authorized
transfer/copies of medical records.
(which is a reflection of what's happening here in oz).
But it's still nice to demo a WAN efficient system,
say for VPN for the nursing home road warrior.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Gnumed-devel] re: server-side object,
sjtan <=