Fair question and one that was bound to come up.
You are right, we had a review and planning session in December 2018 where we planned out the future of EtherCIS (MkII)
The plan was to manage that development in the open from that point on.
For their own reasons, several of the attendees at that session set up a private fork of EtherCIS and took their refactoring efforts offline for a period of months early in 2019.
In the meantime we continued to use and still to continue to use EtherCIS as a key aspect of 3 tier open source stack (PulseTile + Qewd + EtherCIS)
We were pleased to see Birger and team finally get their work (which they called EHRbase) out to open public release , under Apache 2 etc, since October and great credit to Birger and the energy and effort of the whole team in recent weeks since then as it continues to improve. Thankfully Christian, the founder of EtherCIS has been involved in the transition and is very happy with the outcome.
We are waiting on some further improvements to EHRbase ( inc JSON API ( related to specification work ongoing) , further work on documentation etc) before we can swap out EtherCIS to use EHRbase within our stack , but we intend to do so as when its ready for that.
We look forward to supporting and promoting EHRbase and continue to promote the important role of open source within the openEHR community and beyond
Hope that helps explain and helps others who may have the same question
Dr. Tony Shannon
Director, Ripple Foundation ripple.foundation