Stream: conformance
Topic: share an operation definition
Jose Costa Teixeira (Nov 02 2017 at 11:57):
Hi. Is it possible to exchange the definition of an operation? I mean the actual logic.
Jose Costa Teixeira (Nov 02 2017 at 11:58):
This: System A has an operation patient$predict_life_expectancy . Can System A tell system B "the predict_life_expectancy is defined by looking up the birthdate in a valueset (horoscope) and subtracting the value of (doomsday) from today, and updating the patient's attributes accordingly".
Grahame Grieve (Nov 02 2017 at 12:01):
you need to look into the clinical reasoning module
Jose Costa Teixeira (Nov 02 2017 at 12:05):
The one that seems closest is activitydefinition
Jose Costa Teixeira (Nov 02 2017 at 12:06):
(perhaps activityDefinition could be in the Clinical Reasoning)
Grahame Grieve (Nov 02 2017 at 12:30):
you should look at CQL actually
Thomas Lukasik (Nov 02 2017 at 19:22):
@Jose Costa Teixeira , @Grahame Grieve IMHO, this question seems closely related to the 6th (optional) REST constraint, described in Fielding's thesis::
5.1.7 Code-On-Demand
The final addition to our constraint set for REST comes from the code-on-demand style of Section 3.5.3 (Figure 5-8). REST allows client functionality to be extended by downloading and executing code in the form of applets or scripts. This simplifies clients by reducing the number of features required to be pre-implemented. Allowing features to be downloaded after deployment improves system extensibility. However, it also reduces visibility, and thus is only an optional constraint within REST.
Bryn Rhodes (Nov 10 2017 at 21:00):
@Jose Costa Teixeira, I'd second Grahame's recommendation. A CQL library that describes the logic would support sharing the behavior. Sharing the way that you want to evaluate it is something that would be done with PlanDefinition.
Last updated: Apr 12 2022 at 19:14 UTC
