Open Dental

It's supposed to be cleared out after use. We'll get a fix out immediately. I thought we fixed it a few weeks ago, but it still seems to be there.

1. I just meant that the leading spaces were messed up in large portions of the code, so that change would fix it. 3. Delete, OK, and Cancel events always come at the end of the file, that's all. 5. Oh, I forgot that the family module never appears. But usually, the referral is determined from their...

Sure. If you have two offices. They each have their own database, but the databases are identical and continuously synchronized. Both offices are connected via a VPN so that it is like one big network where you can see all the other computers at both offices. So each workstation connects to the data...

I had to remove this new button because of the following problems: 1. Leading spaces instead of tabs. Large sections of the file were affected due to designer generated code. 2. I don't recall any discussion before adding this new feature. 3. The code for the event was located at the end of the file...

Fixed

Yes, it took us a few months to ease into it. Derek built a web interface for it. I found that interface to be too clumsy, so I built my very own Windows interface. So it took us a while to get everything going. But I use it full time now. For now, just the OD staff are submitting bugs. I'd like to ...

OK, I see it now. Yes, I can duplicate it, so I'll put it down as a bug.

As with all planned features, we can never give an estimate of when they might happen. Any estimate we give would almost certainly be very wrong.

Zoom. Well, there are plans to let you resize the tooth chart to some degree. That would probably satisfy your need.

No. It actually sounds like a Windows malfunction to me. The main program window wouldn't be tucked under the task bar otherwise. I have had this happen to me on one computer temporarily.

Yes, of course it's complicated, but that's ok. What we will do, of course, is create an Inbox. We'll also make it so that incoming email will automatically attach itself to the correct patient.

As I replied on the other thread, an extension would make it too clumsy. It's more of a core issue, so it's something that we should add.

Not really. Changes get made to the Task feature with each version. Eventually, that will be possible.

Oh, global as in "same for all computers". I just added mounts back in.

A USB drive makes a lot more sense to me.

The sensible place to put this button is in the Confirmation List window. That window already handles all user interface functions such as letting user pick a date range, displaying a list of appointments to confirm, letting users deselect some appointments, etc. If you build it anywhere else, it wi...

It will be released soon, so no more new features (even though I don't notice anyone else actively working on it).

1. I would treat it like any other broken appt. Break it. Then either delete it or move it to the unscheduled list. If it gets deleted, then they will show up on the recall list again. Procedures stay on the TP and may be removed later if needed. 2. Usually you just delete it from the Unscheduled li...

Good point. Obviously, I did consider a combined list, but it turned out to cause some difficult complications. For now, I had to settle for separate lists for each supplier. As with all new features, the first version is not going to be terribly slick.

Greetings. We do have some translations for about 8 different languages now. Many of them, including Spanish are not posted simply because we're so busy. We're hoping to entirely automate the sharing of translations between users so that we won't ever let it get behind like this again. But for now, ...

I can't figure out right now why it's not showing in the SVN 5.4 folder, but I see it in the head. It's in the RequiredDlls folder.

It's because you are in China. Check your system Date format in the Control panel. I think you are accidentally switching the day and month. The other possibility is that we simply haven't tested it on the Chinese calendar, and that there is a small bug when using that calendar.

You can make the path local if you want, right? Some people share their database folder on the network. So those users can make a backup from a workstation. Obviously, this security risk is not acceptable to everyone.

It's planned.

Is it terminal services?

Well, I really don't think it's a good idea to do any manual manipulation of the database, and that includes adding indexes, deleting old data, or whatever. Having said that, I think it's probably safe to delete old securitylog entries. It's also safe to clear out the signal table. But do this at yo...

Still using 2005. Try another update. A day or two ago, I made a commit that actually crashed while in design mode. But I've committed a fix. Otherwise, I don't know.

I thought about it some more. I don't think the UK version would provide any advantage over the blank database that came with the trial version. I think the database that comes with the trial version is just what you need. But I also think that the database that you attempted to update will also wor...

Moving to a Linux server does not increase performance afaik. Response time seems to be the same. Sure, securitylog table will increase. That's the downside of keeping a history of all changes. 10MB isn't really that big of a deal when you think about it. But emailmessage? I can't imagine for the li...

Hmm. No, the bug is still there, but I'll try to make it a higher priority to fix it. It's unusual for us to let a bug languish for so long. I won't bore you with why it has happened in this case, but I will say that it's a simple fix. As for the hardware, that's a different issue. I honestly don't ...

That question is entirely too complicated to handle through the forum. I don't think the program is doing anything wrong. I think it's working as intended. We just need to look at what you are doing using a remote connection.

No, you're certainly not the only one with this request. But each user requests this in a slightly different way. It's honestly hard to know exactly what people are asking for, and hard to come up with a report that will please everyone. You see, I pull up my monthly P&I report regularly, and it doe...

I just added it back in as an option. I thought that would be faster and more reliable than trying to track down how to make it more efficient. I didn't notice any difference on my db either. But we did get a copy of a db that was very slow. We did not specifically tie it to this feature, but commen...

OK, I'm adding it back in right now.

Really. I thought David was the only one using it.

Text import... Do you mean the XML import or the tab delimited import?

We had to disable it due to serious performance issues in larger offices. If we enable it again in a future version, it needs to be optional.

My apologies. We will post a new UK database just to be sure.

Have you seen the database documentation here?: http://www.open-dent.com/manual/programmers.html Basically, the process is fairly straightforward if you stick to just the patient table. But once you start moving beyond that, it's just too complex to explain on a web page. We have full time staff and...

I'll put it down as a bug until I have a chance to look into it further. But I think it might actually preserve the original date. I know the notes audit cannot be altered no matter what you do.

It should have changed the way the TP was calculated. It will now use the fee schedule of the office/provider as the fee for the procedure rather than the fee on the PPO fee schedule. In this case, you would use the PPO fee schedule as the fee schedule for the insplan.

Putting a writeoff on a preauth is something we didn't anticipate a user attempting to do. You are correct. I suspect that the actual solution is going to be for us to immediately eliminate any existing writeoffs on preauths, and then never allow them again. I think the reason we didn't anticipate i...

-It's not available everywhere. Only certain states, and only certain cities within those states. -It can't tell you anything about subscriber or individual eligibility, but rather only about specific plans in general. -Expense. Those are the three reasons I've heard for why some people don't use it.

It's far too complicated to explain on a forum. We have a very standard routine for handling this issue: 1. Make sure user is on a recent version. (you didn't say what version you use). 2. See if the db maint tool fixes it. 3. Get a copy of their database. 4. Add a routine to the Database Maintenanc...

OK, I just used the new DataObject framework for the last 6 or so tables that I added. It's working very well. I did run into one issue that I think needs to be addressed. I think a field like this: [DataField("Descript")] private string descript; bool descriptChanged; /// <summary>The description c...

When large corporations call, they tend to ask us if we have a central database. If we use circular replication, we can't honestly answer yes. So I don't see it as the final solution for enterprises. But it may indeed scale up well beyond ten servers.

Are you talking about until you memorize your status colors. We look at them all day long, so it doesn't take long to memorize the colors that are used. Unless I misunderstood.

Which claimform? Is it the 2006, or is it a different one? I would sort of need to see your screen.

Double click on the procedure (not the procedure code), and then at the bottom, double click on the estimate. That's where you would always go to override estimates that look wrong to you.

It does not contain any procedure codes unless you live in the USA.

I like the idea of a catalog server. But as I indicated in the last post, I think that's a battle for another day.

Problems with mysql proxy: 1. We don't want certain writes to be passed to the other servers. Especially message buttons and certain other signal entries. 2. We would have to learn the language used for proxy functions. 3. Adding or removing a server node would require altering the proxy scripts on ...

Finally some technical explanation of what you had in mind. But I'm still far from convinced that it's workable. I can see that it's marginally possible with 2 masters and one slave, but they do point out that it's dangerous. So now you're talking about making the central server a slave to 50 other ...

Complicated question. The simplest solution is to edit the estimate for the core, and override the percentage to 50%. But to have it do that automatically, I would have to see your screen and look at how you have set up your percentages. I think cores would fall within the basic restorative category...

Run a report on the resulting adjustments.

Try our "1500" claimform instead of our "HCFA-1500" claimform. It's downloadable from our medical insurance page.

Yes, it should be deleted after use. It is becoming more and more common for us to use temporary tables, and sometimes those tables don't get deleted if we don't specifically add it to the query. I didn't think about it breaking your replication. I did add a delete clause in a recent version (not su...

The beauty is that you can have many-to-many replication, as long as you correctly "partition" your data. If each sever is the "master" for the data managed by the practice it belongs to, you can have all that data replicate. Then, all data is available at all branches. They have read-only access. ...

Go to Setup | Data Paths. Do you have the box checked to not use AtoZ folder? Checking that box will make the ClaimForm setup unavailable and might also cause your background to disappear.

No, it's not in that window any longer. It's still just as easy to enter it from the main window.

It's not a bug. It was supposed to have this behavior all along and recently got 'fixed'. That's the whole point of the patient ID is to override the subscriber ID.

I don't think that's what drjrl is talking about. Everyone experiences the edges of their claims getting cut off to some degree. This is simply due to the fact that printers can't print that close to the edge. We can't shrink them, or the insurance companies tend to have trouble scanning them. I con...

You can reassign them in bulk in Setup | ClaimForms. But are you compiling, or are you using the version you purchased from us? The purchased version does include the claimform background. If you don't see it, you should call us.

Simple. Don't ever download from the "head" folder for versions that you will use with live data. Instead, download from one of the named version folders. Don't jump the gun and try to use a version that has not been reported as being released yet on our previous versions page.

Anything is possible. But it's low priority at the moment. The way you avoid this issue is by establishing the proper office flow. While the patient is in the chair, the only person allowed to touch that patient's chart is the chairside assistant. Do not let the patient get up to leave until all cha...

Please tell me you're not using 5.4.0 with real patient data. That version is NOT suitable for use in a live setting, and it says so right at the top of the page in big red letters. http://www.open-dent.com/manual/developers.html . But I did just notice that there was no such warning at the top of t...

I finally decided that the most elegant solution is to have the program default to the first category instead of to the quick buttons. This will avoid yet another option field in the setup windows. This will also make the trial version work better.

Use version 5.4. Click the popup button in the main toolbar. Type in the note.

ewlooney, are you asking me or Frederik? If you're asking me, I think we're talking about having one virtual database common to 50+ offices. Due to the complexity, I would be happy with a replication delay of up to an hour. Or even a delay as high as one day could be compensated for as Frederik sugg...

I don't know. The "owner", as you call it, seems like a secondary consideration. I'm much more interested with how to actually pass the data up to the centralized server. Data that's already on the centralized server can be replicated; no problem. But pumping data back the other direction is going t...

Excellent idea Frederik. That's the direction to go. Let me think about it some more.

Well, the current version has a bug that causes a problem in Linux or Mac. It's in the procedure edit window. Other than that I don't think there are any problems. I think we will do some testing today on Linux to take care of that bug.

Time is now one of the optional columns in the Chart module. Also, all commlog entries always recored the time. Procedures do not currently. So that phonecall would be a commlog entry.

I know you can set those server variables, but that seems a lot harder to the end user than just letting OD take care of it. We do it automatically. Also, it works for Oracle. I don't believe MySQL can do the 'star' replication that you refer to. I don't believe you can have multiple masters replica...

Forgot about that.

Our long term plan is to keep a database of these fees on our server, and have all of our users automatically populate that database with fees as payments come in. Then, have those fees go back out from our database to each office. The huge problem with making this work right now is that there is no...

No. Everywhere. But then, not again for 10 minutes or unless you change the note.

Hmm. I guess I can't argue with that. I'm used to thinking of intraoral cameras as a $10,000 money pit. I guess it's time to order some.

I think you forgot to install the dotNet framework first. Either that, or you have antivirus software that's interfering.

The key piece of information here is that it won't pop up again for the same patient on the same computer for 10 minutes.

Good post. Yes, I've been aware of the way it's handled in MySQL, which I refer to as circular replication. We do support circular replication. And certainly, the program must be specifically tailored for this. The program must prevent and handle duplicate keys. Or, as in the case of the flow chart ...

I'll put that down as an option.

Yes, that's correct. But what Dr. Neelley was asking for was to not have to do all the work of looking up each med the first time. It's a reasonable request. It will happen, just not sure when.

Since 9 million records were stolen, that works out to about a fine of 10 cents per record. So maybe the risk to a dental office with 5000 patients is something like $500 plus lots of bad publicity. This is a little bit tongue in cheek. I am well aware that the risk doesn't necessarily scale like th...

There used to be. I'm not sure where the button went. I'll put it down as a bug.

It was fixed in 5.3.16. So you're just not current enough.

It was fixed in 5.3.16. So you're just not current enough.

Yes, it's planned. See our future versions page.

I don't know. It's been at least a few weeks since I attempted to run on Linux. Hopefully this will get better soon as our Linux workstation comes on line for use with real patients.

I think it's related to which printer you have setup. I notice that you are in debug mode. Is that what you intended?

Sure. We built it. We plan on posting the source code in case other resellers want to provide the service to their customers. We also plan to create a web page to describe the new functionality. In short, everyone gets a registration key now, even users in foreign countries. When you push the update...

Really? That's interesting. I'll put those both down as bugs.

The programming isn't too hard. A simple symmetric encryption strategy would make those numbers unreadable in the database. And the current security framework would prevent unauthorized access. We would probably also have to encrypt insurance subscriber id's because those are frequently the same as ...

Copied from another thread posted by Yorek: with identity theft making the headlines almost every day, Are there any plans to encrypt patients' Social Security and Credit card #'s? No matter how hard we try, laptops get stolen, USB drives get lost and we even hire a bad person unknowingly. I try not...

This deserves a new topic. I will start it.

Thanks.

Good point. That window was built before we had the grids with automatic line wrap. So it might just be time to put it all into a scrollable grid with a search filter.

Yes, that would be nice. As we add images to the new sheets framework, the 3D tooth chart could play out in a number of ways. It's going to be interesting.

I think today will be the day.

It's easy for us to add password protection specifically to P&I reports. What's harder, and what one user actually keeps requesting, is that dentists be blocked from seeing each other's P&I. But that's not what you're asking. Your request is easier. And no, we can't say when it will happen. We are p...

No, it's not yet plan specific.

On http://www.open-dent.com/manual/multiplelocations.html , we list the Replication Support option as our currently preferred option for supporting multiple locations. We also provide a link to the mysql website, which shows this image: http://dev.mysql.com/doc/refman/5.1/en/images/scaleout.png The ...

Thanks.

Any procedure code will work. Any combination of letters, numbers, spaces, punctuation, whatever.

The patient age shows in the Chart module in the grid at the lower left. If you don't see it, then try a newer version.

Your office is certainly pushing the limits of what's possible. I commend you for being so persistent. We have made a number of improvements specifically due to needs that arise directly from your office and its unique setup. For those who are unaware, your office is using circular daisy chain repli...

Less than a week until we release the beta.

Since you don't have SVN commit priv yet, I guess I'll go ahead and add that field this weekend.

You mean when you hit the New button in the Procedure Codes window? In the New Code window, right? Those types that you see there are only useful in that window. They just automate the other boxes in that window. So if you've already added the codes, then there's no point in adding another type, too...

I can't duplicate it. When I move appointments from one column to the next, it always changes according to the column, never to the primary provider for the patient. Are any of the providers assigned to the operatories hidden? I would need to see your screen I think.

But do you have SVN commit priv? If not, call.

We could? How would we check if program terminated normally? It crashes hard.

DateEntryC is a security related date, because only completed procedures affect finances, so we have to very carefully track when a procedure was actually marked complete. ProcDate is the date that shows to the user; the ordinary date. I agree it's time to add "DateTP". We have a number of users who...

Didn't overhaul the deposit slips; just the daily payment report.

We have run across this problem a time or two. It's fixable by doing just what you did. Note: your hardware driver is the one that crashed the computer. So our reasoning is that it's rare, it's not our fault, and it's solvable. We've looked at many different solutions. If it was stored in a local co...

Once we can automatically grab benefit info from in the ins co, the plan details you described won't be hard. I think it would look like separate deductible overrides for each separate xray procedure code. Too much work for a human to type in, but easily done if automated. Actually, we'll also have ...

Well, the good news is that, internally, we already do track D0xxx deductibles separately from D1xxx deductibles. But you're saying that even within the D0xxx category, they are being differentiated? Exams have no deductible, but radiographs do have a deductible?

It's a very good idea, and something that we should strive very hard for. I can't give you an immediate answer to that question because of the complexity. It's something we'll have to mull over for a while. One alternative is to enhance the email merging functions entirely independently of sheets. W...

The problem with another status is that it will make our jobs as programmers very difficult for a while. Status is how we calculate patient balances, and it will create a potential for bugs. I would rather simply automate the process better. Status EO. Date today. Green X. Possibly even link a refer...

That would be Unscheduled list. We have a nearly identical Unschedule List. We currently track broken appointments as adjustments in the account. Dentrix tracks them in a different way (I can see it in my head, but can't remember the name of that screen). You'll find that we are a superior alternati...

Hmm. That's a first. Good point though. We are moving quickly towards letting users customize their statements and other printouts. It would be able to handle situations such as this quickly. Until then, I can't think of a way other than to include it as a general note as part of the billing. Then, ...

The math involved in appt calculation is explained in the manual. It's doing what it was designed to do. It just needs to be overhauled to handle offices that use fixed chair times.

It's still planned. When lab cases were recently overhauled, lab printing never quite made it in. It's actually going to work out for the best, though, because we have a new framework that we're building to handle all printouts generally, and lab slips can become part of this new framework.

There is slightly better feedback on claim status. Deeper integration with Tesia is still planned.

Yes, insufficient funds would also go in as negative payments. Insurance writeoffs would only happen with PPOs right? I mean you have to have a contract with the insurance company, or you wouldn't write it off in the first place. Version 5.3 has better handling for writeoffs. Just do it when enterin...

Yes, they could. The only good solution I can think of is to physically lock down your hard drive/computer with metal straps and quality locks. Or, you could take the data home, restore it to make sure it works, then delete it from the computer, and physically secure the USB drive in a safe.

Well, the statement printing issue might be because you are using the debug build instead of the release build. As for the claimform, I don't think anything changed there. Which claimform?

We actually just built a framework for that. So far the only part of OD to be moved over to that framework is the labels function in version 5.4. But I consider that to be very important. We make a major thrust in that direction about once a year, but each thrust has so far largely fizzled. Maybe th...

They really aren't functional yet. We still have to build that.

You're aware of all the changes in 5.2 related to providers right? You might notice that we NEVER reallocate existing splits. Instead, we simply make adjusting entries after the fact. No new tables were added. I'm assuming your additions would enhance the existing framework rather than moving in a d...

Excellent idea.

Don't even try to use autonotes before version 5.4, which is not yet available. In earlier versions, the menu option was not supposed to be visible, but it looks like it did slip through accidentally.

That's the whole reason why we don't currently offer an outsourced solution for billing. It isn't in any particular table. It's dynamically generated from roughly a dozen different tables using some fairly complex math. There are some good solutions to this problem, and we are moving in that directi...

I will look into it, but I can't until next week, as I'm on vacation.

Those would be entered as treatment with a status of EO (existing restorations, other dentist). They will show as green. But all of the ones you mentioned do not have graphical equivalents. Our plan is to let users draw on the 3D chart with a pen or mouse for such things.

I edited your post slightly. Did I do it correctly? What country are you from? If not from the USA, then we can't release the American procedure codes. Is that what you wanted to know?

Yes, we're working on it.

I agree that would be better. There are just other very pressing needs right now. We'll get back to that at some point.

Yes, the holder certainly does open the bite. When taking a molar BW, the patient is biting on a plastic tab around the area of the canines. You can imagine how much this opens the bite. I'm getting BWs with pretty much zero bone level showing, and I'm using a #2 sensor. You can't take vertical BWs ...

Wired sensors are pretty much useless for BWs. The patient CANNOT bite together all the way, because it would squish the cord. This is especially a problem for patients with a deep bite. The only patient we've gotten a tolerable BW on was one with a slight open bite in anterior. I don't know why thi...

Right. I'm not sure what an "acct user code" is. What screen are you talking about? How is it labeled on the screen?

Yes, they will eventually be formalized somehow to be handled differently. But it's a low priority. They can be deselected when printing a deposit slip for the other checks, so they still shouldn't mess up the daily total.

Hmm. I'm not sure how it got that way. In any case, it's a user configurable option, just like for any procedure code. In the proc code edit window, change the area of the mouth to tooth.

I'll put it down as a bug in 5.3. That way, we can fix it quickly without making him wait for 5.4.

See the bottom of this page: http://www.open-dent.com/manual/reportprodinc.html. Basically, you need to use a negative payment rather than any kind of adjustment.

Still having trouble with the holders. For example, the BW holder only passes across the occlusal of the premolars even when taking a molar shot. This causes the entire thing to tip unpredictably forward and backward. It's as if someone took a BW tab and fastened it only to the very anterior 1/3 of ...

Oh, really? Yes, I just verified that it is not hiding users properly. I'll put it on the bug list. Thanks.

First, you upgrade to version 5.2. Then, you go to the Security window and hide them there.

Frederik, You made mention of this issue in the last few commits. I would like to know if this is an issue specific to Linux, or if it applies to Windows as well. I have no intention of trying to install anything in the GAC. And even on Linux, my installation strategy is to have all dll's in the app...

Since my last post on this topic, we have fixed a bug in the program that was requiring the "right click run as admin" sequence. This is no longer required in current versions.

Later versions have more elegant support for video cards. There are still issues that can happen, but we have solutions for all of those issues now.

Let's say you have 50 clinics, and you want them all to have separate databases for speed and in case their internet connection goes down. You want all 50 servers to have the exact same virtual database so that you can see all the patients and run complex reports. Replication would do this. It would...

The X12 specification certainly allows for the carrier to pass all of this detailed information. Our database was designed to mimic the X12 fields to greatly ease the sychronization of this info. That's why the "benefits" section of each insurance plan looks so complex and is in its own window. It f...

You shouldn't have needed to install any twain files. We don't use those. To our eyes, the quality looked identical to that of Apteryx. But we don't have any enhancement filters yet, so I think they have the advantage there if enhancement is needed.

I suppose we could add it as an option at some point.

Right, just change the category. My favorite category names for this sort of thing are "obsolete" or "never used". Some day, we'll let users delete codes, but it's not a high priority right now.

Done. The patient could not bite all the way together. She was not impressed. There seems to be one glaring issue in OD: rearranging the images on the mount. I think we already programmed that, so I'll have to go see where that option went.

I spoke too soon. After I read the directions, snapping the vertical cage on wasn't too bad. But I will need to order more durable sleeves. It's worth the money to avoid moisture on the sensor. We'll be taking 4BWs in about an hour. Wish me luck.

Well, I hooked up my Suni sensor today to start using it with real patients. The sensor worked fine, but the XCP holder was lousy. The horizontal basket slides on OK, but the vertical basket simply puts too much stress on the sensor. So we can't use if for BWs until we get a better holder. We can us...

Not yet. Sorry.

I'll have to just update the manual. It should just happen automatically with no need to do anything.

Sorry, I'd have to see it to understand it.

I understand that you want to automate it, but I will insist that what you are planning is a bad idea. First of all, the claim totals are not fundamental value fields. They are instead, calculated and derived sums based on the values in the claimproc table. Your queries would have to create new clai...

Yes, I just discovered the same bug today.

Sorry about that. I hate it when it does that. We'll move the bb to our own server in a bit.

Yes. That's not our requirement. That's a DentiCal requirement. You could turn on the image yourself, but DentiCal will deny the claim.

None.

FormRpStatement, line 472.

It's available in everyone's 5.3. You turn it on from Setup, Misc. Yes, it passes the data to X-Charge. But credit card numbers should not technically be stored unencrypted in the database. So if you turn it on, the liability associated with the unencrypted numbers is totally up to you. I would say ...

Which claimform? Is it the medical 1500? That's a known bug that will be fixed within a day or two. As for scheduling the recall, did you set up a schedule for the provider yet?

The new payment report is done for v5.4. It subtotals by type and looks gorgeous. It took about 5 days, which is a huge amount of time for one small feature, so I hope it was worth it. The good news is that it forced us to start using RDL again. The better we get at using RDL, the better will be the...

Yes, you will cause inconsistencies in the database. Please don't even consider it. How would you automate this anyway? Where are you getting this data in electronic form?

I suppose it did. Sorry. I didn't think anyone would miss it. There's only room for so many columns.

It looks really great Frederik. Thanks.

The bug has been found and we're working quickly on a fix.

That column is history. It was just there as a temporary solution to the PPO problem.

I really appreciate it.

Fix posted.

We already have checkboxes for the fee and insurance columns. So you're just talking about being able to turn off the discount column, right? Yes, that seems very reasonable.

The discount column is in the TP module, whereas the Adjustment column is in the Account module. Discounts would only be assignable to status of TP. Adjustments, as always, are only assignable to status of Complete.

Bottom line is that it's cheaper for us to target and support one database. Much cheaper.

Yes, that was it.

Yes. Significant changes were made to the way time is calculated based on the individual provider rather than just the provider for the appointment. But it shouldn't let you save an appointment with zero length. I'm going to search through all sections where appointment.Pattern is set to see if the ...

If you are in another country, they you should be looking in the language translation portion of the program. But if you really are planning on altering the source code, beware that it will tend to lock you into the current version. The only way to update will be to make the same changes again and a...

Thanks for the pictures. I think we're getting closer, but I still can't duplicate it. This is what mine looks like: http://www.open-dent.com/ForumImages/writeoffBalance.gif So now I'm trying to figure out what's different between our two setups. I will be reviewing the code in that area to try to s...

So let me get this straight. Writeoffs are not showing in the Adjustment column of the Account module? I specifically remember adding writeoffs to the adjustment column on individual procedures. Maybe these writeoffs are ones that are not attached to individual procedures. Is that the case? Are the ...

Well, we added support for Oracle last year, and it was painful to say the least. Many inconsistencies between the way the two databases handle things. What we've ended up with is an annoying situation where every query we use must be thought about in terms of Oracle. So we frequently have: if(Oracl...

Doesn't allow the administrator to log in? How on earth do you expect to get anything done that way?

Yes, I've seen the graphical interface block me from performing actions which it decided were dangerous. But var/lib/mysql/opendental (or whatever the path is) has never been a problem for me.

Hmm. And you're logged in as root superuser?

Yes, I'm doing this on Linux. I use SUSE which comes with the KDE graphical interface. Almost as good as MS Windows.

The discount column will be enhanced later to make it useful for all patients, whether or not they have insurance.

Commands? I'm too stupid to type in commands. I just highlight my opendental folder, rightclick, permissions. Then I check the box to apply to all subfolders and click OK. I waste about 20 seconds performing this ritual every day.

Goodness, don't mess around with 5.3.3 when 5.3.7 is available. I don't even want to talk about it unles you are on the most recent version.

I've had trouble with Linux permission from day one. Every time the MySQL database is upgraded to a new version of OD, it reassigns the owner of certain database files to be 'mysql'. Then I have to change the permissions before I can make backups from my personal computer. My point is that even once...

Wow! I hadn't hear about the ADO.NET Entities Framework before. I'm very excited about it. This could really boost speed of development. So yes, I strongly support this change. I have to confess that I will really miss the simplicity of the current 'TableType' classes. I frequently dive into them to...

I keep meaning to start using it, but I worry about how to hang the cord in such a way as to not damage it. So I keep putting it off. Maybe Monday will be the day.

I think the main problem is the known bug when you try to edit the claim proc. That's simple enough and will shortly be fixed. Of course is should not be allowed to alter an existing check amount. So we will test it some more after the main bug is fixed.

I don't think the Renaissance file should be touched. Other than that, it seems like you're on the right track. I'll add it to version 5.4 since it will only take a couple of minutes. Then, once you start using 5.4, you will have it available to put on the form. For clarity, it will be CollegeName r...

You say you "went back to the claim and made the writeoff". Now how did you do that exactly. You have the claim open. Now, did you double click on the that procedure and edit the writeoff inside the claimproc edit window? Or did you again click the button at the upper right for enter payment by proc...

I would suspect the recall logic that you added a few versions back. Let me explain what I think happened. When you added it, you forgot to account for people leaving the varous boxes empty. So it worked for you, but was buggy for many other people. In an attempt to fix their bugs, I wrote some logi...

Open Dental

Search found 5741 matches

Referral button in patient edit window.

Version 5.5

DataObject boilerplate

Encrypt SSN and Credit Card #

Replication

Version 5.4 beta

Mysql.data.dll in repository vs. GAC

Suni Sensor