I also agree with Tims comments, we need to stay within scope of OpenEHR. Obviously anyone building an HIS has an interest in proving interoperability with other standards - but that should be up to them not OpenEHR.
Echoing Berts comment if we can get an early heads up on the requirements - it does not have to be perfect nor complete, just something that we can get started with on the design side. Demonstrating connectivity at a conference is great but I plan to have my system running 24/7 on the internet with simulated random data and it would be *very* cool to have a partner system which was sending and receiving data - so you could log into either system and see the data flow... On 11/9/07, Bert Verhees <bert.verhees at rosa.nl> wrote: > <snip> > (I snipped it away because of readability) > > How and whether that system performs with HL7v2,CDA,CCD, etc. is outside > > the scope of openEHR conformance. > > > I must say, I agree with Tim, we must take care that we (only) test to > openEhr-specs conformance. > > I would like to add some remarks. There maybe already thoughts about the > coming API, can I find some information about that? It is difficult to > have this discussion without that information. Let me explain: > > There are more platforms in which the openEhr specs can be build, .NET, > Java, Eiffel, also C++ is possible. There are also many platforms on > which openEhr can run. Linux, Mac and Windows. > There are many interfacing-possibilities to other services/software. The > good thing about open standards is that all this is posssible. > But now an API, which must be platform-independent, because there is no > platform defined in the specs. How will that look like, from technical > view: I can imagine, this will be a service as in (http) SOA/SOAP-level > > Maybe I am wrong, so please tell me were to read more about it. > > regards > Bert Verhees > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >
