Bill,
We just started exploring using SQLite. We are currently on 5.7 and I have 6.0.1 loaded on a local VM that I am testing with. Someone said that 5.7 came bundled with SQLite, but it isn’t in our installation.
Anyway, we have numerous physician tables for various affiliations. What we want to do is create a single provider table that will emcompass all physicians, PA, NPs. We already have a thread that is used to create MFN staff update messages from a VRL file that is generated from a SQL DB trigger. This file is FTP’d on the back end to Cloverleaf.
What I’d like to do is tap into this and use this file to pull out the various fields that we need to populate the SQLite table. Then, in our various XLATE’s we will have to insert code to replace the currently TABLE lookups, so that we are pulling data from the SQLite table.
I’m envisioning an inbound thread that reads the VRL file from our HIS (containing provider updates from our DB trigger) and running a pre-proc that will either add, update, or remove/inactivate providers in the SQLite table. I’ll build an outbound file thread and a route that will copy pertinent info from the inbound VRL to a flat file for auditing purposes, so we can verify that changes to the SQLite table were actually made and agree with what changed in our HIS.
Is this clear as mud? 😀
.
