On 17-07-18 12:05, Ian McNicoll wrote:
This is harder for newbies to understand but....
We don't write API's as learning material for newbies, but for
professional communication, so that is no problem.
Also for the rest I agree.
There is need for API's for interaction between two OpenEhr
environments, and API's for the rest of communications (that will be
used most). I mentioned FHIR as example, of course FHIR is not perfect.
But we cannot deny its success.
A specific message-format-API is not what I am looking for, by combining
several API's, a developer should be able to craft any message he wants,
very easy. I have done that a lot, also last year. It is sometimes my
daily income.
Often we forget that on discussion-lists we are in the year 2525, but on
the market we still see message types from 20 years ago, HL7v2, EDIFACT,
XML, vendor specific formats, it all happens a lot. Sometimes the only
way to communicate with some critical software-products.
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
