Difference between revisions of "Talk:1.3.6.1.4.1.19376.1.5.3.1.1.10.4.1"

From IHE Wiki
Jump to navigation Jump to search
(New page: {{Fixme | In CDA R2, the classCode "TRNS" is a valid classCode for a general Act. However when an Act is under an Entry (as it is in Transport), the list of valid classCodes is constrict...)
 
m
 
Line 1: Line 1:
−
{{Fixme |
+
In CDA R2, the classCode "TRNS" is a valid classCode for a general Act.  However when an Act is under an Entry (as it is in Transport), the list of valid classCodes is constrained and TRNS is not part of this subset. 
  
−
In CDA R2, the classCode "TRNS" is a valid classCode for a general Act.  However when an Act is under an Entry (as it is in Transport), the list of valid classCodes is constricted and TRNS is not part of this subset. 
+
This problem is significant, but not majorly so, because the vocabulary used for code will indicate that this is some form transport act, regardless of the code system used.  The reciever may not understand the code system, which may make it difficult to location transport acts without knowledge of the template identifiers.  Regional extensions should constrain the code system to use an appropriate value set to support interoperability.
−
 
 
−
This problem seems significant, because the classCode is the only place at the V3 level where a parser could determine that this Act is in fact a Transport Act.  One can't rely on the code to tell us this, because, while the recommendation is that a transport-based codeSystem be used, it isn't required and therefore cannot be relied upon.  The only other option would be to rely on the IHE PCC Template ID, but this probably was not the intention.
 
−
 
 
−
}}
 

Latest revision as of 15:51, 30 September 2008

In CDA R2, the classCode "TRNS" is a valid classCode for a general Act. However when an Act is under an Entry (as it is in Transport), the list of valid classCodes is constrained and TRNS is not part of this subset.

This problem is significant, but not majorly so, because the vocabulary used for code will indicate that this is some form transport act, regardless of the code system used. The reciever may not understand the code system, which may make it difficult to location transport acts without knowledge of the template identifiers. Regional extensions should constrain the code system to use an appropriate value set to support interoperability.

Retrieved from "http://wiki.ihe.net/index.php?title=Talk:1.3.6.1.4.1.19376.1.5.3.1.1.10.4.1&oldid=24029"