Hi,
I was using the Archetype Editor for a new COMPOSITION archetype, but the tool does not allow to put SECTION (or ENTRYies) on the content tab, only SLOT’s (to SECTION or ENTRYies), and so, I checked at the specification, and I found out that this limitation is caused by the tool… So, my question is: why is not possible to define the SECTION’s of a composition inside the archetype (the only possible way is through SLOT’s, and so, I have to use a template to fill that slot)?
Many thanks,
Humberto
Try LinkEHR-Ed, you can do that kind of things on it
http://www.linkehr.com/
Humberto Naves wrote:
Hi,
I was using the Archetype Editor for a new COMPOSITION archetype, but
the tool does not allow to put SECTION (or ENTRYies) on the content
tab, only SLOT's (to SECTION or ENTRYies), and so, I checked at the
specification, and I found out that this limitation is caused by the
tool... So, my question is: why is not possible to define the
SECTION's of a composition inside the archetype (the only possible way
is through SLOT's, and so, I have to use a template to fill that slot)?
no, you can just define more archetypes for SECTIONs and then include
them in the first. You are correct actualy - there is nothing in the
specs to prevent a single archetype from COMPOSITION down to SECTION and
everything underneath. It just isn't called for much because it prevents
re-use. (And I am not saying that the tool should not be changed).
- thomas beale
Hi Humberto,
If you have a look at the work that has been done in the UK with archetypes (using this tool) http://www.ehr.chime.ucl.ac.uk/display/nhsmodels/Home
you will see that the process is designed around reuse - so we have a few composition archetypes that have no specific content and a whole lot of section and entry archetypes that can be put together for whatever purpose that you require. The archetypes are maximal data sets for a particular concept.
If you start to put sections and entries into an archetype at the composition level, your potential uses drop dramatically and therefore the shareability of the data.
The way we get around this is to use a whole lot of generic archetypes that are put together in a template (in slots) and then further constrained for a particular use case. This means that the template can be as specific as you require for your purpose, while still maintaining the ability to share the data because it is based on shared archetypes.
Hope this helps.
regards Hugh
Humberto Naves wrote:
I strongly agree with your idea of reuse (we just can’t reinvent the wheel all the time…) But I think imposing such restriction in the tool could be frustrating in some cases… In my case, I want to elaborate a COMPOSITION archetype, and define the SECTION’s of that COMPOSITION, and then I will add slot’s to the ENTRYies (my reuse starts here!). Because of the restriction, I must create artificial archetypes (the workaround you just said before), to accomplish what I want. Maybe, it is better to alert the user with a warning, instead of forcing him to make tricks…
What I was talking about was not really a work around - templates are not artificial archetypes, but ways of using archetypes in particular use cases.
My contention would be that you should first look to see if the composition and section archetypes are already available somewhere and if not then create them as separate archetypes and make them available for wide use. Then other people can use your archetypes and you can share data with more people!
As soon as you start creating archetypes that are specific for a particular use case (even compositions with sections) you then lose a lot of the power of openEHR where interoperability is a real and achievable goal. The tools are designed like this to reflect the design goals of openEHR.
regards Hugh
Humberto Naves wrote:
Hi
I would just add that although it is tempting to do this at the level of the archetype in isolation, it will create many archetypes that are really for specific purposes rather than having meaning. As Sections are really about human navigation we understand that people may want to have sections that only have certain things in them, or the SOAP problem oriented layout. Generally though, a progress note might be organised in 100s of different ways and we do not want 100 compositions that are Progress Note for this and that. This is the role of templates.
http://www.openehr.org/wiki/pages/viewpage.action?pageId=1376257
Cheers, Sam
Hugh Leslie wrote:
(attachments)
