877.303.3377
|
Sep 26
2011
|
Healthcare Technical Services Projects for September 25Posted by admin in Untagged |
|
- ITS Routing Rules Research and Changes – Completed detailed research on the content of ITS ORU messages in production and provided this information to the client along with a request for guidance regarding their requirements for identifying Radiology vs. Transcribed Reports. Worked to designate a Meditech ITS Expert IT resource to help with the ITS departments and report types. Ultimately, I was able to identify a relatively simple rule for identifying Radiology reports which was any reports for ITS report department “DIS” with all others being considered “Departmental” in the Provena vernacular and roughly analogous to the clients “Transcribed” reports. Based on this information, updated the routing rules in the client schema to route Radiology reports and Transcribed reports in separate data feeds on their way to the client and was able to start the backload for those data types. Did not move forward with the changes and backload until I received word from the Microsoft Project Manager that he was in agreement with our analysis of Radiology vs. Transcribed within the context of Meditech ITS.
- Backload of Historical Data – Completed backload of Historical Data from 7/1/11 forward. Completed backload of historical data for all data types and all six ministries. The historical backload processing required some very detailed baby sitting in order to ensure that all historical data files were processed through the client schema and delivered in sequence to the client from 7/1/11 forward. In total, there were 18 separate data file archive locations for pulling the data files for the backload and some tricky issues dealing with the nature of the “robocopy” setup that “archives the archives” from the active e*Gate servers to the ACN013 data archive server.
- Production Implementation of Schema Bridges to client Schema – Up front, worked within the Integration Team’s “Ports” MS Access database file on the X drive to identify and assign ports for 4 control brokers, 7 JMS IQ Managers and 4 outbound HL7 e*Ways to the client including a separate set of ports for TEST and PROD. Recorded within the “Ports” MS Access file all inventory for all of the above. Subsequently, exported the schema from ACN015 and imported that schema into ACN016. Completed configuration changes to update all control brokers, IQ Managers and HL7 e*Ways to use the port assignments from PROD. Also, updated all IQ Manager, JMS e*Way Connections and Batch e*Way Connections to point to the new PROD drive letter for logical server AEGT14T which is the L: drive (change from I: drive for TEST AEGT11T). Also, created Cluster Resources for all new control brokers and configured them per conventions established from the current e*Gate environment’s Cluster Resource configuration defaults. Subsequently, turned on production interface components to provide real-time data feeds to the client from data fed from the schema bridges in the current environment. Turned on these live feeds once the historical backload was complete.
- Production Implementation of the client Schema – Completed production implementation for all four client Bridge schemas. This work was intensive on ensuring that the proper message subscriptions were defined for the 18 different data feeds from the six ministries. Prior to the configuration of subscriptions in PROD, exported each module from its respective CONV schema and then imported them into the analogous PROD.
- Changing 5.6 access for consultants and analysts for different testing scenarios.
- Creation of EPIC training users.
- Modification of NUR 200 menu.
- This week, the ASAP team presented three new workflows to Ops. We are also preparing for two Ops meetings coming up next week. We need to present past workflows to Physician administration. During the second meeting next week, we will be presenting our final three workflows. The ASAP team has been preparing for the upcoming start of the build phase therefore we have been researching Clindoc documentation and familiarizing ourselves with our northern location’s setup.
- The team held a Gap Analysis meeting and discussed electronic charges in Epic, Reports, and Build trackers. We were able to review all OpTime online reports this week. We ran all of the Norther location’s OpTime online reports and sent them to for review. We were also able to review all of the northern location’s Clarity Reports in production as well as start to document in the build tracker and prepare for documenting the Gap Analysis.
- This week the remaining Radiant workflows (excepting sedation) were completed. All workflows except one have received NCH signoff. Signoff for the remaining workflow was deferred until next week given team availability during UGM week. Review of the orders list distributed by the Orders team was completed; no immediate revisions were required. There has been some preliminary discussion by the team toward taking advantage of the opportunity to tweak preference lists as part of this project. The team will discuss this further next week and report any developments to the Orders team.
- Performed Rhapsody testing and pointing out build deficiencies that need to be addressed prior to go live.
- In progress Rhapsody Route Design FTP log/DB logger to capture Financial transaction between Meditech/Lawson/LSS (Testing)
- Redesigning SQL table for FTP log (Waiting for DB to be populated)
- Created new HL7 Rhapsody Adt message definitions to handle new interfaces.
- Created Rhapsody ADT Routes for Meditech to MedData App
- Created Rhapsody ADT Route for Meditech to IPC App
- Created Rhapsody ADT Route for Meditech to Penrad App
- Created Rhapsody ADT Route for Meditech to TeamHealth App
- Debugged Javascript for message filtering from Meditech
- Completed specifications for Hawaii Server translator.
- Began work on HDOHDecryption and HDOHCleanup translators
- Completed cross system merge testing.
- Continued work on complex merge testing.
- Activation preparation activities.
I am very impressed with Orchestrate Healthcare’s professionalism ... industry skills and also with their communication — they are responsive experts.