he structure is logically a keyed
>> list of values, where we never know the keys, and in the
>> 'conversion_details' case, because we are not currently sure of the
>> keys (and maybe we'll never have standard keys for that).
>>
>> - thomas
>>
>> __
a keyed list of
values, where we never know the keys, and in the 'conversion_details' case,
because we are not currently sure of the keys (and maybe we'll never have
standard keys for that).
- thomas
___
openEHR-clinical mailing list
openEHR-clinical at lists.openehr.org<mailto:openEHR-clinical at
lists.openehr.org>
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141120/83745581/attachment.html>
p://location.in.clinicalelementmodels.com>">
["tool"] = <"cem2adl v6.3.0">
["time"] = <"2014-11-03T09:05:00">
>
This is because in the first case, the structure is logically a keyed
list of values, where we never know the keys, and in the
'conversion_details' case, because we are not currently sure of the keys
(and maybe we'll never have standard keys for that).
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20141120/06ec350a/attachment.html>
On Wed, Nov 19, 2014 at 02:12:31PM -0300, pablo pazos wrote:
> The question was not "how to do X in a POMR", the question
> was "how to model a POMR in openEHR". Please read my first
> message to the list.
I certainly did.
I was not precise in my first wording. What I wanted to point
out was tha
4 matches
Mail list logo