Thanks,

More questions below.

On 27 March 2012 13:12, Grahame Grieve
<grahame at healthintersections.com.au>wrote:

>
> > 2. The problem of openEHR archetype constructs being over-granular for
> > summarised reports, mostly in the integration space but we do also need
> this
> > in the EHR space at times. As an example I might want to record a
> Medication
> > instruction in a summary, along with a couple of key events e.g Date of
> > first prescription, Date of last prescription. Currently we need to use a
> > further 2 ACTION archetypes, which feels clunky to developers and looks
> > clunky in the tooling, as it requires encapsulation within a SECTION or
> > written documentation.
>
> right. Agree with this, though I suspect it doesn't quite cover all my
> issues.
>
> Can you give any examples?


> > I think we can largely resolve this with better tooling but we do lack
> any
> > easy way of asserting the relationship between the Instruction archetype
> and
> > the child Action archetypes.
>
> I thought this was in ADL 1.5?
>

There is a backward reference from each Action to it's parent
INSTRUCTION/Activity in ADL1.4 but we need a way to assert the relationship
in e.g a template so that this is clear to developers and clinical
reviewers, better still that these 'indicative' references are
automatically resolved at run-time with actual links where necessary.

Ian

Dr Ian McNicoll
office +44 (0)1536 414 994
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com

*Primary Health Info 23 ? 25th April in Warwick ? are you
coming?<http://www.primaryhealthinfo.org/>
*

Clinical Modelling Consultant, Ocean Informatics, UK
Director openEHR Foundation  www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
SCIMP Working Group, NHS Scotland
BCS Primary Health Care  www.phcsg.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120327/d9bc8d7c/attachment.html>

Reply via email to