Hello Pablo,

This sounds like a good initiative! Maybe it could be a good idea to add some 
way to distinguish ADL 1.4 and ADL/AOM 2 projects. Perhaps also the different 
RM versions?

Regards,

Pieter Bos

Op 19 mei 2017 om 18:30 heeft Pablo Pazos 
<pablo.pa...@cabolabs.com<mailto:pablo.pa...@cabolabs.com>> het volgende 
geschreven:

Hi all,

We were discussing on other threads about the need to improve the tools, ref 
impls and frameworks we use for openEHR stuff. We are few in the community 
working on those areas, and sometimes doing duplicated work and overlapping 
solutions.

I believe if we know who is working on what, we can make a better use of our 
collective time as a community, and reuse others work, or even help on their 
projects.

Modeling tools are getting behind the specs progress, tool chain is broken and 
needs manual work to get modeling done, open implementation tech stacks are not 
complete, etc...

What if we can publish the areas we are working on, tools that we already have, 
and try to coordinate better to fix those issues and collaborate better as a 
community?


I have created a small google form to gather and share that info, it has these 
questions:

1. On which areas are you / your company working on? (modeling tools, CDRs, 
APIs, ...)
2. Is code open or planned to be open?
3. Current status (idea, planned, developing, developed, released, ...)
4. Main issues and challenges (for the community to help)
5. Available tools / solutions and where to find them


If you see there is another question that can add value to this, please let me 
know. After this is complete, I'll share the form. When we have some answers, 
I'll publish them on the wiki.

Hopefully others can this this as an opportunity to move forward on the 
modeling and dev areas to increase openEHR adoption.


Kind regards,
Pablo.

--
Ing. Pablo Pazos Guti?rrez
Cel:(00598) 99 043 145
Skype: cabolabs
        
[https://docs.google.com/uc?export=download&id=0B27lX-sxkymfdEdPLVI5UTZuZlU&revid=0B27lX-sxkymfcUwzT0N2RUs3bGU2UUovakc4VXBxWFZ6OXNnPQ]
 <http://cabolabs.com/>
http://www.cabolabs.com<http://www.cabolabs.com/>
pablo.pa...@cabolabs.com<mailto:pablo.pa...@cabolabs.com>
Subscribe to our newsletter<http://eepurl.com/b_w_tj>

_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org<mailto: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

Reply via email to