-
Notifications
You must be signed in to change notification settings - Fork 5
eHMP Debugging Testing Commands
This page is just a collection of random utilities that I have found in the eHMP code base that help me confirm whether things inside of it work or not. Feel free to contribute.
If you managed to deploy the eHMP UI, you have a health-check API that is publically available (no need to login): You can reach that using https://ehmp-ui-ip/resource/healthcheck/detail/html.
Buried in the documentation, this is obtained using the following code:
WRITE $$BASE^XLFUTL($$CRC16^XLFCRC($$KSP^XUPARAM("WHERE")),10,16)
$$KSP^XUPARAM("WHERE") gets you your christened domain.
You sync patients from a VistA Instance by running this against the vxsync machine:
curl -I http://vxsync-ip:8088/data/doLoad?sites={Vista Site Hash}
curl will not return any output. The -I shows you the actual returned headers.
To check how far the load is progressing, do this on the JDS machine:
curl http://jds-ip:9080/statusod/{Vista Site Hash}
This will show you a huge bunch of counters. You are looking for a flag called syncCompleted and you want that to be true.
According to the documentation, there is a tool called sync-stat.sh which will let you debug a single patient sync. Test it like this:
cd /opt/tools
sync-stat.sh -n "lastname, firstname, mi" -det -ver
To reset all syncs in vxSync, you can do this:
node tools/rpc/rpc-unsubscribe-all.js --host <vistaip> --port <vista-xwb-rpc-port>
D FULLRSET^VPRJ resets JDS--removing all the patients in it.
JDS can be cold started (listeners etc) using D GO^VPRJRCL.
To check that JDS is running curl http://jds-ip:9080/ping.
Sometimes, individual patients do not make it to Solr. Here's how to check. On the vxsync machine, you can check the contents of the solr index:
./check_solr.sh -startdate -s 20160801000000 -e 20160816000000
To resync a single patient to solr, do this:
./solr-reindex.sh -p "<vista site hash;patient dfn>"