A little help

[aarkerio]

Hi, I am interest in help building your Ruby OpenEHR implementation but I'm afraid I'm a little lost.

I understand Archetypes have definitions, ontologies and constraints and they are the "lego bricks" that allow build an OpenEHR application. I also understand that templates are a kind of archetypes formed but basic archetypes and those templates are compiled to generate the operational templates (OT). This OT connect the medical world with the programmers world and contain the info to build the model (the "M" in MVC).

But from there I don't know how I can help this project, I think would be a good idea to make a wiki page for every OpenEHR step (serialize, validation, template compilation) and what current Ruby class creates those implementation features.

Cheers from México!

[skoba]

Thank you for your concern.
I have written ADL parser and Rails generators for archetypes, and I am writing a OPT(OPerational template) parser, now.
To edit or author an archetype/template, I have used Ocean Archetype Editor and Template Designer.
Making web based Archetype/template authoring tool is my(and other openEHR developer) dream, indeed.
If you help this project on this aspect, it will have great impacts for us.

[pacharanero]

Hi Manuel, I'm a doctor/informatician in the UK and I'm also learning Ruby
and Rails. I share your feelings of being a little lost, although I have
been offered some work as a clinical modeller with Ocean Informatics on a
freelance basis in the next few months, meaning I should get a much better
understanding of the technicalities of the ADL parsing, serialization etc
and when I do I will try to contribute this to the Ruby openEHR project, in
the form of a Wiki as you suggest.

Shinji, if there's any other help I can offer please let me know - for
example if you have some dull and repetitive sections of code to produce, I
could probably do this with guidance, also I would be happy to help with
documentation of the code (I guess you would use Rdoc?)

Marcus

On 25 December 2013 01:42, Shinji KOBAYASHI notifications@github.comwrote:

Thank you for your concern.
I have written ADL parser and Rails generators for archetypes, and I am
writing a OPT(OPerational template) parser, now.
To edit or author an archetype/template, I have used Ocean Archetype
Editor and Template Designer.
Making web based Archetype/template authoring tool is my(and other openEHR
developer) dream, indeed.
If you help this project on this aspect, it will have great impacts for us.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-31189256
.

[skoba]

Thank you Marcus.
I recognise that documentation is emerging problem for us.
However, writing English is a little heavier for me than writing Japanese or Ruby.
In the next project, I will develop rails EHR by this library and I can write documetns with examples.
I would appriciate if you correct my English well.

Happy new year!
Shinji

[pacharanero]

I'd be happy to do that Shinji. If you could add small pieces of
documentation to explain which bits of code do what, I will correct the
English and extend the documentation.

M

On 31 December 2013 08:07, Shinji KOBAYASHI notifications@github.comwrote:

Thank you Marcus.
I recognise that documentation is emerging problem for us.
However, writing English is a little heavier for me than writing Japanese
or Ruby.
In the next project, I will develop rails EHR by this library and I can
write documetns with examples.
I would appriciate if you correct my English well.

Happy new year!
Shinji

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-31387171
.