So far so good! It’s been about a week since download/install. I’ve been able to get a procedure going for lab orders and downloads as txt. I’ve then been steered towards saving towards a system folder. Which isn’t agreeing with my OpenEMR-Mirth-Elis stubbornness, 
. Mirth isn’t giving much cooperation of setting up a channel yet. So I figured a good time to check in and everyone call me a noobie. That I should be using SMTP or something besides machine folders to currently store test toxicology orders.
A little easier to describe where it’s at. The Word screenshot shows success up to generally the center top left portion on the Mirth print screenshot. Basically 5 of 6 phases left. OpenEMR itself seems great! Obviously putting together/entering toxicology lab procedures/orders to send to my clia-aiver lab will take some time itself. A little leary going down a file folder read path, but doesn’t seem more than 6 extra hours later.
There we go! OpenEMR sending Lab orders to OpenELIS. I still need to test sending results back. And pretty good odds OpenELIS isn’t out of box prompting a provider in OpenEMR of patient labs back. Got through utilizing DORN for FHIR between containers. Hopefully by next weekend it’s at just adding loinc codes and/procedures.
Ugh, The OpenELIS intro certificate(s) expired, lol. It took a little finagling but seems fhir TLS is back up. I’m working on understanding the little triangular quirk of a non client-server specified certificate satisfying emr to elis and the elis/fhir trigger with importing service requests. Of course replacing elis to emr certificate files for final reports lead to the bright idea of getting away from Test_Lims to my organization as the default and landed those resulting errors with unrecognized certificate for the ensuing emr to elis tidy up work. I was sort of hoping to be past cron polling before tidying up data exchanges, but even with the redundancy of AI never wanting to just replace a certificate. Only seems maybe 4hrs from an easier round of certificates 2 years from now. I’m not convinced AI understands a Questionnaire in JSON doesn’t necessarily disappear to auto populate locations from EMR’s drop down either. I know the route AI is taking and it’s right, but I’m also like, a generic non client-server certificate for an app to talk to itself doesn’t seem bad either, lol. A little bit of an updated diagram of intended integrations. Definitely turned a longer 2weeks than intended, but seems worth seeing the integration workflow through Linux cmd and Docker over just browsing the files in Windows. If it’s what I end up using for a behavioral health clinic. Makes sense to become file proficient. Not crazy about seeing Mirth back on the itinerary, but I’m still at imaging modules being file storage for what best case would be more external storage space anyway when emr has a viewer. If I contract an attending, I think the integration would be appealing though. At least to equipment sales reps, lol. As a chemical dependency counselor though. The emr/elis integration seems a really nice workflow to maintain documentation of a CCF workflow. Even if mostly just intended waiver toxicology for contingency management, etc. initially.
