|
Healthcare Technical Services Projects for May 29 |
- Parkview Code set questions and data analysis review.
- Medicity Client Prod Package reviewed, Centura UAT, SLVRMC UAT,
- regarding Grid-EHR interface.
- Cert deployment to ensure all client environments are in sync prior to prod deployment.
- Working on Cert package for the lab interface.
- Cert package for client Lab published, BOM sent to client
- Prod package in process for deployment next week
- Multiple discussions regarding testing and issues, updated code sets and processed 275 new prod ADT messages to cert for issue analysis.
- Successful Cert deployment for CORHIO SLVRMC Lab interface. Sent 125 prod messages to cert with only 1 failed message.
- Client UAT issues
- Assisted in testing the merge functionality in PA
- Reviewed MHS code sets and sent back for some clarification
- Merge issue - clarified
- DB parser issue - resolved
- UAT issue – in progress
- Continued preparation of Rhapsody Test Scripts and testing.
- Continued creation and comparison of the 1500 HL7 messages sent from the VITL providers for Medicity.
- Participated in the ePI Super user training.
- Helped reconcile providers as part of core Eclipsys RIS load.
- Interfaces built for Epic Outbound Testing:
- ADT from EPIC to ancillary systems:
- -MUSE EKG
- -Xcelera Cardiology
- -Xper Cardiac Cath Lab
- -Cerner Copath
- EPIC and Rhapsody Documentation
- Rhapsody testing
- Mapping and Design requirements
- Epic to Hyland Onbase Documentation Session meeting
- Radiology Interface Vrad Team Meeting
- HL7 field testing radiology results to ADT/ORU/ORM to Mckesson Star
- Safety Surveillor
- Sent ADT and Lab samples to Premier
- Got Results route and Mapper completed
- Set up call with Premier
- Pharmacy Orders also sent to Premier- they now have to adjust to an RDE order message
- CareStream
- Got MFN messages configured and mapper in place for physician updates- Problem with EPIC and Morrissey interface. Also Epic may not have the ability to transmit State ID # until after go live date.
- Sent samples for verification of the MFN messages sent to Carestream
- The MFN portion will not make the June 3rd deadline and may not make the go live date due to the Lack of State ID # by EPIC
- Discussion with Physician and team per email from received where Epic was saying some scheduling would be done in Carestream. Clinical Team said “NO”
- Set up special call for May 31st to work out the process flow for scheduling- Cadence group, Orders group.
- Lab Result messages are configured to process to Carestream results
- Set up the RHIO route- need to test next week
- MedSelect Medication Dispensing System
- Continued Unit testing
- Sent Dispense messages from MedSelect to Epic
- State Immunization Registry
- Requested Extract for Testing of Conversion to EPIC.
- Prepared checklist document to use with EPIC to highlight responsibility for Data transformation issues highlighted in testing
- Radiation Oncology System
- Continued Unit testing
- Encounter Conversions data to EPIC
- Assisted making changes to interface highlighted by EPIC testing.
- Physician Credentialing system
- Test data flowing from TEST instance to Rhapsody.
- Meditech 5.6 Upgrade Meeting with Meditech – Attended meeting with Meditech regarding the HL7 interface changes for the Meditech 5.6 upgrade project.
- e*Gate Update 2 Project Control Broker “-egst” parameter issue (20 hours) – Continued to work the issue by focusing on the issue of the Windows Server 2008 R2 Cluster Service running under the “Local System” user which is a change from the Cluster Service for Windows Server 2003 which ran under a user defined domain “Cluster Administrator” account. Completed research on this issue (Microsoft Windows Server 2008 R2 Technical Specifications web site) and discovered that this is a fundamental change for Windows Server 2008 R2 and that it should not be changed. Worked to confirm this was in fact the case. Attempted to modify the “Log On As” user for the Cluster Service with no success. User then contacted Microsoft support who confirmed that the Cluster Service must run under the “Local System” account based on the new design/configuration for the cluster service with Windows Server 2008 R2. Returned focus to the e*Gate Update 2 application and found references to e*Gate defined Windows Registry entries. Ultimately found an e*Gate registry key called “Base Directory” that was superseding the specified “-egst” parameter for the control broker start up scripts. After deleting this Windows Registry entry, the problem was resolved. Success! Once the solution was confirmed with some additional testing against other logical servers/drives, contacted Lori and Tony to notify them that the issue was resolved and turned my attention to documenting this workaround and to re-installing the e*Gate Update 2 software based on the new solution.
- e*Gate Update 2 Project Re-install / documentation update after “-egst” issue resolved – Completed documentation of the workaround to delete the “BaseDirectory” Windows Registry Key. Completed re-install of the e*Gate Update 2 environment while validating/updating the installation document one final time. Once the install was complete, notified the team that we are now ready to utilize the e*Gate Update 2 environment with the necessary flexibility to use whichever logical server/drive for a participating host that we choose. The main impact is that this allows us to create the new environment to truly mirror the current environment.
- Meditech 5.6 Upgrade Project – Received some solid direction to get started with analysis of the Meditech HL7 ADT feeds that are sent to e*Gate in order to document the Message Types, Trigger Events, Segment and Field usage for each of the data feeds for each ministry for the current Meditech 5.5 environments. A team member shared a template spreadsheet to work with that I soon expanded to meet the specific needs for ADT messages from Meditech. Began development of an e*Gate collaboration service utility that will process any number of messages producing a report that lists all of the Message Types, Trigger Events, Segments and Fields that are actually used in production HL7 ADT messages. Structured the utility in a generic fashion so that it can be used for all future HL7 feed analysis (Lab Results, Text reports, RX Orders, etc.) Also, documented for each Meditech ADT feed to e*Gate the associated e*Gate module that receives the feed and the e*Gate archive folder/file specifications for each.
- Support for the Null Pointer Exception issue – Worked to open a Service Request with Oracle for the issue he is experiencing with a newly established TEST control broker in the SeniorServices schema. Subsequently, identified with Oracle’s support that the issue seems to be related to the JMS e*Way Connection configuration for the new control broker. Will continue to work this issue with Oracle next week.
 |
|
877.303.3377
Orchestrate Healthcare assessed our immediate issues and proposed a training solution that met our needs as well as worked within our budget