Difference between revisions of "Ignacio Valdes Implementation Log"
m (6) |
(11) |
||
Line 15: | Line 15: | ||
==Episode 9== [[Episode9|Initial hospital configuration terminal session]] | ==Episode 9== [[Episode9|Initial hospital configuration terminal session]] | ||
==Episode 10== [[Episode10|Psychiatry specific DSM Axis II-V diagnosis, precaution ordering]] | ==Episode 10== [[Episode10|Psychiatry specific DSM Axis II-V diagnosis, precaution ordering]] | ||
− | + | ==Episode 11== [[Episode11|WorldVistA configuration Utility, KIDS Patch Install]] | |
− | |||
[[Category:Intracare Implementation Log]] | [[Category:Intracare Implementation Log]] |
Revision as of 03:37, 10 May 2009
Ignacio Valdes, a psychiatrist in Houston TX, has been charged with implementing VistA for a chain of psychiatric facilities. He has posted his progress on the Hardhats discussion group. Some of the threads are reproduced here.
The traditional method for implementing a new VistA instance has been likened to an old-fashioned barn-raising: at the appointed time the holders of "institutional memory" would gather and put the thing together. There was no written blueprint, yet at the end of the day there would be a solid, usable Initial hospital configuration terminal sessionstructure in place. The unedited discussions quoted here give a taste of the skill and wackiness of such a gathering.
In this case however, the ultimate goal is not just a new VistA instance, but also a blueprint for how to do it.
==Episode 1== Do What and Why? ==Episode 2== Multiple Sign-ons ==Episode 3== IPv4 vs. IPv6 ==Episode 4== Keane records integration/population ==Episode 5== Patient picture? ==Episode 6== (missing) ==Episode 7== iptables and other useful port commands ==Episode 8== Power outage restart ==Episode 9== Initial hospital configuration terminal session ==Episode 10== Psychiatry specific DSM Axis II-V diagnosis, precaution ordering ==Episode 11== WorldVistA configuration Utility, KIDS Patch Install