Ignacio Valdes Implementation Log/Episode8 - Revision history

DavidWhitten: DavidWhitten moved page Episode8 to Ignacio Valdes Implementation Log/Episode8

2020-11-13T03:57:10Z

DavidWhitten moved page Episode8 to Ignacio Valdes Implementation Log/Episode8

← Older revision	Revision as of 03:57, 13 November 2020
(No difference)

NeilArmstrong: Added a glossary link to Debate~

2013-02-22T16:15:31Z

Added a glossary link to Debate~

← Older revision		Revision as of 16:15, 22 February 2013
Line 602:		Line 602:
	performance implications would be.		performance implications would be.

	Basically, you're running into the legacy code problem. Modern MUMPS implementations do support ACID transactions, but this facility was not available when the bulk of VistA was developed. This has led to a controversy between people arguing that it is not feasible to build transaction support into VistA, and people (like me) that argue that it is essential to do so. Unfortunately, this generally mutates into a highly emotional debate over the use of MUMPS, which is not the point at all.		Basically, you're running into the legacy code problem. Modern MUMPS implementations do support ACID transactions, but this facility was not available when the bulk of VistA was developed. This has led to a controversy between people arguing that it is not feasible to build transaction support into VistA, and people (like me) that argue that it is essential to do so. Unfortunately, this generally mutates into a highly emotional [[debate~\|Debate]] over the use of MUMPS, which is not the point at all.

NeilArmstrong: Added glossary link to Configuration~

2012-11-01T20:06:19Z

Added glossary link to Configuration~

← Older revision		Revision as of 20:06, 1 November 2012
Line 678:		Line 678:
	Skip Ormsby Date: Fri, 22 Aug 2008 20:15:58 -0400		Skip Ormsby Date: Fri, 22 Aug 2008 20:15:58 -0400

	As long as the subject is about power outages, at the hospital I was at we had no break power for 8 PDP 11-44s that would run the critters for 15-20 minutes, which was long enough for either the main generator to kick in or for one of us to gracefully shut the systems down. When we went to the MSM/486 configuration, we made sure that all of the parallel bars were zipped tied and the plugs were zipped tied so the didn't accidentally come out of the plug. And of course the no break power would last a very long time, but we never pushed it past 1/2 hour. The biggest problem was more in line with a disk controller going nuts, or a nic card that would go berzerk, or bad memory, which in turn would put curd into the data base. For us it was a case of fix and forget it, because there were other fish to fry. Never did have a real power outage to the computer circuit, even when the room was flooded from a broken pipe in the ceiling. Lost the lights, etc., but computer kept right on humming until we shut them down in a speedy, graceful shutdown.		As long as the subject is about power outages, at the hospital I was at we had no break power for 8 PDP 11-44s that would run the critters for 15-20 minutes, which was long enough for either the main generator to kick in or for one of us to gracefully shut the systems down. When we went to the MSM/486 [[configuration~\|Configuration]], we made sure that all of the parallel bars were zipped tied and the plugs were zipped tied so the didn't accidentally come out of the plug. And of course the no break power would last a very long time, but we never pushed it past 1/2 hour. The biggest problem was more in line with a disk controller going nuts, or a nic card that would go berzerk, or bad memory, which in turn would put curd into the data base. For us it was a case of fix and forget it, because there were other fish to fry. Never did have a real power outage to the computer circuit, even when the room was flooded from a broken pipe in the ceiling. Lost the lights, etc., but computer kept right on humming until we shut them down in a speedy, graceful shutdown.

	-skip		-skip

NeilArmstrong: Added a glossary link to Action~

2012-07-25T09:19:03Z

Added a glossary link to Action~

← Older revision		Revision as of 09:19, 25 July 2012
Line 152:		Line 152:
	On node EHR:vista there is 1 free Sub-Manager(s). Status: Run		On node EHR:vista there is 1 free Sub-Manager(s). Status: Run

	Enter monitor action: UPDATE// ^		Enter monitor [[action~\|Action]]: UPDATE// ^

	Select Taskman Management Utilities Option: halt		Select Taskman Management Utilities Option: halt

NeilArmstrong: Added glossary link to Allergy~

2012-02-22T07:10:12Z

Added glossary link to Allergy~

← Older revision		Revision as of 07:10, 22 February 2012
Line 576:		Line 576:
	> If the answer is that the business processes of health care (at least as addressed by VistA) are not inherently robust in the face of non-Atomicity and non-Consistency, then what mechanisms currently exist in VistA that provide these requirements?		> If the answer is that the business processes of health care (at least as addressed by VistA) are not inherently robust in the face of non-Atomicity and non-Consistency, then what mechanisms currently exist in VistA that provide these requirements?

	This is interesting. It seems uncontroversial that database integrity is a requirement for health information systems (for example, we wouldn't want a penicillin allergy to be "lost"). In the ACID model, I would be hard pressed to say which of the four properties (atomicity, consistency, isolation and durability) can be dispensed with. But what is less obvious is that the ACID approach is the only route to database integrity. Thee latest ACM Queue takes this on with a little column whimsically entitled "BASE: an alternative to ACID"		This is interesting. It seems uncontroversial that database integrity is a requirement for health information systems (for example, we wouldn't want a penicillin [[allergy~\|Allergy]] to be "lost"). In the ACID model, I would be hard pressed to say which of the four properties (atomicity, consistency, isolation and durability) can be dispensed with. But what is less obvious is that the ACID approach is the only route to database integrity. Thee latest ACM Queue takes this on with a little column whimsically entitled "BASE: an alternative to ACID"

	*http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=540&page=1		*http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=540&page=1

DavidWhitten: /* The Intracare Implementation Log (Back to Episode 7) (Back to Log Homepage) (On to Episode 9) */

2009-05-08T19:53:03Z

The Intracare Implementation Log (Back to Episode 7) (Back to Log Homepage) (On to Episode 9)

← Older revision		Revision as of 19:53, 8 May 2009
Line 1:		Line 1:
	==The Intracare Implementation Log [[Episode7\|(Back to Episode 7)]] [[Intracare Implementation Log\|(Back to Log Homepage)]] [[Episode9\|(On to Episode 9)]]==		==The Intracare Implementation Log [[Episode7\|(Back to Episode 7)]] [[Intracare Implementation Log\|(Back to Log Homepage)]] [[Episode9\|(On to Episode 9)]]==
			[[Category:Intracare Implementation Log]]

	==Power outage restart==		==Power outage restart==

Ssw0213: Readability edits

2009-05-07T22:13:13Z

Readability edits

Show changes

Ssw0213: navigation links

2009-05-07T20:56:25Z

navigation links

← Older revision		Revision as of 20:56, 7 May 2009
Line 1:		Line 1:
	==The Intracare Implementation Log [[Intracare Implementation Log\|(Back to Log Homepage)]]==		==The Intracare Implementation Log [[Episode7\|(Back to Episode 7)]] [[Intracare Implementation Log\|(Back to Log Homepage)]] [[Episode9\|(On to Episode 9)]]==
	==Power outage restart==		==Power outage restart==

Line 1,031:		Line 1,031:
	"we have met the enemy and he is us." - Pogo		"we have met the enemy and he is us." - Pogo

	[[Intracare Implementation Log\|~~Back to~~ Log Homepage]]		[[Episode7\|Episode 7]] [[Intracare Implementation Log\|Log Homepage]] [[Episode9\|Episode 9]]

Ssw0213: 8

2009-05-06T22:22:46Z

Show changes