characters.
leo
Thomas Beale-3 wrote:
On 10/01/2012 10:05, Leonardo Moretti wrote:
If DV_TEXT doesn't allow to use carriage returns, line feeds, or other
non-printing characters, as stated in
http://www.openehr.org/releases/1.0.2/architecture/rm/data_types_im.pdf,
pag 29, there is a way
Hi all,
maybe this is a silly question, but I didn't find a point in the specs
where this is clearly explained:
The following notation on ADL:
ELEMENT[at0009] occurrences matches {0..1} matches { -- Pattern
value matches {
DV_DURATION matches {
value matches {PYM}
}
}
}
constraints the data to
If DV_TEXT doesn't allow to use carriage returns, line feeds, or other
non-printing characters, as stated in
http://www.openehr.org/releases/1.0.2/architecture/rm/data_types_im.pdf,
pag 29, there is a way to represent short text with minimal formatting
characters (carriage returns)? Which data
..
Regards,
leonardo
Thomas Beale-3 wrote:
On 26/05/2011 16:48, Leonardo Moretti wrote:
Hi all,
I thought a lot on your proposal.
If we want to use pseudo-units (non-UCUM terms), then we have to be able
to
distinguish when a term is in UCUM syntax. For example g/m2.7 is a valid
UCUM
Hi all,
I thought a lot on your proposal.
If we want to use pseudo-units (non-UCUM terms), then we have to be able to
distinguish when a term is in UCUM syntax. For example g/m2.7 is a valid
UCUM string, but it is interpreted as (g/m^2) * 7 and not as g/(m^2.7),
because in UCUM ?.? is the symbol
Hi
there are a lots of scientific publications treating the indexations of left
ventricular mass (LVM).
I can link some abstracts, but the whole PDF documents are not public:
- http://www.nature.com/jhh/journal/v23/n11/full/jhh200916a.html
- http://www.ncbi.nlm.nih.gov/pubmed/11729247
or here
Thank you Thomas,
I have clear how to use terminology_id and code for DV_CODED_TEXT, but here
I'm wondering if I can use the ordinal (integer) value as coded value in a
DV_ORDINAL, like in this example (note: code_string5/code_string):
items archetype_node_id=at0004.1 xsi:type=ELEMENT
name
I'm wondering which is the correct use of DV_PROPORTION and DV_QUANTITY...
When using DV_QUANTITY with property attribute 'proportion' and when using
DV_PROPORTION? Why can not we use always a DV_PROPORTION for proportion!?
--
View this message in context:
Hi Bert,
maybe also this links could be helpful..
http://old.nabble.com/%22state%22-and--%22protocol%22-structures-are-mandatory%2C-when-defined--td29174701.html
and
http://www.openehr.org/wiki/display/dev/Existence+of+Attributes+%28AOM,+ADL+and+XML%29
Leo
BertV wrote:
Hi all,
I
it is 0..1 we agree on that
if it is defined in the archetype i think it is mandatory, so 1..1
however the items inside the ITEM_STRUCTURE (suppose ITEM_TREE) can be set
to 0..1
so.. it is requierd, but not the content..
Alessandro
On 16 July 2010 14:09, Leonardo Moretti lmoretti
Hi Alessandro,
items cardinality matches {0..*; unordered} is referred to items elements,
not to protocol element
This means we can have something like this:
observation
data
...
/data
protocol archetype_node_id=at0011 xsi:type=ITEM_TREE
name
value*List(en)/value
/name
/protocol
Hi Ian,
in my opinion an empty string has a semantic difference with a null value.
Empty string is however a valid value. For example, I could have different
cases for Comment in openEHR-EHR-OBSERVATION.blood_pressure.v1:
- a non-empty string with the comment on blood pressure measurement.
- an
ian at mcmi.co.uk
Clinical Analyst Ocean Informatics openEHR Archetype Editorial Group
Member BCS Primary Health Care SG Group www.phcsg.org / BCS Health
Scotland
On 29 June 2010 12:26, Leonardo Moretti lmoretti at noemalife.com wrote:
Hi Ian,
in my opinion an empty string has
]
}
}
}
}
Regards
leo
Leonardo Moretti wrote:
Ok, Ian,
using a null value, a null flafour is needed.. For your example cases:
a) The doctor simply did not add any comment.
b) The doctor purposefully 'added an empty string' by clicking through the
data entry widget, perhaps
Thank you Ian, you are right, null_flavour tag is not needed.
But in the previous post I proposed also an other change: in the original
ADL code
ELEMENT[at0033] occurrences matches {0..1} matches {-- Comment
value matches {
DV_TEXT matches {*}
}
}
value doesn't
4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com
ian at mcmi.co.uk
Clinical Analyst Ocean Informatics openEHR Archetype Editorial Group
Member BCS Primary Health Care SG Group www.phcsg.org / BCS Health
Scotland
On 29 June 2010 16:13, Leonardo
Hi koray,
I added a PR for each problem I found:
http://www.openehr.org/issues/browse/AEPR
Best Regards
leo
Koray Atalag-3 wrote:
Hi Moretti, I noted similar problems and discussed with Tom. He suggested
that we create a PR.
Here is another problem:
AE allows in specialisation setting
Thanks to all,
I agreee with Sebastian, the real point is knowing how much this order
actually matters, practically and theoretically!
Currently, XML-schemas are the only formal specs of how the xml must be
done, so I think we need to be compliant with these!
@Sam Will new XML schema for
Moreover,
XMLSerializer.output() produces xml fragments for DV_ORDINAL like this:
children xsi:type=C_DV_ORDINAL
rm_type_nameDvOrdinal/rm_type_name ...
while I'm expecting to have this
children xsi:type=C_DV_ORDINAL
rm_type_nameDV_ORDINAL/rm_type_name
Probably XMLSerializer is
been fixed in Rev 504 earlier this year.
See e.g. the APGAR score archetype at
http://openehr.org/knowledge/OKM.html#showArchetype_1013.1.172_7
Regards
Sebastian
Leonardo Moretti wrote:
Moreover,
XMLSerializer.output() produces xml fragments for DV_ORDINAL like this:
children xsi:type
think of persistent compositions as Managed Lists (current
medications, allergies etc)
I wondered how you were interpreting it?
Cheers, Sam
-Original Message-
From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
bounces at openehr.org] On Behalf Of Leonardo
Hi all,
I'd like to define persistence for a composition dinamically (and not
statically in an archetype), because this property changes depending on
application or application context.
If I'd like to define a composition as persistent, could I define this into
a template? Is this the correct
22 matches
Mail list logo
