New Care Credit Integration Setup Problem

[drtech]

Seems to be a problem with the Care Credit Integration setup. When I input the Merchant Number, it accepts it if I don't "enable" the program link, however as soon as I click enable and OK, it says the merchant number must be a 16-digit number...however it IS a 16 digit number I have entered...

OD v 20.3.39 - self compiled, running mysql on linux server

[drtech]

looks like the program is not validating the number setting the value of CareCredit.IsMerchantNumValid, so it is kicking it out...

[drtech]

...and the Care Credit Apply, Reports, Lookup, Manage, Quickscreen buttons seem to all be pointing to a Null link...and take me to nothing....is there a setup I am missing that is not in the manual? (I do not have clinics enabled, seems like the code is referencing clinics in the code of those buttons?)

[jordansparks]

You re-copied the RequiredDlls into your bin folder? We change them sometimes.

[drtech]

Yes, copied all of them again...no change. Still says it needs a 16 digit number, but it is 16 digits in the box, when I go to enable the program link. Is there a required file missing from the SVN maybe?

[joes]

The Care Credit integration only works with a registered copy of Open Dental. The CareCredit.IsMerchantNumValid() method that drtech referred to that is causing the issue is part of Bridges.dll. A functioning copy of Bridges.dll is not available from the public repository, and is only installed when a registered copy of Open Dental is updated to or beyond version 20.3.

[drtech]

so, the open source model for "Open Dental" is no longer the case?

[nathansparks]

so, the open source model for "Open Dental" is no longer the case?

Good question! This answer to the question is that Open Dental is still Open Source, nothing has changed. This 'program link' content, in this case, is protected by a licensing agreement with a third party. Third party/program link code that is outside of the primary function of the software is sometimes in a protected dll. Other distributers do this also, so if another compiler has special behavior they want to introduce, it may go into a dll. Sometimes we distribute the dll, like with CDT.dll, but in that case we need to make sure first that the entity to which we distribute the dll has a proper legal agreement with the owner of that content. We do this not because we have to, but because we think it is in the interest of the dental community to have access to the dental codes. In this case there is no argument that it is necessary.
In general, just because we are giving the primary code base to the Dental Community through our licensing, that does not mean that we might not sometimes add non-essential functionality that is only for our customers. We also do this with web forms, in program help, patient communications, patient portal, etc.

[drtech]

So, this is part of E-services now? That is not how the manual seems to read, nor does it seem like it needs to be a part of e services as it should be connecting with care credit directly. I understand some of those other services you devote online computing resources for on an ongoing basis for users to interact with and therefore most charge monthly fees... Just disappointing that things seem to be moving in a direction of things not available to use for compiling users. Been a fan, contributer, and user of Open Dental for 14 years, but not liking this direction...

[nathansparks]

No, it is not currently part of eServices. It is a third party program link available to customers with proprietary third party code that is not Open Source. We may add eServices that offer Care Credit functions in the future (I like the idea).

[drtech]

so can we buy the *.dll to make it work?

[jordansparks]

I'm pretty sure we can just give it to you.

[allends]

Dr Fuchs,
The Bridges.dll is available to all customers who have a current support contract since we package it with our updates.

The Bridges.dll has code that tells CareCredit that Open Dental is making the call to them, it poses a significant security risk for us to allow non-authorized versions of Open Dental to utilize it, since they could maliciously pose as us.
As a self-compiler, you are free to continue utilizing our open source code to create an integration for CareCredit that you can use, but we are unable to give you our Birdges.dll since it is effectively a representation of our company when it comes to CareCredit.

[jordansparks]

I'm going to rephrase that. The dll cannot work with any version of OD where the source code was changed in any manner. This prevents hacking of the dll. It's technically impossible for that dll to work for you.