Difference between revisions of "Q: How do I correctly map "Order-Level" comments and "Item(Result)-Level" comments?"
Jump to navigation
Jump to search
(Created page with "=Scenario= The lab/rad vendor is sending multiple NTE segments. Some contain comments associated to the order, while others contain comments associated to the result. Additionall...") |
|||
Line 1: | Line 1: | ||
=Scenario= | =Scenario= | ||
− | The lab/rad vendor is sending multiple NTE segments. Some contain comments associated to the order, while others contain comments associated to the result. Additionally, the comments can be sent across multiple segments, and as such, the concatenation of multiple segments is typically mapped to the corresponding FileResult_CMS parameter | + | The lab/rad vendor is sending multiple NTE segments. Some contain comments associated to the order, while others contain comments associated to the result. Additionally, the comments can be sent across multiple segments, and as such, the concatenation of multiple segments is typically mapped to the corresponding FileResult_CMS parameter. |
=ORU Message Definition= | =ORU Message Definition= | ||
Note that the key NTE associated is driven by the message definition. By specifying the parent segment, ORUs with NTEs occurring consecutively after the OBR segment(s) can be distinctly mapped to order-level comments. Along those same lines, ORUs with NTEs occuring consecutively after the OBX segment(s) can be directly mapped to result-level comments:<br> | Note that the key NTE associated is driven by the message definition. By specifying the parent segment, ORUs with NTEs occurring consecutively after the OBR segment(s) can be distinctly mapped to order-level comments. Along those same lines, ORUs with NTEs occuring consecutively after the OBX segment(s) can be directly mapped to result-level comments:<br> |
Latest revision as of 13:03, 20 July 2012
Scenario
The lab/rad vendor is sending multiple NTE segments. Some contain comments associated to the order, while others contain comments associated to the result. Additionally, the comments can be sent across multiple segments, and as such, the concatenation of multiple segments is typically mapped to the corresponding FileResult_CMS parameter.
ORU Message Definition
Note that the key NTE associated is driven by the message definition. By specifying the parent segment, ORUs with NTEs occurring consecutively after the OBR segment(s) can be distinctly mapped to order-level comments. Along those same lines, ORUs with NTEs occuring consecutively after the OBX segment(s) can be directly mapped to result-level comments: