In ADL2 it doesn't really matter. THe only difference is that in an ADL2
template, specialisations are local 'overlays' inside the patient
template, rather than distinct archetypes in the archetype library.
In which case, you should specialise with archetypes as long as the
archetypes are likely to be reusable; when they are not, it would make
sense to further specialise by the use of overlays in a template.
All this is moot for people still using ADL1.4 tools ...
- thomas
On 26/09/2017 02:52, Pablo Pazos wrote:
Hi all,
I'm working with the clinical synopsis archetype, using it to model
very open psychotherapy notes. The difference of that archetype from,
for instance, blood pressure, triage, problem/diagnosis, is these
archetypes are more or less very specific concepts, while synopsis
might be used in many contexts, by different specialties, to save
different kinds of data. The synopsis itself is a very generic concept.
Considering querying for a synopsis, I think queries should consider
the context, not only the archetype id. For instance if I want the
psychotherapy notes instead of other kinds of clinical synopsis, some
extra data should be given in the query.
I can see two ways of doing this, with more 1. specific archetypes or
2. using templates to filter the query results. 1. means the synopsis
archetype might be specialized to synopsis-psychotherapy, so queries
can use that new archetype id. 2. at the template level using the
synopsis archetype, and the template is for psychotherapy. This
implies the template id should be used on the query as context/filter.
What alternative do clinical modelers see as more correct?
I like specializing archetypes because we can keep queries simple, but
we might end up with a lot of archetypes. Using templates makes
queries more complex, but we don't need more archetypes for
specializations.
Thanks!
PS: please let me know if this doesn't make sense :)
--
Ing. Pablo Pazos Gutiérrez
e: [email protected] <mailto:[email protected]>
p: +598 99 043 145
skype: cabolabs
<http://cabolabs.com/>
http://www.cabolabs.com <http://www.cabolabs.com/>
https://cloudehrserver.com <https://cloudehrserver.com/>
Subscribe to our newsletter <http://eepurl.com/b_w_tj>
_______________________________________________
openEHR-clinical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
--
Thomas Beale
Principal, Ars Semantica <http://www.arssemantica.com>
Consultant, ABD Team, Intermountain Healthcare
<https://intermountainhealthcare.org/>
Management Board, Specifications Program Lead, openEHR Foundation
<http://www.openehr.org>
Chartered IT Professional Fellow, BCS, British Computer Society
<http://www.bcs.org/category/6044>
Health IT blog <http://wolandscat.net/> | Culture blog
<http://wolandsothercat.net/>
_______________________________________________
openEHR-clinical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
