Introduction: To use the scheduling enhancements as provided by the VA you'll need two components installed. 1) The MDWS software - a .NET based solution which builds a communication bridge between itself and VistA. MDWS exposes VistA APIs as a web service interface which ultimately enables programmers to interface with VistA without having to know MUMPS. 2) The enhanced VistA Scheduling routines - a MUMPS based solution, enables MDWS to communicate with VistA. This document will detail the installation and maintenance of the second component, that is the enhanced VistA Scheduling routines,
The MDWS team is re-using the refactored code as provided by the EHR Refactoring Services group on OSEHRA. They maintain a public repository available here - https://github.com/kthlnkeating/VistA-FOIA. We pull from the upstream (EHR Refactoring Services) repository, enhance and test the code so it works with MDWS and VistA and release our own KID builds. (At the time of this writing, enhance includes wrapping the upstream code in RPCs and modifying routines where necessary so that MDWS can function correctly.)
Our enhanced Scheduling repository is available at https://github.com/VAchris/VistA-FOIA
We tag our builds. The current tag will always point to the latest and greatest code that has been exercised and/or includes bug fixes as noted in the commit log. The untested tag means simply exactly that - it is the latest/greatest and its untested.
Bugs: If you find a bug please submit it to http://issues.osehra.org/ under the Project EHR Refactoring. Also BE SURE to submit the bug under the Scheduling component otherwise your bug will fall into a bucket that few monitor.
- Decide whether or not you are daring or dashing. If you're daring then check out the untested tag ; otherwise you're dashing (and there is nothing wrong with that) check out the current tag. Either tag you choose you'll be cloning from https://github.com/VAchris/VistA-FOIA
- Once you have completed cloning, change directory to Packages/Scheduling/KIDS. In the directory you'll see two files ending in file extension KID. (KID refers to VistA's Kernel Installation and Distribution System; imagine if you will a package manager likening its capabilities to a RedHat RPM file.)
- Using VistA's KID menu options install the file SD_5.3_260003_RC2.KID [This is the EHR Refactoring Services BUILD]
- Using VistA's KID menu options install the file SD_6_0_1_TX.KID ; replace X with the file number available. Ie, SD_6_0_1_T7.KID
- That's it... you've successfully installed the enhanced VistA Scheduling routines.
Manually Verifying Installation:
- Using FileMan perform an inquiry on the OPTION file.
- Inquire about the entry named SD API.
- If you see the context and it's associated RPCs listed then you've installed our enhancements correctly.
When it is necessary we will release a new KID build otherwise you're probably wondering how we align ourselves without producing a KID file over and over again. We'll its pretty basic. We install the latest routines from your local git repository - we of course assume you placed the latest and greatest code in your repo. So how does it work?
- Prep your git repository - ensure you have the latest code in your repository.
- Starting from the root of your repo there is a file located in Scripts/BuildSingleRoutineFolder.bat [this is currently a Windows batch file because that is our assigned development environment] Take a look at the file and adjust the parameters as needed; really all we're doing is copying all the MUMPS routines into a single folder so that VistA can later ingest the updated routines.
- Once the BuildSingleRoutineFolder completes, from programmer mode run D EN^MDWSPKG and select the latest EHR Refactoring Services BUILD. (Ie, SD*5.3*26003)
- Tah dah! You have successfully imported the latest MUMPS routines without a KID build.