Ignacio Valdes Implementation Log: Difference between revisions
From VistApedia
Jump to navigationJump to search
DavidWhitten (talk | contribs) m DavidWhitten moved page Cambridge / Intracare Implementation Log to Ignacio Valdes Implementation Log |
DavidWhitten (talk | contribs) No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
[[Category:Cambridge / Intracare Implementation Log]] | [[Category:Cambridge / Intracare Implementation Log]] | ||
==[[Ignacio Valdes Implementation Log/ | ==[[Ignacio Valdes Implementation Log/Episode1|Episode 1 The Layer Cake]]== | ||
==[[Ignacio Valdes Implementation Log/Episode2|Episode 2 Multiple Sign-ons]]== | ==[[Ignacio Valdes Implementation Log/Episode2|Episode 2 Multiple Sign-ons]]== | ||
==[[Ignacio Valdes Implementation Log/Episode3|Episode 3 IPv4 vs. IPv6]]== | ==[[Ignacio Valdes Implementation Log/Episode3|Episode 3 IPv4 vs. IPv6]]== | ||
| Line 35: | Line 35: | ||
==[[Ignacio Valdes Implementation Log/Episode26|Episode 26 Scheduling patients for a Clinic]]== | ==[[Ignacio Valdes Implementation Log/Episode26|Episode 26 Scheduling patients for a Clinic]]== | ||
==[[Ignacio Valdes Implementation Log/Episode27|Episode 27 Suppressing WORK COPY -- NOT FOR MEDICAL RECORD]]== | ==[[Ignacio Valdes Implementation Log/Episode27|Episode 27 Suppressing WORK COPY -- NOT FOR MEDICAL RECORD]]== | ||
==[[Ignacio Valdes Implementation Log/Episode28|Episode 28 Easy template importing and exporting== | ==[[Ignacio Valdes Implementation Log/Episode28|Episode 28 Easy template importing and exporting]]== | ||
==[[Ignacio Valdes Implementation Log/Episode29|Episode 29 Adding Appointment Schedule Menu to Clerk ID.]]== | ==[[Ignacio Valdes Implementation Log/Episode29|Episode 29 Adding Appointment Schedule Menu to Clerk ID.]]== | ||
==[[Ignacio Valdes Implementation Log/Episode30|Episode 30 Change Access/Verify code text to UserID/Password?]]== | ==[[Ignacio Valdes Implementation Log/Episode30|Episode 30 Change Access/Verify code text to UserID/Password?]]== | ||
Latest revision as of 04:45, 13 November 2020
Astronaut, LLC [1] has been charged with implementing VistA for a psychiatric hospital. Posted is the progress on the Hardhats discussion group [2]. 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 structure in place.
The ultimate goal of this is not just a new VistA instance, but also a blueprint for how to do it.
Note that this page is a work in progress; see Hardhats [3] for logs that do not appear here.
