Thanks for the kind words, but I will have to give James all the credit for running the queries. In his business, he can do that with his eyes shut.
Some basic info. A long time ago one could use Sql Server Management Studio (the program which allows you to manage the SQL database) had a system admin and password that many people knew. Now when AC installs SQL the sa username is different for every user, so it is nearly impossible to use SSMS (***********************************). If AC installs the entire v11 with SQL 2016, the only login will be with sa and password. (*******************************)
Using SSMS (v18)
https://support.microsoft.com/en-us...8-8-093287d3-7aa8-f13d-22af-eda7aea16665 you can read and write to SQL, therefore to AC. So, it sets up an ethical situation. "Patient comes in with a 104 febrile...." and ends up with meningits, that note could be changed to "Patient comes in afebrile,...." now changes are logged and Indy and I disagreed on whether the logging could be turned off. (James can break the tie). I always look at EMRs and compare them to paper as the standard. So, if you had 104 written in the note, you would have to strike it out with a line and initial it. It would be hard to change. So that leads to do you have a right to your data or just read and not write. Of course, you could in parentheses write {edit pt not 104 was afebrile date and time and initial or sign]
______________
The person I use (before I knew James) works on all versions of SQL. His only job is to work with companies (say Quick Books) where they may be using it in a company or companies with hundreds of users. A user would select something which would ask for information with a query and the time would be recorded. So, say it took 3 seconds. The SQL Server tech would then monitor the query for time. If the query took longer than 3 seconds, then the bottleneck was with SQL and that could be looked at, i.e. how the query used the tables, etc. If the query took 2 microseconds, then the bottleneck was with Quick Books.
So, when we ran a query to pull medications over and it took 5 seconds but SQL took 15 ms, then we need it was with the program. That doesn't mean the program is written wrong, just the path it has to navigate the data.
