Hi all, I just published the received responses. So far only four members of the community shared they work, ideas and needs. For you:
Hope this can get others motivated to follow. We need to improve our community, collaborate and be more open. https://openehr.atlassian.net/wiki/display/dev/Development+Community+Coordination On Mon, May 22, 2017 at 4:56 AM, Seung Jong Yu <ggoj...@gmail.com> wrote: > Good Idea, Pablo ! > > Even if I can not support openEHR specific terminology services, I filled > form :) > > Seung-Jong Yu MD > seungjong...@gmail.com > > Certified Board of Family Medicine > CEO, InfoClinic Co., Ltd. (i...@infoclinic.co > , > http://infoclinic.co > > ) > Administrator, openEHR Korea ( > mas...@openehr.kr , > http://www.openehr.kr) > HL7 Korea Board of Director (http://hl7korea.or.kr) > > Mobile : 82-10-4752-5435 > ggoj...@gmail.com ( only for mailing list ) > > 2017-05-20 1:29 GMT+09:00 Pablo Pazos <pablo.pa...@cabolabs.com>: > >> 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 <099%20043%20145> >> Skype: cabolabs >> <http://cabolabs.com/> >> http://www.cabolabs.com >> pablo.pa...@cabolabs.com >> Subscribe to our newsletter <http://eepurl.com/b_w_tj> >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical@lists.openehr.org >> http://lists.openehr.org/mailman/listinfo/openehr-technical_ >> lists.openehr.org >> > > > > _______________________________________________ > openEHR-implementers mailing list > openehr-implement...@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr- > implementers_lists.openehr.org > -- Ing. Pablo Pazos Gutiérrez Cel:(00598) 99 043 145 Skype: cabolabs <http://cabolabs.com/> http://www.cabolabs.com pablo.pa...@cabolabs.com Subscribe to our newsletter <http://eepurl.com/b_w_tj>
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
