Windows 10 .Iso

system · October 5, 2015, 11:12am

yehster wrote on Monday, October 05, 2015:

The column in question is created when upgrading from 4.1.2 to 4.2.0 when the proper scripts are run.

openemr/openemr/blob/master/sql/4_1_2-to-4_2_0_upgrade.sql#L2935


#IfNotTable log_comment_encrypt
	CREATE TABLE `log_comment_encrypt` (
	  `id` int(11) NOT NULL AUTO_INCREMENT,
	  `log_id` int(11) NOT NULL,
	  `encrypt` enum('Yes','No') NOT NULL DEFAULT 'No',
	  `checksum` longtext NOT NULL,
	  PRIMARY KEY (`id`)
	) ENGINE=InnoDB;
#EndIf


#IfMissingColumn documents encounter_id
ALTER TABLE `documents` ADD `encounter_id` bigint(20) NOT NULL DEFAULT '0' COMMENT 'Encounter id if tagged';
#EndIf


#IfMissingColumn documents encounter_check
	ALTER TABLE `documents` ADD `encounter_check` TINYINT(1) NOT NULL DEFAULT '0' COMMENT 'If encounter is created while tagging';
#EndIf


#IfNotTable report_itemized
CREATE TABLE `report_itemized` (
`report_id` bigint(20) NOT NULL,

However, since the title of this thread is about Windows 10, the fundamental issue for why the column is missing in this case is not clear.

system · October 5, 2015, 12:23pm

fsgl wrote on Monday, October 05, 2015:

This Ars Technica article is about Microsoft collecting information despite the opt-outs.

It then follows that HIPAA is being violated each time OpenEMR is used in Windows 10; unless all patients agree to release PHI to Microsoft; which is something they would vehemently opposed & which makes the practice look derelict in its duties to patients.

Even if Microsoft would give you a BAA, it would be meaningless because collected personal data will be shared with advertisers. That defeats the purpose of a BAA.

Hopefully you created a system image before the Windows 10 upgrade or at least a good backup for reversion.

system · October 5, 2015, 11:51pm

kornyak wrote on Monday, October 05, 2015:

This error ocurrs in every patient now as a result of the upgrade. What would you propose as the best way to proceed?

system · November 3, 2015, 2:35pm

kornyak wrote on Tuesday, November 03, 2015:

THANKS!! I simply ran the upgrade on the data base and now all is well. Thank you so much!!
FYI All I did was upgrade win 7 to 10, I did not reinstall or modify anything, and other than this odd problem, all seems to work fine!

system · November 14, 2015, 3:37am

aethelwulffe wrote on Saturday, November 14, 2015:

Real easy. Sniff the traffic, block access to the domains that are not directly related to windows updates. Live tile settings to no updates etc… notwithstanding, just block it at the firewall, then there is no question.
No bing, no nothing.
Now using Win10 Enterprise (picked up three licenses through the Techsoup.org program). No unknown traffic as far as I can see. A big part of that is the circumventing of the whole windows start menu by using classicshell.net to replace that goofy thing. No indexing, no searching. For all other bits, you can tweak your registry quite nicely. Takes no more time to secure than any other OS, and they all have issues like this…and it is nothing compared to an Airbook Pro