Quoting Horst Herb <[EMAIL PROTECTED]>: > 2.) All segment definitions except for the MSH are in separate modules and > get > imported depending on the version of the HL7 file > (e.g. header suggests version 2.3.1, AU -> module xxx gets loaded for segment > > xxx, and the segment parser gets initialized with the version number, so that > > the segment parser can load the appropriate content parsing table for the > repsective segment). This is basically the method used by Tim Churches' PHREDSS, there seems little point in duplication.
It is MPL not GPL, so we can't import it into gnumed or wagtail CVS, but that's no reason to avoid using it as a dependency. > I can send you the PIT specs (just a few A4 pages) *Please* post these to ozdocit.org, I have been looking for these for what seems like forever. There is a PIT parser already in mini-gnumed which we can use, too. > strongly propose to help discussing the XML meta format instead so that > gnumed (and others) only have to "learn" a single format and leave the > message parsing to the universal parser modules converting those other > formats into our meta format and viceversa. Hmm, I'm not sure this would be less work in total than writing parsers that talk SQL direct to the gnumed server. Substitute YAML for XML, that would make it more attractive IMHO. Ian _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
