anchor.diff:  
   Prop_Val = java.lang.Integer
   
  -.Normal Scenario 4) Configure 2 properties, Alias_Key and Alias_Value for each Table Association.
  +.Normal Scenario 5) Configure 2 properties, Alias_Key and Alias_Value for each Table Association.
   If there are more than one table associations, configure multiple pairs of these properties.
   
   The Prop_Val for ALIAS_KEY can be anything. 
  
positive.code: 
  Note that duplicate Aliases are removed during the cleanup phase. So having more than one of these configured is ok. However, in order to support ‘AND’ conditions with multiple fields in the SAME table, we need to replace <criteria> with a subquery template using Special Scenario 4 above. 
  
  .Special Scenario 6) Add Extra Alias for Special Cases
  Sometimes we have an alias that translates to multiple aliases due to hierarchy relationship levels. This EXCLUDES Observation Types Issues. For example, FURTHER.orders table translates to OpenMRS.patient.orders table. Therefore, we need another alias to support the Sub Level. We need the Translated aliases to be like this, where the ord will go through the patient object:
  
  
negative.code: .Part One (Query Translations)
  There are Normal Scenarios and Special Scenarios for Query Translations.
  
  .Normal Scenario 1) Configure Translate Attribute Name
  For each Attribute Name that requires Translation:
  
  Prop_Name = ATTR_TRANS_FUNC
  
  Prop_Val = translateAttr
  
  .Normal Scenario 2) Configure for DTS Coded Value Translation with:
  Prop_Name = ATTR_VALUE_TRANS_FUNC
  
  Prop_Val = translateCode
  
  .Normal Scenario 3) Configure for Data Type Translation with:
  Prop_Name = ATTR_VALUE_TRANS_TO_DATA_TYPE
  
  Prop_Val = xs:decimal (Or other appropriate valid XML Data Types)
  