search

jorritspee / openEHRxNuts

A specification for a distributed openEHR data federation using Nuts v6
0 stars 0 forks source link

Decide on using REST API and/or query API in spec #2

Open jorritspee opened 3 months ago

jorritspee commented 3 months ago

Links: https://specifications.openehr.org/its

joostholslag commented 3 months ago

‘All’ API’s specified in openEHR are rest apis. Probably we need both the ‘query’ and ‘ehr’, and potentially the definition api, so probably the nuts spec will be a separate spec, if at all part of the openEHR spec.

jorritspee commented 3 months ago

Okay thanks. But you mentioned earlier that not all vendors have implemented the REST-API. Is that something we have to take into account (and how)?

joostholslag commented 3 months ago

Okay thanks. But you mentioned earlier that not all vendors have implemented the REST-API. Is that something we have to take into account (and how)?

Yes. All have implemented rest apis (at least all currently relevant for this project.), but not all use the official openehr specification for those apis. Better has, code24 and Nedap have not (yet). At least partly because they don’t support aql and thus can’t support the query api. We should discuss how to handle this. I think we should focus on the official rest apis, because I expect both companies to implement the rest api at some point. But we should discuss how big the deviations are and wether there are possibilities to make the solution work for non standard openehr rest apis too.

Compare for example https://www.ons-api.nl/techniek/apis/APIS.html#/openehr.CompositionWrapper/openehr.CompositionWrapperAPI.authorizedCompositionVersions With the standard: https://specifications.openehr.org/releases/ITS-REST/Release-1.0.3/ehr.html#tag/COMPOSITION/operation/composition_get