Re: Archetype publication question - implications for implementers

2015-10-15 Thread Thomas Beale
I've skimmed the replies on this thread, and I'm inclined to think everyone could be right. Problem is, they can't all be right at the same time. So considering the issue from a global deployment perspective I had the folllowing idea: * in the archetype library, we should stick to

Re: Archetype publication question - implications for implementers [ long ]

2015-10-15 Thread Thomas Beale
Eric, nice summary of issues. If I can take the liberty of pulling out what I think are your key issues to worry about + recommendations. I bolded my own subset of those ... On 10/10/2015 10:07, Eric Browne wrote: *Notes on UCUM* * UCUM does not supply normative names of units. * Some

Re: Archetype publication question - implications for implementers [ long ]

2015-10-15 Thread Grahame Grieve
hi Eric Some comments: * UCUM introduces ambiguity, despite the above claim. > please demonstrate examples. > * UCUM does not provide a single code for each unit - it provides 2 > normative codes, as well as a non-normative display/print rendition and an > ad-hoc name. For each unit, UCUM

RE: Archetype publication question - implications for implementers

2015-10-15 Thread Heather Leslie
Hi Thomas, See my email from October 9 regarding how this has been resolved. There is now an updated v1 Blood Pressure archetype with addition of the correct units for Tilt added to the node and a note that the previous units are no longer to be used. It has been republished as a non-breaking