SLots in archetypes

Hello,
In archetype-editor one item type is Slot which only accepts archetypes in form of Cluster or Element as constraint on that slot. Is there any way to put a slot for including one Observation in another? Is the only way of putting two Observations together is using templates?

Regards
Pariya

MSc; PhD Candidate
Department of Computing Science and Engineering
Chalmers University of Technology
http://www.chalmers.se/cse/EN/people/kashfi-hajar

Hi Pariya,

No, it is not possible to nest Observations within slots. The allowable classes for slots are determined by the reference model. There were good reasons for setting this restriction, as allowing nested ENTRY classes intoduces all sorts of complications around the context of the observation, but it can sometimes seem awkward when creating models. In my experience, it is usually straightforward to work around the restriction by refactoring the observation which requires to be nested, as a CLUSTER archetype.

Can you give a specific example?

Ian
Dr Ian McNicoll
office / fax +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian@mcmi.co.uk

Clinical Analyst Ocean Informatics ian.mcnicoll@oceaninformatics.com
BCS Primary Health Care Specialist Group www.phcsg.org

2009/5/29 Pariya Kashfi <hajar.kashfi@chalmers.se>

Hi Ian,
Thanks for your response.

In my case, I intend to use some existing Archetypes in my own observation. Having one Cluster/section named Status and Signs, I want to put two existing archetypes named Observation: Laboratory Values and Observation:Physical Examination into that. Re-factoring existing archetypes, in this case, doesn’t make sense since eliminates the benefits of reusing existing archetypes.

_Pariya

Hi Pariya,

It seems to me that you are exactly describing the use case for
templates. Remember that the definition for an archetype is the maximal
information model for a 'single' clinical concept. What you are
describing above are most certainly separate concepts.

The purposes and usage of slots is well defined in the archetype
principles document.

HTH,
Tim

Hi Pariya,

it sounds like what you want to do is to have a number of Observations within a single report or encounter. In this case, you group them under a SECTION archetype, possibly within a COMPOSITION archetype. Since such grouping is usually a local thing, it would be more normal to do it in a template than in a archetype.

  • thomas beale

Pariya Kashfi wrote:

(attachments)

OceanCsmall.png

Hi

For that example, you should use a section archetype to group the physical examination and lab results archetypes together within
A symptoms and signs heading. The key thing to understand is that these headings, though useful for humans, have no semantic value and should not normally be referenced when querying.

We make a lot of use of a simple ‘Ad-hoc’ Section archetype that can be renamed at template level to match local requirements.

So something like

COMPOSITION.Encounter.v1 “Oral medicine clinic”
SECTION.Adhoc.v1 “Status and Signs”

SECTION.Adhoc.v1 “Lab Values”
OBSERVATION.lab_test-glucose.v1
OBSERVATION.lab_test-fbc.v1

SECTION. Adhoc.v1 “Physical Exams”
OBSERVATION.exam-mouth.v1

SECTION.Adhoc.v1 “Conclusions”
EVALUATION.problem-diagnosis.v1

Again, just to stress that the Section headers should not convey any querying semantics, they are there purely to assist human navigation.

Ian

Dr Ian McNicoll
Clinical analyst Ocean Informatics
Tel/fax +44(0)141 560 4657
Mobile +44 (0) 775 209 7859
Skype imcnicoll