rdejournett wrote on Saturday, January 24, 2015:
There would probably need to be a bit of database work within the open emr, unless there was a field such as last update date/time. I am looking at the patietn_data table and don’t see such a field, but I do see some date fields. Basically we’d need to know what type of message to send and where to send it. For example the typical new patient ADT is an A04, so when a new entry in the patient_data table was created, we need somewhere to say ‘create an Hl7 message for this patient’, such as an HL7 table with the id, date, and message type.
As for the HL7 itself, probably it would be best to do the work in Mirth, that way the core application is insulated from any requirements. For example Epic doesn’t really like A04s without a CSN, they want an A28. Some don’t want version 2.5.1 of HL7, they want version 2.2 or 2.3.
My biggest question - is there a training database somewhere with some (fake) patient data? I’d need that or to figure out the app enough to do registration, scheduling, create vaccination orders, that sort of thing.