> I would also like to start importing openEHR content into PatientOS in
> the new few weeks.  I am less concerned with the data at this point, 
> rather I would like to be able to take a template (perhaps initially
> just archetypes and I will combine them internally to be larger forms)
> import it and make then available as a data entry form (and display).
> 
> I am debating whether to parse the XML generated by the Archetype Editor
> (awesome tool by the way) or leverage the java reference implementation
> to read an ADL and then import.  I expect the XML would be quicker but
> more prone to break.  Though at this point it is a proof of concept not
> a long term solution (which may use the TDS instead).

I am going to use a temporary solution, to get my data into my system.
It is not that important, it is only maybe 1% percent of all the code
involved, and with no interface change at most places I can switch
easily to another more standardized solution if it comes up, or maybe a
solution a customer wants, is also possible.

I took a short look at your system (is it yours, or from a team?), I
couldn't find any quick pointers to the architecture behind, and the
standards used. Maybe you can point me to some information.

I am interested.

thanks
Bert

Reply via email to