Version 0.26 Release Notes¶
Release Date: September 3, 2015
The 0.26 release introduces two new modules: the CSD module, which implements the Care Services Discovery API; and the DHIS2 module, which may be used to forward data to DHIS2. It also features enhancements to MOTECH Data Services, including UI support for entity relationships and import/export support for schemas.
This release also adds a significant amount of documentation aimed at MOTECH developers and implementers, including documentation for most existing modules.
Where to Get it¶
The links below point to the 0.26.6 release, which is the current dot release from the 0.26.X code branch.
The newly added DHIS2 module enables MOTECH to forward data to a DHIS2 server. Individual-level (DHIS “tracker”) data may be forwarded in addition to aggregate-level data. One interesting use case that this module enables is forwarding data collected with handsets (e.g. CommCare) to DHIS2 by way of MOTECH. This use case may be configured entirely using UI utilizing the Tasks module to define the mapping between systems.
The newly added CSD module supports connecting MOTECH to a health worker/facility registry that supports the Care Services Discovery standard.
UI for MDS Object Relationships¶
This version also adds support for creating relationships among Data Services entities using the user interface. Relationships may now be defined either via code annotations or via UI using the schema editor. Several types of relationships are supported: one-to-one, one-to-many, many-to-many, and master-detail. You can read more about entity relationships here.
MDS Schema Import/Export¶
MOTECH adds the ability to import/export MDS entities in version 0.26. This feature allows an implementer to export his/her end-user-defined entities (EUDEs) to a file so they may be imported into another MOTECH server. You can read more about this feature here.
You can browse the list of tickets resolved for this release on our issue tracker.
|||And yes, we did just invite you to view documentation describing the auto-generated documentation that describes the auto-generated APIs for manipulating database entities that are auto-generated based on code annotations. Simple, right?|