On Sun, 29 Apr 2001, Tim Cook wrote:
...
> The system is built. Hopefully, the community will now start on
> these things. Individuals do not have to build an entire charge
> table or an even a whole major template. FreePM is designed so
> that pieces (objects) can be built and exported at several levels
> as Zope objects.
Hi Tim,
I agree with you 100%. However, I think it would help a lot if we
provide nice and user friendly tools for the creation of these "Zope
objects".
> These individuals objects can be shared or they
> can be combined into containers for re-distribution back to the
> community. (If anyone needs a HOWTO on this I will post some
> instructions?)
Good idea. Maybe even a tutorial.
> FreePM can export objects using Zope's XML format but that is not
> very conducive to manual editing.
Since it is XML, it should be pretty easy to use.
> Defining the EMR/EHR XML
> standard is a big job unto itself.
Even by not specifically defining a standard, you have decided to settle
on using Zope's XML standard :-). In contrast, the OIO system does define
a very simple XML standard - that should be easy to translate to other XML
standards. FreePM's charge table should not be that complex. Furthermore,
I am not sure what the equivalent structure would be in GEHR???
I think you are in fact quite a bit further along than GEHR :-). If you
start using a reasonable XML structure, other projects may decide to use
it.
> When that target quits moving
> so much we are prepared to build the necessary methods to
> export/import those records.
Why don't you take the lead and nail that target? Let other projects
follow your lead.
> I would much rather work with GEHR,
> etc. to develop the XML standard and 'code to that' than come up
> with a FreePM XML format.
I understand.
> If you do not want to store the Zope objects then I can setup an
> upload area and a zwiki site for documentation of them.
Zope object XML is neither good nor bad per se. The OIO Library can index
and host any metadata so FreePM templates and charge tables can be nicely
handled :-).
Wiki is an interesting idea. If you do decide to set one up, I like to
suggest inserting links between entries in the OIO Library and pages in
the Wiki. This can give us the best of both world. Structure and
flexibility!
Best regards,
Andrew
---
Andrew P. Ho, M.D.
OIO: Open Infrastructure for Outcomes
TxOutcome.Org (hosting OIO Library #1)
_______________________________________________
Freepm-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/freepm-discuss
