make archetypes quite brittle. i.e. when the archetype definition
is loaded into the clinical system I either have to consult the
URL straight away and store the resulting codes, or else delay
the binding and risk having the terminology codes for my
ADL disappear in the future?
why would
)
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20070107/8e1d9bf4/attachment.html
-- next part --
___
openEHR-technical
Andrew Patterson wrote:
make archetypes quite brittle. i.e. when the archetype definition
is loaded into the clinical system I either have to consult the
URL straight away and store the resulting codes, or else delay
the binding and risk having the terminology codes for my
ADL disappear in
Colin Sutton wrote:
The query tool needs to manage this, as it should manage the language. I
suggest the user (or user environment) should be able to select whether to
look at local terminology or that of another country (the default may be
where the patient's record was created, and the
Hi to all,
While revising my MST archetypes, I came across some confusion on the
use of cardinality and occurences. And when I reread ADL 1.4 and ADL2,
inspected the sample archetypes and then created new ones with Archetype
Editor and also tested with the Workbench my confusion got even more
5 matches
Mail list logo
