877.303.3377
|
Jul 09
2011
|
Healthcare Technical Services Projects for July 8Posted by admin in Untagged |
|
- Cardiology Lab Results Interface – Practice representative reported that they were no longer receiving results for a physician assistant. Completed research of old emails and found that her provider mnemonic was changed a few months after the practice go-live. Subsequently, updated the associated data map file to ensure that the new provider mnemonic would be used for the lab results filter logic within the e*Gate collaboration. Moved the new data map file into production and then confirmed a day later that physician assistant’s lab results were being routed to Heartland. Also, notified client of the same.
- VendorFTP Schema Interfaces Start/Stop Schedule Issues – Worked at length to research why after the most recent down time that the start/stop e*Way schedules were no longer functioning as configured. Ultimately, discovered via Oracle web site knowledge base research that the –ns parameter cannot be included in the e*Gate Control Broker start up script if the user wishes to configure a stop/start schedule for e*Ways within that Control Broker. Modifed the startup script for the Control Broker to remove the –ns parameter, bounced the control broker, re-set the schedules and confirmed that the start/stop schedules were working properly once again.
- TMG (eMDS) Interface for Conversion – Completed e*Gate changes and testing to filter out NTE segments (within OBX segments) that were redundantly reporting the performing laboratory site (already sent in OBX.15 – Producer’s ID). Once the changes were successfully tested, moved the change into production and notified TMG of the change.
- ResponderNet ADT Interface – Received a report that the e*Gate collaboration for A34 (merge) messages was throwing the exception labeled “NoSuchMethodError”. This one took a while because the line of code for which the exception was thrown was perfectly fine. Ultimately, identified the fact that the underlying ETD was corrupt. Created new ETD as an exact copy of the original and then used this new ETD to recompile the collaboration rule that was throwing the exception. Once the new ETD was in place, the exception was no longer thrown and the 50+ messages that were sitting in the queue were processed successfully. Subsequently, sent out detailed email to the team warning them to keep a look out for this error and listed for the team the resolution path that I used.
- MCHIE Project Data Flow Diagram – Completed development of the data flow diagram (Visio) including changes after client’s review and then delivered the completed document to MCHIE representative. Also, worked to confirm that it would be OK to pull copies of the Meditech HL7 Interface Specfication documents based on her review. After thier review, pulled the copies together and sent them to our client.
- MCHIE Project Message Metrics – Created a utility for generating message count metrics that was tailored from a similar utility created for the Meditech 5.6 Upgrade project. The purpose of the utility is to generate and provide message volume metrics to the MCHIE team. The metrics they are asking for include maximum messages per day, peak volumes and average message sizes for each of the 4 data types: ADT, LAB, RAD and Dictation.
- AEGT11 Registry Service Issues – Worked at length at various times during the week to research the potential causes of this latest registry service issue which required that the registry be bounced each morning this week from Tuesday 7/5 through Friday 7/8. The symptoms of this issue are that nobody on the team is able to access schemas defined to the AEGT11 registry. Ultimately, identified that there was a rogue e*Gate BOB running out side of the control broker and was using credentials that were obsolete as of 7/4 when user A01JOHTH changed his password. The other modules running under the control broker were fine, but this one was failing its sign-on every 30 seconds and each time increasing the number of connections to the registry closer and closer to the maximum number of connections value (increased to 3072 by the end of the week). Final work on this issue was to kill the rogue process which stabilized the AEGT11 registry service once again (did not have to bounced throughout the weekend and seems stable this morning Monday 7/11).
- Neuroscience (SSC) ADT Interface – Worked at length with client representatives to research and identify a method for filtering ADT events based on the Consulting Provider field in the ADT message (PV1.9). It turns out that testing/validation performed Wednesday morning 7/6 was incorrectly focused on the wrong ADT feed from Meditech. Final decision after several go rounds was to use a list of provider mnemonics (captured in an e*Gate datamap file) to allow ADT messages with Neuroscience providers acting as consulting providers to be sent to the SSC system. Also, identified overriding filter rule that will send all ADT messages where the patient location is set to the new location that has been defined specifically for the Neuroscience clinic/site.
- Transolutions “CrossOver” BOB Exceptions (2 hours) – Worked to resolve two separate exceptions that were occurring since go-live related to the use of the “substring” method within this BOB.
- Datanex DRA Tool PSFTP Interface – Worked to perform a series of manual file transfers to and from Sentry to move us closer to loading all of the historical outpatient claims data into Senty and to provide the reports from Sentry back to the CBO staff.
- Contacted Meridian Integration Manager to obtain EMR resource.
Orchestrate was sensitive to our budget constraints. They were easy to work with ... overall a very upbeat and positive experience.