Congrats Seref,
Very valuable contribution!
Tomaz
From: openEHR-technical on behalf
of David Ingram
Reply-To: For openEHR technical discussions
Date: Friday, 27 October 2017 at 13:28
To: "For openEHR clinical discussions (openehr-clini...@lists.openehr.org)"
, For openEHR technical discussio
This is great work. Look forward to read the details.
Congratulations!
Sincerely
Bjørn Næss
Product Owner openEHR platform
DIPS ASA
Mobil +47 93 43 29 10
From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On
Behalf Of Ingram, David
Sent: fredag 27. oktober 2017 13:28
T
I have written a note on how we will use ACTION.procedure to document what
happened during surgery.
Have a look at the notes here:
https://github.com/bjornna/openehr-discussion/blob/master/surgery/index.adoc
There is also some discussions on #slack:
https://openehrclinical.slack.com/messages/C7U
This is a very interesting topic. I have written out some of the problems in
this repo: https://github.com/DIPSASA/openehr-conformance/tree/master/aql
The general answer is that you need to write you AQL as detailed as possible.
Meaning you need to know which level you expect the multiple occure
There is a lot of use-cases involving multiple EHRs. The answer from Ian is
defined in AQL specification.
In an upcoming version of the REST API I think population queries will be added
to give client even more control on this kind of use-cases. We have already
implemented this a while ago.
Ven
5 matches
Mail list logo