I'm not sure what the patient flags issue was, but I don't think we
would plan to support 2 versions of reporting. At some future version,
reporting would switch to depending on calculation rather than logic.
This will likely be timed at the time point at which logic is changed to
depend on calculation. So this _should_ end up being transparent to the
end user who has existing Logic Rules, as they would be exposed to the
reporting module via calculation...
On 03/06/2012 01:19 PM, Friedman, Roger (CDC/CGH/DGHA) (CTR) wrote:
@Darius, Mike, Ben
How do you intend to deal with the dependency problem of reporting
and logic to avoid what happened with the patient flags module? Are
there going to be two versions of report, one that uses Logic and one
that uses Calculation? Is this entirely independent of the core release?
*From:*[email protected] [mailto:[email protected]] *On Behalf Of *Darius
Jazayeri
*Sent:* Monday, March 05, 2012 5:23 PM
*To:* [email protected]
*Subject:* [OPENMRS-DEV] "Calculation Module" sprint
Hi All,
When Ben mentioned it on a recent thread, I realized we haven't given
an update on the dev list of where things stand with Logic 2.0
<https://wiki.openmrs.org/x/jYW5AQ>.
We spent quite a few design calls working out a new approach to the
core OpenMRS logic service. Basically, what we'd previously defined
was too concretely specified, and wasn't designed in a way that let us
iterate on it easily.
The existing logic module will no longer be a core module
<https://wiki.openmrs.org/x/2REz>, and we'll be transferring ownership
of it to the Chica team. They will be able to focus on the module's
core competency of letting you write high-level rules in Arden, and
optimizing the parser.
We'll be introducing a new core module: the Calculation module, which
Wyclif did the groundwork for a couple weeks ago. This will be a
/lightweight/ module, which defines the interfaces needed to
"calculate XYZ about about a patient or cohort" (hence the name) but
we will /not/ specify how that should be done. I'm pretty excited
about this idea, and kudos especially to Mike Seaton for having pushed
us in this direction.
Next week we'll start a two-week sprint on the Calculation module,
with the approximate goals of:
* finish off remaining tickets in the core calculation module
* retrofit the reporting module to plug into these interfaces
* retrofit the logic module to plug into these interfaces
Mike and I will both be in Indianapolis on Wednesday; our schedule
will be quite packed, but can we find a block where Tammy, Steve, Win,
and Wyclif are available for some last-minute sprint planning?
-Darius
------------------------------------------------------------------------
Click here to unsubscribe
<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l>
from OpenMRS Developers' mailing list
------------------------------------------------------------------------
Click here to unsubscribe
<mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l>
from OpenMRS Developers' mailing list
_________________________________________
To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
[email protected] with "SIGNOFF openmrs-devel-l" in the body (not
the subject) of your e-mail.
[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
