LA eCR Peer to Peer call "feedback"
Hi Louisiana!
I'm sorry I missed the eCR Peer-to-peer call last week, but I'm looking at the notes. I have to chuckle about the "ersatz" informatics group (you mean the usual way we get to form a peer group -- by whose interested LOL). Also the issue of inheriting a system that has no documentation on how it works. For our ELR project, we've tried to really push ourselves to document every process and IT development as much as possible (even though we are behind a bit on that).
We have developed a QA tool in our ELR System based on the Kendo UI (the ELR Transaction Logger). I believe there is an open source version (Carl from our team will have to comment on that), but we actually use the licensed version. Carl has developed ways of showing how many input messages, how many output, if a message is missing some desired variable and what that is, if a message failed, if a new LOINC or SNOMED has been sent we haven't mapped, or if there is a missing LOINC or SNOMED, etc. Because there are only two of us running the ELR System and project, we have been able to put HL7 validation of both structure and content using the PilotFish (TM) Technologies integration engine and console. Carl also maintains mapping using Base-X and that mapping is mirrored in our Maven surveillance system. Our outputs include an xml format for our Maven system, and TSV (flat file) formats for programs that don't want data uploaded into Maven, or for the HIV folks still using eHARS, or for programs like blood lead that want to review the files and make corrections for missing information especially for child lead results. We can take these TSV files and reprocess into Maven formats (blood lead also uses Maven for surveillance and case management).
Other than pulling line list reports and using pivot tables, I haven't done any other ELR metrics (except for the annual ELC volume reports which are gross estimates as we have not yet gotten all labs using ELR). Except Zika -- we do populate the specimen collection date and date tested and date report received for tests done at our state lab for required Zika grant metrics.
We'd be happy to demonstrate our system and the Transaction Logger for anyone interested. It might give folks some useful ideas.
I'm sorry I missed the eCR Peer-to-peer call last week, but I'm looking at the notes. I have to chuckle about the "ersatz" informatics group (you mean the usual way we get to form a peer group -- by whose interested LOL). Also the issue of inheriting a system that has no documentation on how it works. For our ELR project, we've tried to really push ourselves to document every process and IT development as much as possible (even though we are behind a bit on that).
We have developed a QA tool in our ELR System based on the Kendo UI (the ELR Transaction Logger). I believe there is an open source version (Carl from our team will have to comment on that), but we actually use the licensed version. Carl has developed ways of showing how many input messages, how many output, if a message is missing some desired variable and what that is, if a message failed, if a new LOINC or SNOMED has been sent we haven't mapped, or if there is a missing LOINC or SNOMED, etc. Because there are only two of us running the ELR System and project, we have been able to put HL7 validation of both structure and content using the PilotFish (TM) Technologies integration engine and console. Carl also maintains mapping using Base-X and that mapping is mirrored in our Maven surveillance system. Our outputs include an xml format for our Maven system, and TSV (flat file) formats for programs that don't want data uploaded into Maven, or for the HIV folks still using eHARS, or for programs like blood lead that want to review the files and make corrections for missing information especially for child lead results. We can take these TSV files and reprocess into Maven formats (blood lead also uses Maven for surveillance and case management).
Other than pulling line list reports and using pivot tables, I haven't done any other ELR metrics (except for the annual ELC volume reports which are gross estimates as we have not yet gotten all labs using ELR). Except Zika -- we do populate the specimen collection date and date tested and date report received for tests done at our state lab for required Zika grant metrics.
We'd be happy to demonstrate our system and the Transaction Logger for anyone interested. It might give folks some useful ideas.