I agree, I think. We need to be able to document inside the EHR. database what was sent to the service, what was received from the service.
The EHR application actively interacts via an interface with the service, and the ERH-system application documents/stores via an other interface in the EHR database. Why would an AOL need to deal with the service, when all data and associated ranges are inside the EHR database? The AOL is using the interface with the EHR database only, I think. Gerard Freriks +31 620347088 gf...@luna.nl Kattensingel 20 2801 CA Gouda the Netherlands > On 2 Mar 2018, at 02:55, Colin Sutton <colin.sut...@ctc.usyd.edu.au> wrote: > > There is a risk that the external service could provide different answers at > different times, if the external service is updated for technical or clinical > reasons (e.g. knowledge improvements) > Shouldn't the result of the query to the external service be made at the time > of the source event, not in AQL. > — > Colin >> On 1 Mar 2018, at 10:31 pm, Bert Verhees <bert.verh...@rosa.nl> wrote: >> >> On 01-03-18 12:01, Diego Boscá wrote: >>> I believe that we need a way in standard AQL to call to arbitrary external >>> services, this seems like another use case for that \ >> >> I agree! >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical@lists.openehr.org >> http://scanmail.trustwave.com/?c=13000&d=oeSX2qbCWwprcB5eNMB27oRdY2Loky0QJHUrFju91A&u=http%3a%2f%2flists%2eopenehr%2eorg%2fmailman%2flistinfo%2fopenehr-technical%5flists%2eopenehr%2eorg > > > ##################################################################################### > Scanned by the Trustwave Secure Email Gateway - Trustwave's comprehensive > email content security solution. > ##################################################################################### > > ________________________________________ > IMPORTANT NOTICE: This e-mail and any attachment to it are intended only to > be read or used by the named addressee. It is confidential and may contain > legally privileged information. No confidentiality or privilege is waived or > lost by any mistaken transmission to you. The CTC is not responsible for any > unauthorised alterations to this e-mail or attachment to it. Views expressed > in this message are those of the individual sender, and are not necessarily > the views of the CTC. If you receive this e-mail in error, please immediately > delete it and notify the sender. You must not disclose, copy or use any part > of this e-mail if you are not the intended recipient. > ________________________________________ > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
