Connecting CPT to visit type in eBO

[zesty1989]

I'm trying to create a report in eBO (eClinical Works' reporting software) that maps our visit type to the CPT codes that are most commonly billed under those visit types. I formatted the table like this:

Appt Date / Patient Name / Acct # / Visit Type / CPT Code / Primary Insurance


When I tried to run the report I got this error message:
Cross joins (between query subjects: [Dictionary Building Blocks].[CPT Codes], [Import Layer].[EMR ENCOUNTER], [Import Layer].[VISITSTS CODES], [Import Layer].[PATIENT], [Import Layer].[PATIENT USERS], [Import Layer].[EDI FACILITIES], [Import Layer].[FACILITY GROUPS], [Import Layer].[PRIMARY INSURANCE]) are not permitted for the user who has the identity '*'.
Details:
CAF-WRN-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID:2018-08-31-15:06:36.434-#292

My supervisor thinks that we need to use cognos to get the cross joins to play nicely together. Is this true? If so, how do I make that happen?

[MFGF]

I'm trying to create a report in eBO (eClinical Works' reporting software) that maps our visit type to the CPT codes that are most commonly billed under those visit types. I formatted the table like this:

Appt Date / Patient Name / Acct # / Visit Type / CPT Code / Primary Insurance


When I tried to run the report I got this error message:
Cross joins (between query subjects: [Dictionary Building Blocks].[CPT Codes], [Import Layer].[EMR ENCOUNTER], [Import Layer].[VISITSTS CODES], [Import Layer].[PATIENT], [Import Layer].[PATIENT USERS], [Import Layer].[EDI FACILITIES], [Import Layer].[FACILITY GROUPS], [Import Layer].[PRIMARY INSURANCE]) are not permitted for the user who has the identity '*'.
Details:
CAF-WRN-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID:2018-08-31-15:06:36.434-#292

My supervisor thinks that we need to use cognos to get the cross joins to play nicely together. Is this true? If so, how do I make that happen?

Hi,

When you see cross-join errors like this, it often means that the modeller forgot to define one or more relationships in the Framework Manager model the package was published from. I'd suggest the first course of action is to look at the FM model and sanity-check the relationships.

Cheers!

MF.