Finder Questions

[chapindad]

Here is my very long search term:

“acquisition” OR “actual cost” OR “actual price” OR “ain’t what’s paid” OR “aint whats paid” OR “AMP” OR “APhA” OR “ASP” OR “average manufacturer price” OR “average price” OR “Average Sales Price” OR “AWP” OR “average wholesale price” OR “benchmark” OR “Best Price” OR “Blue Book” OR “BP” OR “Cardinal” OR “carve out” OR “chargeback” OR “CMS” OR “Centers for Medicare and Medicaid Services” OR “Direct price” OR “Discount” OR “DP” OR “DPW” OR “Drug cost” OR “Drug payment methodology” OR “Drug pric” OR “EAC” OR “FAC” OR “Facts & Comparisons” OR “false cost” OR “false price” OR “FDB” OR “First Data Bank” OR “First DataBank” OR “FSS” OR “generic” OR “HCFA” OR “IMS” OR “Ingredient cost” OR “invoice cost” OR “invoice price” OR “J Code” OR “MAC” OR “Margin” OR “market price” OR “Markup” OR “Mark-up” OR “Master Drug Database” OR “MDDB” OR “Maximum Allowable Cost” OR “MCO” OR “Medispan” OR “MMCAP” OR “multiple source” OR “multi-source” OR “multi source” OR “NAAG” OR “NACDS” OR “NAMFCU” OR “NASMD” OR “National Association of Attorneys General” OR “National Association of Medicaid Fraud Control Units” OR “net cost” OR “net price” OR “NWP” OR “PDL” OR “payment method” OR “Pharmaceutical Providers” OR “Pharmacy Association” OR “Pharmacy pricing” OR “preferred drug list” OR “Price Alert” OR “Price Chek” OR “Price Probe” OR “Pricing benchmark” OR “professional cost” OR “real cost” OR “real price” OR “rebate” OR “Red Book” OR “shortfall” OR “SLP” OR “suggested list price” OR “sticker price” OR “suggested price” OR “SUL” OR “State upper limit” OR “SWP” OR “true cost” OR “True price” OR “U&C” OR “URA” OR “Usual and Customary” OR “Ven-A-Care” OR “venacare” OR “WAC” OR “WHN” OR “Wholesale” OR “WLP” OR “WPP”

This search term returns a lot of extra emails. If you look at the preview it highlights the word “and” and “of” which are both in the search term but are part of a phrase and not by themselves.

Topic

[Support 2]

Thank you for providing the complex search query example above. A quick check reveals this issue is already documented in our JIRA database (ATG-273). We logged this in 2006 after an internal review and, until now, have not had any external customer reports on this issue.

Thanks again for the example, we can now take this use case into consideration during feature prioritization reviews (we added a reference to your post to issue ATG-273).

Kind Regards,

Advansys Support

[chapindad]

So… There is no fix? But it is a known problem?

[Support 2]

Yes, it is documented and we do not have a resolution. The scope of the work to fix the issue is yet to be determined.

If you would like to provide further background to your current and ongoing needs, to which we may be able to respond in more detail, please feel free to email us directly at support@advansyscorp.com.

Kind Regards,

Advansys Support

[Author]

Replies