Open Dental Forum

Bug reporting is currently done by phone. Most bugs are too complex to describe in an email or a post. It's been a few weeks since your post here, and I see that this bug was fixed 3 days ago. Thanks.

Hmm. All those pages look fine to me. So I took one example:
https://opendental.com/site/images/periochart.png
When I put that into a browser, I get the correct image. You don't?
I suspect your post might be outdated. Maybe it was a temporary issue that has resolved.

It's one reason why we've been trying to deprecate plug-ins. They are not a good idea for stability of the program or of the database.

We added more features to it in 25.1 to make filling out multiple forms in a single family more efficient. 25.2 is getting even more enhancements in that area. At the same time, we've been working through the system to get the app approved in the two different app stores. I think that might be done....

Yeah, pretty sure it's spam. Removing links until I can be sure.

Yes, it did. You have to retrain to use the red X at the upper right. It was silly to have two buttons that do the same thing. And modern apps tend to not have cancel buttons. I thought about it for a long time before I did it. You'll get used to it very quickly and then it won't be annoying.

Only one patient at a time. But yes, you can open multiple instances. That is quite common if you want to look at two patients simultaneously.

Technically, yes, as long as you don't connect to the same database. But it's probably too easy to make a mistake. Maybe try it on your home computer instead so that it's truly separate?

1. The columns are called operatories. https://opendental.com/manual/operatories.html. Add providers to operatories.
2. Add the hygienist to that operatory.

I'm pretty sure the above is spam and should be ignored. I removed the link in the signature. I'd better not see another spammy post from this user.

I suspect that post two rows up is spam. It had a link which I deleted. They restarted a conversation that's 7 years old and they sound like ChatGPT to me. I'm sooo close to just deleting it.

They are already in Version 24.4 beta. So you can set up your eForms and see how they work. You can fill them out in Open Dental proper on a full workstation. But to actually use them as intended, we need one or both of the following: 1. eClipboard beta needs to be released. It supports the new eFor...

This new feature has been added: Chart Letters Basically, you start out by merging a Word document through our normal button at the top. But you use the new Chart Letter button in that window. The Word document then shows up as a row in the Chart Progress Notes. From there, when it's edited we alway...

Looks like the in-office version will be coming out first, and the web version will follow months later. The in-office version means eClipboard rewritten in a newer programming language. You hand the patient a tablet and they fill out the forms in the office. The ability to use those same eForms for...

I think there are some workarounds for Dentimax. Specifically, every time you close Open Dental, also go to the Windows Task Manager and close the instance of Open Dental that seems to be running in the background waiting for the Dentimax driver. https://www.opendental.com/site/sensorcompatibility.h...

Our filter needs to be better. It should use regular expressions to ignore those keywords if present inside of quotes.

We consider RxNorms to be part of the EHR features that were added solely to allow offices to get their government incentive. We didn't think anyone was actually using those features. We have not been updating EHR features because nobody's using them. I'm curious what you use RxNorms for.

Hmm. This wouldn't need a feature request. It would be considered a bug. So this has nothing to do with sensors. You're saying it's for any image. So it should be reproducible. I will try to duplicate. I have not seen that. What's the resolution of your monitor? What's your Windows scaling? That's t...

That's the idea. We want them to do everything that mobile sheets can do, including that. We'll see if that particular feature makes it into the very first version or not. Most of our engineering effort over the last week seems to have been going into powerful layout options like handling percentage...

Regarding fonts, all label type fields support rich text, including text color, background color, font size, bold, underline, paragraph left margin, paragraph alignment, and paragraph hanging indent. We don't actually have an option for different font families like Arial vs Times yet. I'll think abo...

We also added fixed vs. percentage field widths, optional 3D border boxes around each field, and a bunch of other fluff that I wanted to put into a later version. But the early testers complained way too much about some of these lacking features, so we added them. Since they are still working on the...

Yes, we have added age-based conditions. It is fully functional. Still not released yet because we're building the server side that patients will actually navigate to in order to fill out the forms.

Yes, it has conditional logic support, but that feature is not quite as powerful as Flex yet. The parent conditions can be any radio button or check box. That's all built and working well. It's fantastic. But the parent condition cannot yet be an age derived from a birthdate. I will consider where t...

To prevent staff from using this old code, set its fee to $0 and also start using various entry methods that do not require typing codes. There are many better ways than typing a code. In the Appointment Edit window, you can click on the list of available procedures. In the Chart module, you have pr...

That's a few years old. We don't fix bugs on versions that old. We always recommend upgrading to the latest stable before we research any bugs. So you should update to 23.3, and it might just solve your problem.

We are aggressively building eForms. This brand new framework will completely replace mobile sheets and webforms. It will be used for patient forms, insurance info, medical history, and consent forms. Normal sheets could still be used, and it will not otherwise replace sheets in general because shee...

The way eClipboard should behave is that if it loses connection, it should not crash. Patient should instead see a progress bar of some sort while eClipboard attempts to reconnect, even if that takes 5 min and requires going into tablet settings or whatever. Under no circumstances should a loss of c...

That's a bug. All flipping, rotating, and cropping should be applied to any outgoing image. I'm reporting it to our bug list.

What specific version are you using?

It looks like that field is not currently an option. But it would be very fast to add, and since it's required and I don't see any possible workaround, we will add it immediately. It will be in version 24.1, hopefully within the next few days.

Conversion of the actual Imaging module window is underway in stages. Many controls have been converted, including the image selector at the left, the windowing slider, and the zoom slider. The toolbars have been overhauled again, with more icons. Nobody should be able to see any difference at all w...

What version did you move from? I think it's been that way for a very long time. That's a Windows 11 feature called Snap Layouts. Open Dental uses custom title bars, so it doesn't have support for Snap Layouts. We made our own similar feature from scratch for use in the Imaging module to allow you t...

I can't believe it's been a month since my last post. The thing I'm most excited about is that I came up with yet another trick to remove the need to convert windows to WPF if they are too hard right now. I'm using a global static event that FormOpenDental subscribes to. Any WPF window can call a me...

I looked into it. The ToolBarOD is pretty solid. I verified that it only repainted when it needed to, like if the mouse is moved to a new hover button. It doesn't repaint if you just move the mouse around on the same button. So that was my main concern. The timer seems harmless, since it's a pretty ...

Finished up a lot of details on the ImageSelector. The new one completely replaces the old one already, and I can't tell any difference at all. It admittedly took quite a bit longer than I planned. In the process, I perfected a technique for setting the scale and zoom of these nested WPF controls. T...

I would expect it to draw better in DirectX than in OpenGL. We switched away from OpenGL about 10 years ago after a good solid attempt. Since we're using MS, DirectX is just a better fit. Thank you so much for tracking down that CPU usage in the ToolBar. I have a little down time at the moment, and ...

We've been working hard on conversion of the Imaging module. I've personally been working on the ImageSelector at the left. It's just about done. This has required a lot of work on peripheral issues like the ToolTip, vector drawing with SVG-style commands, and some threading to load thumbnails quick...

As we move to WPF, issues like the fonts should get better. We've already been able to reduce the number of calls to the Windows API, and I can see us being able to get rid of those completely some day. We're still on 32 bit because of all the bridges we have with other software. We'll have to build...

CustomGPT worked. But by worked, I mean it's about 80% accurate. It can spit out great responses that are relevant to OpenDental. The responses are not word-for-word from our manual, but are reorganized and summarized as only ChatGPT can so elegantly do. The main problem is the 20% that's wrong. You...

Looks like we might release 23.3 as beta within a week. 23.2 would then become stable.

The steel framework is going up for Bldg H. Always exciting to watch the welders. I've asked ChatGPT questions about how to use Open Dental, and the answers are garbage. I'm going to try CustomGPT, but my expectations are low. We all know what we want, but I just think nobody has been able to build ...

I've been very productive. Spent a lot of time working with other engineers on interesting and complex jobs. A few examples: -Perio chart refactoring is going nicely. The code is gradually getting more sane and less spaghetti. This is critical before any actual improvements can be made. -FAQ at the ...

Making some pretty fast progress in lots of little details: -added WebBrowser control -added SplitContainer control -added properties to all windows for ShowMinMax, StartMaximized, HideHelpButton, etc. -finished up translation framework -improved the help button -fixed window icons -context menu sho...

I've been working on more WPF details, including: -added TreeView control with images -added checkboxes to listBox for some situations. -implemented Autonote composition in WPF, including the automatic yellow text selection. -getting closer to finishing up our richText box. This is already starting ...

I've been working on lots of little things: -Rich text box. Ours is very customized, with a number of dependent popup windows for things like autoNotes and quickPasteNotes. So there are lots of moving parts. It's maybe 50% done. -Filter controls. This is chunk of code that someone wrote about 10 yea...

I think a lot about what Open Dental might look like in 20 years. I'm pretty certain that users will have the ability to interact with it in ordinary spoken language. This would mostly be useful for new users who don't know where things are or why things look the way they do. Once you understand eve...

I can't tell if you're using the API or not for this other window.

I think my posts will tend to get a bit more technical from here on out, since that's what consumes most of my time and attention. I've been working on a variety of properties for WPF, like IsEnabled and ReadOnly. I also added a PictureBox control. There are an awful lot of little details that need ...

I switched to a standing desk. Sitting is an independent risk factor for diabetes, probably because constant muscle work is needed to process sugar. The brand we use is from Autonomous.ai. I'm not the first at the company. We already have hundreds of them. I thought I would get tired, but not as muc...

This is a duplicate post. I answered the other one.

I thought it was recalculated when a claim was created and pretty much everywhere that it might change. We also need it to be accurate in order to display it, so I'm leaning toward thinking you can always trust it.

I'm on vacation now. That's very exciting because I can get lots of work done on the plane, in the evenings, etc. I'll build and enhance a number of WPF controls so that we can convert some more complex windows in a few weeks. A really complicated one will be the perio chart. It's very old. There ar...

I think maybe I'll try blogging here for a while just to give people an idea of what I'm personally doing. Maybe about once a week. This week, I finished the conversion tool for switching from WinForms to WPF. We have about 1000 windows to convert, so we're starting with the simple small windows. Th...

That's a reasonable idea, but it's fighting with all the other requests for prominence. There are some fairly simple workarounds, so it's just not going to be very high priority. One example of a workaround. After extracting the residual root, mark that tooth missing so that you can put a pontic the...

The perio chart was designed under the assumption that you would have an assistant doing the data entry. That assistant can keep up by using the keyboard and mouse. If you don't have an assistant, then entry was optimized to use touch screen. Mouse and keyboard by the person doing the exam is the la...

The description for how to add that file is on the Zoom page in the manual. This page:
https://www.opendental.com/manual/zoom.html

One more thing I should point out is that we spend a huge amount of time rebuilding the same functionality that we already have, except with more modern tools. If we don't do this, then the software becomes more fragile over time. When the Southwest Airlines software choked a few months ago, it was ...

Hi, Steve. I looked up your account out of curiosity. Looks like you were approximately customer number 30 about 19 years ago. What were you thinking? Who buys software that only has a handful of customers? Anyway, you got lucky, and we're still forging ahead.

I have not yet noticed that, but it sounds like a legitimate bug.

We continue to deprecate plug-ins. A program link button sounds like a perfect fit.

Just start fresh and keep them as two separate databases. We don't charge per database. We charge per active office/provider combo.

1. Never thought about it. I'll add it to the planned features. Yes, it does sound like a good idea. 2. I would think of historical radiographs as nice to have, but I wouldn't count on much. If you don't get your hopes up, you won't be disappointed. I really don't know the answers. The conversions t...

I think the original developer of Apteryx had a lot of special inside knowledge. Native sensor support is very hard. Kudos to them for a great product. I always thought the independent imaging software companies would be around forever, so we didn't really do any imaging development for the first 15...

They are all just recommendations. There's a lot of flexibility and each insurance company also handles them differently. For 'D0140', 'D0145', 'D0150', 'D0160', 'D0170', 'D0310', and 'D0320' ADA - Does not recommend putting anything Open dental - Treatment area to Mouth Well, "nothing" is really sy...

Having robots do the drilling on patients was definitely not tongue in cheek. I expect that to happen in approximately 80 years, which is only 40 years after I'm dead. To make it feel more plausible, start imagining all the steps that it would take to get from here to there. The roughly half-way poi...

Your device type was Twain Multi?
https://www.opendental.com/manual/imagingdevices.html
And you were using a fairly new version?

I've added the Insurance ID field to
https://www.opendental.com/site/imaging ... ments.html

We are nowhere close to being done with Open Dental. We've barely scratched the surface of what's possible. I'm personally getting to the end of a months long effort to make it work better on very high dpi screens. It's so much nicer at 4k. Some other things that excite me in the short term: -It loo...

The Dexis website for GxTWAIN https://dexis.com/en-us/gxtwain-and-gxpicture says that multiple images are tranferred with the the Get All function. We support multiple image transfer, so it should already work fine. You mentioned not having a "bucket". I think what you are looking for is the Mount f...

> We are still waiting for a couple imaging features to be incorporated
What features do you feel are missing? There's not any active development in the Imaging module at the moment.

In a referral letter sheet, you can indeed add a field for notes that can be edited from patient to patient. It wouldn't be much use otherwise. But there is one gotcha to beware of. If your letter contains a toothchart or a grid, then it gets saved as an uneditable pdf. You can still edit when it fi...

From all the options you listed, it kind of sounds like enhancing sFTP is the way to go. I wasn't aware that people were running into limitations with that.

There's an undocumented pref called FuchsOptionsOn, which I believe you added a very long time ago. You are the only user who has that pref turned on. We've been gradually stripping those out as we run across them (sorry). So there is also a slight chance that there is some mixed behavior going on. ...

You can run queries to get data like that out of the database, but you should never run queries that alter the database. In theory, your approach might work. I'm 75% sure it would work, but I just can't be certain. If you corrupt your database, fixing it could be a big hassle. I think someone can fi...

Maybe when someone dies, you change the status in Open Dental. Then, if they're a non-patient, they shouldn't come through in the first place. In other words, do the same thing with a different approach. Yes, it will require staff to change the statuses, but it should be easy to run a report to see ...

0. Are you sure you have your Imaging Device set up for TWAIN Multi? It sounds like you still have it set up for single images. https://www.opendental.com/manual223/imagingdevices.html 1. That's new functionality that wasn't even a feature prior to 22.2. It's possible that we only tested it for acqu...

Yes, that is one of many goals. Even once we achieve it, it will still get better over many years. It's one of those features that will gradually mature because it's just so open ended. It's going to require some AI to be able to understand what it's seeing. Unlike automobile AI, this does not have ...

I've just started on the next iteration of the 3D graphics. I think this is the sixth time I've overhauled the tooth chart. One of the earliest versions, 20 years ago, was a simple jpg that I drew shapes on. Some of the overhauls have been required by updates to graphics cards over the years, and so...

Including it in the date field seems like a breaking change. On the other hand, everyone is probably parsing the date with a library that could easily handle the change. Still, I think we'll need to make it an option that you intentionally turn on.

This topic is 10 years old. A lot has changed. I can think of two different ways to do it, and there are probably more. 1. Use our automatic import feature. https://www.opendental.com/manual/images.html About one page down is a section called Import Automatically. You could set the default path to y...

I think it was more important to first add the security. Adding additional ways to delete would be additional features and take additional programming time. So it's just that we don't have unlimited resources. Yes, it sounds like a helpful feature. That's why we have thousands of feature requests. M...

Yeah, I'll take one sample of each format. jordan{at}opendental{dot}com

I just added this to our schema under definition.DefCat enum: Each appointment can be assigned one appointment.AppointmentTypeNum. Multiple AppointmentTypes are linked to this definition through the DefLink table, where deflink.DefNum=definition.DefNum, deflink.LinkType=2, and deflink.FKey=appointme...

And now you can show mounts on sheets. A typical example would be showing an FMX or photo collage on a referral letter.

OK, you can now double click on an image and you get a new window that lets you pick any other image for that patient. It's still a little rough around the edges. For example, it will take a few more hours to implement this for mounts. But it is at least working. It will be in version 22.2, which sh...

I reviewed our current functionality. It's easy to keep track of referral sources and how they are attached to patients. It's easy to create a letter to a specific referral. This part of our software is called "sheets". Once the letter is generated and on the screen, I can edit the text of the lette...

Or we could get our act together and improve the referral letters. I thought we already had images on referral letters, but maybe it's time to go back and take another look.

I've tested the ScanX with switching Windows users. I also had an issue, but not the one you described. My issue was that the scanner was not recognized as present, and I had to power cycle it. Then, it worked. I could not get it to lock up for me. I would suggest that you set up a Windows user for ...

Would anyone be able to send us a few 3D scans from an intraoral scanner so that we could work on showing them inside of Open Dental? Could be any format, like Medit .obj file or 3Shape .dcm file. And, of course, we'll need an .stl file, too. If it's an .obj file, I'm assuming the textures (photos) ...

I'm trying to find time to test the Scan-X issue.

Ortho brackets are successfully drawing, so they will be part of version 22.2.

Your endpoint looks wrong. Instead of this:
GET https://api.opendental.com/fhir/patientNotes/13
it should be like this:
GET https://api.opendental.com/api/v1/patientNotes/13

I got the following as a private msg. Posting it here for everyone: Here is the n8n / Javascript to perform a google calendar update w/o webhooks. I would like to reuse this code for schedules which requires the GET schedules/xxx for deletion. Google calendar will then update calendly. Code below. J...

Done for version 22.2

It wasn't planned to have separate control of thumbnails for chart vs imaging, but it's a good idea, so it might even get done today. It is not planned to split radiographs into their own module. But we might add better toggles at the top of the list for showing radiographs vs front office documents...

32 bit is not helpful. My vote is for RGB. Example "200,100,52". We could later add hex if some people prefer it, but the conversion between the two is really easy.

Ah, thanks for researching that. I suspect that your background finally got taller than 4000, and that's why you noticed it. We chose what we thought was a ridiculously tall number that nobody would ever hit. Each page is 1100 tall, so that's almost 4 pages. There might not be a problem with us allo...

Someone at Open Dental should research this to find out when it was changed and why. Then, we will know what to do.

It sounds like you first need a query to know which document. Then, you could use POST DownloadSftp to get that image. SELECT DefNum FROM definition WHERE Category=18 AND ItemValue LIKE '%P%'; If you get a valid DefNum (190 in this example), then use: SELECT DocNum FROM document WHERE DocCategory=19...

Plugins are being deprecated for users in the US, so this would only work outside the US.

4000 would be 40", but paper is only 11" tall. Does it spill across multiple pages?

We settled on this about 15 years ago. It allowed different ranges of PKs for different offices all using the same database with replication, so that there was virtually no chance of collision. Also, many tables such as logs can fill up rather quickly. It's something that must be intentionally turne...

We just release chart module data, and we could make a method for TP data, if that's what you are asking for. Maybe start a new thread instead of reusing the very old and unrelated thread.

But it's always possible for patient databases to have extremely large primary keys. You need to be able to handle them, even if they are large. In C#, the type is long, and in mysql, the same type is called bigint. It can have a max of 9,223,372,036,854,775,807.

Ah, thank you for the complete explanation. This might be enough for us to be able to duplicate the problem here.

So when you were doing testing with HL7, I'm unclear if you were connecting directly to the db. If so, then you were probably the one who created all the extra connections. Instead, try to reuse the same connection.

What version are you on?

I think Get Slots is the best right now until we add the new functionality. You could use a little math to generate appropriate individual slots.

We're reaching out to you by email. We need to know which offices.

We'll stop working on other things and focus on this problem. There should be no active bugs like this, so we'll work on it aggressively.

This is a good point. The thinking was that if you count each possible time as a slot, then you would just get a bunch of slots for the same day, whereas it might be more useful to get one for each day, and then you could pick any time within that range. Unfortunately, you would need to do a little ...

Until we get that done, we would be happy to move one customer at a time for you manually. Contact us by email for that.

Since our permissions are all at the developer level, I think we're going to be stuck with moving a customer key from one developer to another. Permissions at the customer level would be a massive change. It's possible, of course, but just not sure if it makes the most sense. I think I would rather ...

Let me clarify. Do you currently have two separate developer keys? It sounds like this would be the first step, so that each "developer" had different permissions. Then, we need to add a tool to the developer portal to let you move a customer key from one of your developers to the other. Does that s...

Hmm, I don't quite understand. I don't know how much you know about our schema, so I'll start at a very high level, and then you can reply to help me narrow in on what you are asking. Our schema is here: https://www.opendental.com/OpenDentalDocumentation21-4.xml The following tables might be related...

I'm assuming this is in the Edit Benefits window:
https://www.opendental.com/manual/benefitinfo.html

The database integrity warnings would be totally unrelated to the issue of this thread, which is restoring a backup. You should never get a false positive on those integrity warnings. What specific version of OpenDental are you using?

Yes, we will do this. It would be GET schedules.

I did get the first UI event to fire. This event fires every time you change patients, and it tells you who the new patient is.

Events are functional and will be in version 22.1. So you subscribe to an event https://www.opendental.com/site/apisubscriptions.html and now it fires off to your chosen end point. It's pretty cool. The next step, which I hope to have done before the end of the weekend, is UI events. Push a button o...

My thought is that maybe our dataintegritycheck needs to be adapted to maria? I'm skeptical that the suggestions to uninstall and reinstall things would do much. I'm so happy that you are regularly trying to restore your database. You won't go bankrupt when your server crashes. It really should be e...

Yes, we'll add it.

Thank you. Got it. We will look into it.

That's correct. Usually, when an IT person hears "open a port", then assume we mean changing a rule on the router to allow incoming traffic from the dangerous web. That's not what we're talking about.

Maybe right click on the Solution in the Solution Explorer tab and click Restore NuGet Packages?

It's always a bear to learn all the nuances. It can take some work with the configuration manager and with removing and adding references. We give some guidance here: https://www.opendental.com/site/sourcecode.html Also, if you're using it for testing purposes, you can just install the trial version...

Various versions of VS2019. It doesn't seem to matter. Some engineers keep it up to date and others don't. I have 3 computers, but at the computer I'm currently sitting at, it seems to be version 16.11.5. It's probably different on my others.

Local API is complete. It will be part of version 22.1. This lets you send API messages directly to the local running instance of OpenDental.exe on port 30222. Because it's local instead of going through our HQ servers, it's blazing fast. We do quickly plan to add the eConnector port 30223 as a thir...

I'm not sure. We use VS2019. It might work.

How many offices are we talking about? That's a lot of work for just one office.

You developed a plug-in in-house for your own use and you are not distributing it to others? And you are inserting PayPlanCharges? That's interesting. I can't quite figure out why you are doing that, but I can still talk about it. We would encourage you to use the API. This would be especially impor...

I still don't understand. A windows filename cannot be "cleared". Every file has to have a name. Maybe you mean the document.Description gets cleared. We'll try to duplicate.

The part of our website that you quoted is not about plugins. There are two different ways that 3rd parties can currently make changes to our db: 1. Plugins, the topic of this thread. 2. Queries, which is what you quoted from our website. Yes, they are related, and the warning timeline might be simi...

Uncropping and recropping should always fix it. If not, that seems like a completely unrelated bug. I'll set someone on trying to duplicate that issue.

Our current plan is to not deprecate plug-ins for international customers so that the Mopensoft plugin and other similar plugins will continue to work. Our eServices are tailored to the US, and each country is different.

What do you mean by "it changes his name"? File name? Patient name? Description?

The retake button is only present in the middle of a sequence. If you are retaking after completing the sequence, then you would manually unmount the one you were interested in, then recapture. At least for now. I'll begin considering the workflow for a retake after finishing a series.

No, there will absolutely be no interruption of any plugin with version 21.4. All plugins are whitelisted. In fact, we also made the decision to let international users continue to use plugins moving forward, regardless of our decision to phase them out in the US. International customers don't have ...

I'm very sorry about that. We released a "fix" a week ago, but then realized that the fix was also buggy. We are releasing the real fix in the next few minutes, version 21.4.20. You will want to update to that immediately. Any images that you viewed while using 21.4.17, and which looked bad can no l...

I thought we added a retake button to 21.4, but it is admittedly mediocre. It got reworked slightly in version 22.1. I can't figure out how to make it completely "automatic". I mean you have to tell the software somehow that this is a retake and not the next one in the series. We got it down to 2 cl...

We are making good progress on Events. One fundamental problem that I still can't quite figure out is that databases don't inherently generate events that are consumable externally. That means we will still need to poll the db at a certain interval in order to generate database events. But I think w...

We should improve this message to indicate that it's likely a version issue. We might even be able to get fancy about it and check the required version for each API method.

Our current API has no events. It has come to my attention that various 3rd parties depend heavily on events for their functionality. So far, I'm aware of two strategies: 1. MySQL triggers added to the db. When a trigger fires, this runs a query or multiple queries. 2. Plug-in that responds to certa...

>In addition, OD is planning on charging the developer and the dental office for reading and writing this data.
Not quite. No charge to anyone for reading. If writing, there will be a very small charge to the developer, not to the dental office.

We are constantly making improvements to this area. I expect the false positives to go away within a week or two in the beta. You would need to update the beta to see the changes.

It's giving them to you in batches of 100 at a time, right? Because there's a hard limit of 100. So are you saying it's 1 minute for each request?

We were going to build a separate Imaging module that we would charge separately for. Then Apteryx took a nose dive and Covid hit. I decided that dentists couldn't really afford to pay separately for this, so we just rolled it all into the main program. As part of that compromise, I decided that the...

It's a gradual process that requires constant feedback and adjustment. So it really is impossible to say. The current plan is to start with subtle warnings that don't actually interfere with functionality. The other part of this is that we don't want people to be afraid to update versions of Open De...

I don't think there should be an API method that a 3rd party could call that would cause Open Dental to send an SMS. On the other hand, the API could be used by a 3rd party to get information like cell number, and then to also make an entry into the Db that the text was sent. The 3rd party would do ...

Just PatNum. No GUIDs.

The issue with cropping is a bug that I thought would be fixed by now. We should be very close. We never alter the raw image. All brightness, contrast, text, cropping, etc is always just applied as a filter when viewing. This means it's always 100% reversible. Fortunately, we are able to apply these...

Another user had requested 10 items just before you, so we're still plowing through those. I moved #7 to the top of your group and we'll try to get to it right away.

https://github.com/OpenDental

We're going to start working on a LAN-API. This would avoid the round trip of the API call to our HQ, and your app would instead talk to the eConnector that's already running on the dental office server. This would be faster, and it would also remain running if the internet went down. The message fo...

We switched to GIT! The new GIT repository is not public, so our plan is to push copies to a public GIT repository on github. We have not started doing that because nobody was clamoring for it.

We will write the APIs that you need. I don't think Flex has asked for any yet, but we've been adding new methods quickly as requests come in.

Probably don't. We're deprecating plugins. They are far too dangerous and are causing database corruption. I'm not saying that this plugin is causing database corruption, but I'm explaining why we are deprecating plugins in general. What can Mopensoft do? The plugin should instead be an exe. The but...

>So the concept of using Apteryx within OD has been working wonderfully...
I think you meant to say Scan-X, not Apteryx, right?
What specific version are you using?

Would BaseEst be close enough? It does already have percentages applied. Notice that in the description of AllowedOverride, ComputeBaseEst is the function where the allowed fee is calculated. BaseEst is very close to allowed fee.

Notice in line 482 that this method does an insert to the db. That's not allowed. You cannot ever call a method in Open Dental which alters the database (which means most methods). I'm unclear how you are "referencing" Open Dental, but we have been working hard lately to block all such action. Even ...

Your first issue is a bug that we are now working on.

Those are both great suggestions and have been added to the top of the priority list in:
https://www.opendental.com/site/imaging ... ments.html

5. I did think of a way, but it won't be easy. We've been toying with the idea of a "local API" for certain things. Instead of sending an API command to our server, you would send it directly to the local running copy of OD by using local port. OD would act as a web server and respond to your API re...

We've added all of this to our todo list, and it should be done relatively shortly.

5. There has to be some way to identify which dental office you are interacting with. The way we came up with is that you create your customer key, and then you paste that into the UI on the customer's end. I can't think of any way to reduce the number of steps, which is what you seem to be trying t...

The idea is to not "change" anything, but instead to add to it. We indicate the version that each method was added.

Your database is on your server, not on your workstation. When you open Open Dental, you always connect to that database. So you must have simply connected to the wrong database, probably another one on your server. Go to a workstation that's working, and see which database you are connected to. Tha...

>Also, as a side question, what would be your recommendation to discover new/changed appointments via read API in an efficient way?
Appointments GET (multiple). Specify a DateTStamp with your call so that you are only getting the new/changed ones.

We provide a conversion service. It involves an export from Apteryx followed by in import into Open Dental.

My understanding is that digital panos are easy. That's just a single image.

#2: There are certain fields that it would not make sense to be able to edit. For example, patplan.PatNum and patplan.InsSubNum. Instead of changing these two fields, you would either POST PatPlans or DELETE PatPlans. The rest of the fields make sense. #3: Similar issue as above with claim.PlanNum, ...

This area is developing so quickly that the feature request system is really too slow to keep track of it. I'm tracking it all here: https://www.opendental.com/site/imagingimprovements.html I just haven't had a chance to work in your new suggestions, but they are great. So if the rapid progress slow...

Thank you so much for all the great feedback. We will work hard to make this smoother. Most of the complaints will need to be added as new features, but one of them is already done: Exporting single images from a mount is better in 21.4. 21.4 also has a lot of other improvements that are unrelated t...

You should use our API. Direct inserts to the database are not allowed. If you are using a built-in method, then I'm guessing you're using a plug-in. Plug-ins will fail to load in version 21.4 unless they are white listed, and staying white listed will become harder over time. We would probably not ...

We usually backport to the stable version. I think the new codes are inserted during the version update. So, we'll at least backport to 21.3. If we don't backport to 21.1, you can add any important code manually.

Our autocodes do not support one of the conditions resulting in no code. Each condition has to have a code. So your scenario is just a little too complicated for the autocode logic at this point. But as I went through the clicks, you're really only looking at 2 additional clicks.

#3 doesn't belong in the autocode. An autocode is for a set of mutually exclusive criteria. A tooth can be a pontic OR a retainer, and there's one autocode to make that decision. It looks like BU would need to be entered as a separate step. I think what's going on here, and why I didn't catch on soo...

preference
PrefName=SecurityLockDate

We tested on a PD740, which looks pretty much the same as your MD740 and is probably the same hardware inside. Our camera came with driver software that will generate a keyboard button press when the Capture button is pressed. There's a link to the software in our manual. https://www.opendental.com/...

Do you mean the live video is laggy or that the single image capture is laggy?

Your autocodes really should already be set up. You can reset them to defaults using Procedure Code Tools. The main reason we allow editing of autocodes is for foreign users who use different coding systems. Keeping that in mind, there's one autocode for pontic vs. retainer. It would have nothing to...

There should already be a button for bridge. The basic idea is that you set up the button to have the AutoCode for bridge. That assumes that the autocode is set up properly. So then, you go check out the autocode that you used. It should have two procedures in it: one for pontic and another for reta...

Support has been added for the ScanX. It will be a few days until these changes make their way into version 21.3, and they can't be backported further than that.

Probably done by the end of today, and then we release about twice a week. It will be backported to 21.3.

ScanX machine has arrived, so we've begun troubleshooting.

Let's talk for a moment about how whitelisting works when using Windows Security Policy instead of ThreatLocker. In Windows, you can specify a path, a certificate, or a hash. Both path and certificate would allow Open Dental to run, and only the hash would block our updates. I tried to look for some...

Sorry about the hassle.

Someone successfully used ScanX by using their VistaEasy software. http://opendentalsoft.com/forum/viewtopic.php?t=5903 I downloaded VistaEasy and can't get it to work, but that's probably because I don't have a ScanX device connected. I ordered a ScanX on eBay, but that will take a little while to ...

Our assumption with the ScanX was that it could dump all your images to a folder instead of using Twain. That's why we built the "Import Automatically" feature. Does ScanX not let you do that? If it's using Twain, then it's going to want to send a series of image, which Open Dental can't handle. We ...

https://www.opendental.com/manual/defin ... olors.html
I would recommend nice dark colors for both planned and completed because text looks better when dark. But you can choose your colors.

So I think that's all of them.

We're still trying to find a place in the db to put this info. I think it will probably need a new table. We'll talk about it again tomorrow to try to finalize.

We talked about it. The key is available in our UI, but not in our database. To show in our UI, it makes a call to our HQ server. For now, you would need to store your own config information using any normal method that you wish, including registry, ini file, xml file, database, web method, etc. We ...

In Open Dental, we never alter the original image. We apply crop, rotation, contrast, etc. as a programmatic "filter". So the original images will not be changed. With this version, a conversion needs to be applied to the database in order for the old filter strategy to be converted to the new more-...

It's some matrices, some geometry, and lots of head scratching. We used to crop, then rotate/flip. Now, we have to rotate/flip before we crop. So that gives a totally different result. That's fine, but what do we do about all the existing crop-rotates? They must all be converted. We need eight conve...

We have started implementing our Database Integrity features:
https://www.opendental.com/site/integrity.html
There will be a few irritated users, but we have to rip that Band-Aid off. We have too much database corruption.

Plug-ins must now be whitelisted in order to work.
https://www.opendental.com/site/pluginwhitelisting.html

https://www.opendental.com/site/imaging ... ments.html
Rotations are being enhanced. Lots of crazy math...

I think that sounds about right. But I never really thought about different clients. The way I envisioned this being used was from a database driven server at the HQ of the third party using the API. It sounds like you will be calling the API from software running directly on the customer machine. D...

From https://www.opendental.com/manual/senso ... ility.html
Make sure you have the box checked to show Twain UI. And RESTART Open Dental after you check it. It's designed to only need to click Capture once.

The unmounted feature is complete.

Search found 5768 matches