Hello Marcio
(In the mean time, Pablo Pazos did provide a reply, so i must say that
my response applies more generally to openEHR)
Allow me to remind you that, it all depends on what you are trying to do
(and what sort of resource or time constraints you have).
At this point, i would strongly recommend that you very carefully read,
at least once, the complete "Architecture Overview" document, so that
you understand what openEHR is about and how do the individual building
blocks fit together.
The data structures can (and usually will) get very complex, so having
the bigger picture in mind first helps immensely.
After this, you can move to the "Archetype Model" documents (this is
where you will find answers to questions regarding the structure of the
"Archetype" class) and eventually, the "Reference Model" documents.
The Reference Model will be very important when the time comes for you
to create actual computable representations according to the "blue
print" that the "Archetype" class specifies.
In other words, the "Archetype" that you might have at hand at the
moment, is only a description of a data structure...You can NOT do
something like:
MyArchetype.SomeField = "Some String Value"
...on the Archetype class, you will have to obtain an RMObject (through
the "RMObjectBuilder") and work on that one.
(It is not simply a matter of having "the right class" that someone
might have put together...Almost everything you will need in terms of
code, at least at introductory level, is available through the "java
reference implementation" project.)
I hope this helps.
All the best
Athanasios Anastasiou