I've installed OpenVista per the 10 minute install instructions and the basics go very well. A couple of things though.
1) "Notify Nursing ADP Coordinator and Site Manager that this patient was not admitted into the Nursing Service because Nursing Site Parameters were not updated"
This is "error" message I get when I admit (Admit A Patient) or transfer one. I get bounced back to the "Open" prompt. Am I missing some configuration? How do I set up these "nursing paramaters"?
[BTW, this leads to a weird behavior where HL7 isn't sent until a patient is discharged. It seems only nursing doesn't need discharge.]
2) Programmer Mode - bounced back to Open> again
> openvista open
open> D ^XUP
setting up programmer environment
Identity = man,sys (or man,patch) ...
...
Enter Programmer Mode
and I'm bounced back to the prompt. In other words, I'm not allowed in Programmer Mode. Is there a missing permission?
Thx,
Conor
I can't answer your first question, but as for number 2, I think that's the desired behavior -- the OPEN> prompt is the programmer prompt (which is also sometimes referred to as the MUMPS prompt). When you're running "openvista open" from the Linux prompt, our tools can tell that you already have shell access to the system, so it drops you into the programmer prompt by default. If you "D ^XUP" (for programmers) or "D ^ZU" (for end users) to "log in" to OpenVista, then request the programmer prompt, it will just drop you back down.
In a production environment, an end user would connect and see an access and verify code prompt, then be dropped into their primary menu. So for a physician, that might be a Physician's Menu, but they wouldn't have access to the programmer prompt by default -- they would need to use the Programmer Mode menu option to drop down to the prompt. If you want to see what this is like from a Linux command prompt, use "ovtied open" instead of "openvista open". Alternatively, you could SSH back into the same machine ("ssh -i /path/to/id_rsa openvista@localhost").
There is a Hospital Locations file within OpenVista that contains both inpatient locations (wards or units) and outpatient locations (clinics). There are also nursing locations that need to be setup. The Nursing Locations file points to the Hospital Locations file. If you are trying to admit a patient, I assume that you have units already setup. Now, you need to setup the nursing units:
Once logged in and at Systems Manager Menu option prompt, enter TEST AN OPTION.
At Test an Option Not In Your Menu: enter NURSFL-LOC
At Select NURSING UNIT NAME: enter a Nursing Unit name to match your hospital unit name.
At HOSPITAL LOCATION INSTITUTION: enter your INSTITUTION name.
AtPATIENT CARE STATUS: enter ACTIVE
At WARD STATUS: [ENTER]
The following text should appear with the hospital unit of the same name listed.
Below is a listing of associated MAS wards
1. XXXX
Would you like to (A)dd new MAS wards, (D)elete existing units from the
above listing or (B)ypass this prompt (A/D/B): B// BYPASS PROMPT
There are no AMIS bed sections associated with this Nursing unit.
Would you like to (A)dd new AMIS bed sections or (B)ypass
this prompt (A/B): B// BYPASS PROMPT
Follow these steps for each hospital location/inpatient unit that you would be admitting patients to for nursing care.
On the premature end of "admit patient". Before your answer, I installed WorldVista to compare apples to ... and it needed more configuration than yours. I set up an institution and tweeked MAS parameters (as per someone's instructions) and then it admitted a patient and prompted for another (and sent HL7 immediately). No premature exit. The nursing warning? That showed up in WorldVista too so it mustn't matter.
So I returned to OpenVista and tried to play with MAS parameters - which don't seem to be set? - and after doing that, it started behaving like its sibling! I don't know why - I'm a complete newbie to MUMPS and VistA. One curiosity: OpenVista let's me send (HL7) pings over TCP connections but WorldVista doesn't. WorldVista seems to enforce that only Vista's can exchange pings. This must be a setting of some sort but damned if I know where that's configured! (Overall, I'm impressed by VistA's scale and range but the ease of patching/adding routines does make it difficult to track options/alternatives.)
It's late. I'll tinker some more tomorrow.
Thx for all the info,
Conor
p.s. I made a graph of OpenVista's HL7 configuration. I need to do the same for WorldVista and compare. Are documents such as this of interest to the OpenVista project?
hoot72cpd wrote:
<snip>
p.s. I made a graph of OpenVista's HL7 configuration. I need to do the same for WorldVista and compare. Are documents such as this of interest to the OpenVista project?
Absolutely. OpenVista includes our standard interface suite (charges, orders, results, transcription, etc.), however the documentation is piecemeal and a work in progress. Anything you find of use in your research that could help others, would be more than welcome. The wiki is here and editable OR you can send information to Jon, Alli or myself and we can post for you. Thanks for contributing!