Hello Everyone, I discovered the following issues in the latest spec. I would appreciate your perspectives on them.
1. DV_PARAGRAPH does seem to make any sense as a data type. This is more of a rendering issue. A paragraph can contain multiple observations, but the spec indicates that only DV_TEXT can be in the paragraph. In my opinion, a paragraph is a higher level construct than ENTRY and seems more synonymous with a SECTION. On page 24 of the RIM model it shows an example of DV_PARAGRAPH. However it only shows DV_TEXT items possible in the prose. What if you want to put other data types in the narrative prose? <DV_TEXT>blah, blah, blah</DV_TEXT><DV_DATE>July 16, 1999</DV_DATE><DV_TEXT>blah, blah, blah</DV_TEXT>.... I feel that if you go so far as to make DV_PARAGRAPH a data type, you should also create DV_SENTENCE, DV_BLOCK_QUOTE, DV_HEADER, DV_FOOTER, etc. (which also doesn't make sense IMHO). This is just the tip of an "iceberg" that I have spoken of before. openEHR needs a standardized spec for rendering visual representations of archetypes (i.e. an agreed upon style sheet language w/ a mandatory mapping to the RIM). 2. I can not find the class CONTENT_ITEM detailed in the EHR Information Model. This class is the superclass of ENTRY, but the fields (i.e. name, meaning, etc.) are not described. You feedback is appreciated. Cheers, Matias ============ Matias Klein President, CTO Ethidium Health Systems 3993 Huntingdon Pike - Suite 108 Huntingdon Valley, PA 19006-1927 USA Office: (215)938-8630 Fax: (866)583-8018 http://www.ethidium.com - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
