Coded Term (VTA) does not get used in TMS Derivation (OC discrepancies remain in 'TMS IN PROGRESS' / 'TMS EVALUATION' Statuses)
(Doc ID 2748919.1)
Last updated on FEBRUARY 03, 2021
Applies to:
Oracle Clinical - Version 5.2.1 and laterOracle Thesaurus Management System - Version 5.2.1 and later
Information in this document applies to any platform.
Symptoms
i.
After an omission is coded then it does not get used in TMS derivation (executed as part of Batch Validation). This results in the TMS Discrepancy remaining open in the Oracle Clinical 'Discrepancy Database' with a review status of:
- 'TMS IN PROGRESS' or
- 'TMS EVALUATION' (if an 'Unanswerable' action has been applied in TMS => Batch Validation executed => OC user sets discrepancy status back to 'TMS EVALUATION' => Batch Validation executed)
ii.
A record exists in the TMS_SOURCE_TERMS table for the TMS discrepancy (usually the EXT_VALUE_8 column holds the Oracle Clinical discrepancy_entry_id).
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |