Difference between revisions of "Datatypes R2 Issue 22"
| (One intermediate revision by one other user not shown) | |||
| Line 9: | Line 9: | ||
o displayName: A name, title, or representation for the code as it exists in the code system identified by the value of codeSystem. This must be a valid human readable representation of the code as it exists in the code system at the time of data entry. Normally, this would be the human readable representation of the code that the sending system shows to its users. The displayName is included so that an unaided human interpreter of a code value has a human readable description of what the code meant within the code system at the time of data entry | o displayName: A name, title, or representation for the code as it exists in the code system identified by the value of codeSystem. This must be a valid human readable representation of the code as it exists in the code system at the time of data entry. Normally, this would be the human readable representation of the code that the sending system shows to its users. The displayName is included so that an unaided human interpreter of a code value has a human readable description of what the code meant within the code system at the time of data entry | ||
| − | o | + | o Translation: A set of other CDs that each translate this CD into equivalent codes within the same code system or into corresponding concepts from other code systems. |
(approved 13-Sept 2006, Vocab & INM) | (approved 13-Sept 2006, Vocab & INM) | ||
| − | |||
== Discussion == | == Discussion == | ||
| + | [LeeColler] I believe we need to constrain originalText to certain types. According to the original spec, ((ST)x).equal(x.originalText) which implies that whatever representation originalText is it must be possible to demote it to a string. -- Better yet, can we constrain it to ST? | ||
| + | [LeeColler] On displayName, "valid human readable representation" I'm not sure what "valid" adds, perhaps other than to imply there are "invalid" human readable implementations. I'm not sure what those would be (and leaves open the question as to whether any medical representation is "human readable"). "natural language" might be a better term. | ||
== Links == | == Links == | ||
Back to [[Data Types R2 issues]] | Back to [[Data Types R2 issues]] | ||
Latest revision as of 13:37, 16 May 2007
Data Types Issue 22: New CD definitions
Introduction
Revised definitions as approved by Vocab:
o originalText: The text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. It is valid to use the CD data type to store only the text that the user entered or uttered. In this situation, original text will exist without a code. In a situation where the code is assigned sometime after the text was entered, originalText is the text or phrase used as the basis for assigning the code.
o displayName: A name, title, or representation for the code as it exists in the code system identified by the value of codeSystem. This must be a valid human readable representation of the code as it exists in the code system at the time of data entry. Normally, this would be the human readable representation of the code that the sending system shows to its users. The displayName is included so that an unaided human interpreter of a code value has a human readable description of what the code meant within the code system at the time of data entry
o Translation: A set of other CDs that each translate this CD into equivalent codes within the same code system or into corresponding concepts from other code systems. (approved 13-Sept 2006, Vocab & INM)
Discussion
[LeeColler] I believe we need to constrain originalText to certain types. According to the original spec, ((ST)x).equal(x.originalText) which implies that whatever representation originalText is it must be possible to demote it to a string. -- Better yet, can we constrain it to ST?
[LeeColler] On displayName, "valid human readable representation" I'm not sure what "valid" adds, perhaps other than to imply there are "invalid" human readable implementations. I'm not sure what those would be (and leaves open the question as to whether any medical representation is "human readable"). "natural language" might be a better term.
Links
Back to Data Types R2 issues
