Bert Verhees wrote: > > The most important reason (amongst others) is that a defined API would > speed up the development of more implementations, also other > architectures could benefit from this. At this moment, there is hardly a > market for OpenEhr, a market needs products, a market with only a few > products does not invite people to come and look. > An well defined API would facilitate other developers, would facilitate > a growing market and demand for OpenEhr. > Bert, we need to be careful with what we say here - there is certainly a market for openEHR - it is called the EHR/EMR/GP desktop market, and it is worth many hundreds of ?m. But markets are for products, so we have to talk about 'products based on openEHR', which can be many and diverse. Clearly there are not that many around yet - it is the early part of the productisation cycle, just like with any other new technology.
In my view the APIs that are of the most use right now are the vEHR and the EHR service model. Ocean will publish theirs in the coming weeks, and others are encouraged to do the same, in order to work towards a standardised EHR interface for openEHR. This is of more importance than the current standards activities in my view, since the result will have running software behind it and will be known to work. It will also have been designed rather than put together by committee. - thomas beale
