One general thing to remember is that there will normally be multiple
levels of API, from data to domain to business to application. The APIs
at those levels are likely to be designed based on different design
principles, e.g.:
* data level - API will be typically CRUD and query operations, data
correspond to the information model of the served resource
* domain level - API will be typically industry standard concepts,
e.g. medication list transactions
* business level - API will be transactional, around processes
specific to the enterprise, e.g. admission procedures
* application / presentation - APIs might exist at this level to
provide user-level interactions (workflow) with data or business
processes.
An application might be written to talk to one or more such APIs, so its
view of things will depend on those APIs.
- thomas
On 17/07/2018 09:43, Bert Verhees wrote:
On 16-07-18 16:54, Ian McNicoll wrote:
Hi Bert,
Have a look at what Ripple is doing in terms of 'meaningful APIs'.
See
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/2018-February/014799.html
This is interesting, although, what I understand from it in a "quicky"
This is what I think to have read in that quick information absorption.
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
