Hi,
I was reviewing the latest specs and, compared with 1.0.2 where ACTIVITY.timing
usage is not so clear, I think we still need to improve that specific point.
1. timing description is too focused on medication
"Many Instructions will have only one Activity, usually describing a medication
to
On 17/06/2016 04:55, pablo pazos wrote:
Hi,
I'm preparing some materials for a course and I was reviewing the
HISTORY/EVENT package.
On the INTERVAL_EVENT field descriptions I noted that those might not
be 100% correct or clear. Before raising an issue on JIRA I wanted to
know what you
Done: https://openehr.atlassian.net/browse/SPECPR-197
I added this to the PR description: PP: is it possible to record a mean and a
max value no the same EVENT.data? e.g. mean syst BP and max syst BP in an
interval of time. Since there is only one math_function, for that we'll need a
completely
Thanks Thomas,
I would say that is a common use case when you are creating archetypes, since
the validation rules are not in the AE, I create the adl using AE but see the
validation errors on the ADLWB.
Also, I would consider not everyone has git installed. Think of a modeling
workshop with
Hi,
I created an INSTRUCTION archetype, under Definition > Current Activity there
is a checkbox "ordered" that seems not to be working since when I check it I
see the same on the ADL:
activities cardinality matches {0..*; unordered}
This is a question really, since INSTRUCTION.narrative is
Thanks Ian,
Maybe if narrative can't be coded text, we might want to add that clarification
to the specs or, as you suggest, use string as type.
What do members of the SEC think about this?
--
Kind regards,
Eng. Pablo Pazos Gutiérrez
http://cabolabs.com
From: i...@freshehr.com
Date: Fri, 17
6 matches
Mail list logo
