|
Healthcare Technical Services Projects for April 17th |
- e*Gate Update 2. Sent out email to the team to help re-establish confidence in our ability to move forward with moving Epic project development and testing to the new e*Gate Update 2 environment on ACN015/ACN016. After hearing back from the team, resumed work to get the environment ready again. Based on the issues experienced with the e*Way Connection lists not including a full list of add-ons and the issues with “Missing .def” file when attempting to create new e*Way configuration files in the new environment, completed full re-install of the e*Gate software to both ACN015 and ACN016. For this installation, completed the registry host install up front, renamed and update the registry service to AEGT11T:3700 and then proceeded with the Participating Host, GUIs and Add-on installations. Unfortunately, the issues with the e*Way Connection lists and “Missing .def file” errors were still occurring in the new environment after the re-install was completed for both ACN015 and ACN016.
- e*Gate Update 2. Opened “SR 3-3387879731: e*Way Connection Type pull down list is missing Add-ons (e.g Batch, JDBC/ODBC)” with Oracle support to begin a dialogue regarding the e*Way connection pull down list issue. I was able to resolve this issue on my own by following a solution path I found in the Oracle knowledge base articles. After resolving that issue, began work on the next issue which occurred when attempting to create new e*Way configuration files. The error experienced was “Missing .def” files. I was able to resolve this issue also by attempting the same workaround that resolved the e*Way Connection pull down list issue. Documented both workarounds which involve deleting a specific list of files from the ..\eGate\client\configs folder. For the pull down list issue, the “connectionpoint.ini” was deleted and for the “Missing .def file” issue, all .def files were deleted from each e*Way configuration sub-folder within the ..\eGate\client\configs folder.
- e*Gate Update 2. During the work with Oracle support on SR 3-3387879731, the Oracle support person floated the idea that maybe the 64-bit operating system (Windows Server 2008 R2) was a factor with regards to the issues experience with the e*Way connection pull down list and “Missing .def files” error when creating new e*Way configuration files. Ultimately, Oracle Product Management responded and updated SR 3-3387879731 stating that the 32-bit e*Gate Update 2 application is supported on the 64-bit Windows Server 2008 R2 operating system. However, Oracle pointed out that support for 32-bit applications must be enabled on Windows Server 2008 R2. I did some additional research on the configuration of the Windows Server 2008 R2 servers ACN015 and ACN016 and found that support for 32-bit application is enabled on the two server’s operating systems. I did send an email, requesting that they confirm this research, but have not yet heard back from them.
- e*Gate Update 2. Created a copy of the Epic_Test schema in the new E*Gate Update 2 environment. Also, completed set up of necessary Resources for the e*Gate Registries on AEGT11T and AEGT12T along with Resources for the three currently active Epic_Test schemas on AEGT023 (current environment). Sent out detailed email with full details on how to access the new environment using the existing GUI’s on ACN015 and ACN016. This strategy (for team members to use the GUI’s on ACN015 and ACN016) allows them to leave the current version of e*Gate on their lap tops so they can support both environments for the foreseeable future. The plan is to have them get comfortable with the new environment and once they are ready to start developing and testing Epic in the new environment, will re-copy the Epic_Test schema over.
- e*Gate Update 2. Completed 75% of the work to create the client e*Gate Update 2 Installation procedures including steps and notes to help the user along during the installation process. This document includes detailed instructions for installing the full suite to AEGT11T and AEGT12T. It also includes instructions for defining Resources for the e*Gate registries and control brokers and instructions for moving.
- NPR Extract for PMMC (2 hours) – Worked with the NPR team to inquire about and ultimately agree upon an end date for this interface based on feedback solicited from the Midas ABS users at PMMC. The end date established is 7/31/2011. Also, continued to attempt to solicit final word on what to do with the backlog of NPR Extract files that currently exists. Should we process the backlog or clear it before turning the interface back on is the question.
- DesponderNet ADT support. Worked to guide team members through the process of exposing the HL7 ACK payload in the e*Gate logs for the HL7 e*Way. Also, worked to identify why e*Gate considered the ACK to be a negative acknowledgement (MSA.1=”AE”). Subsequently, worked to identify that the PV1 segment was empty for the A34 that was being NAK’ed by Responder Net. Subsequent testing after change to populate PV1 segment was successful, positive ACK was returned by ResponderNet for the new A34.
- Project RED. Received responses on all of the questions that I posed regarding the proposed HL7 message feeds for Project RED. Sent out a email detailing the plan and schedule for turning on pilot live data feeds to Project RED for ADT and Pharmacy Orders.
- Rhapsody Datagate Conversion process including Route and Documentation Review Datagate Interfaces, Naming conventions, Site layout, requirements
- Datagate to Rhapsody migration
- Interfaces built for Epic Inbound Testing including Sunquest ORU Lab Results to Epic, Radiology ORU Reports to Epic, Invision ADT to Epic as well as Documentation
- Rhapsody testing, Mapping and Design requirements.
- Epic Radiology Results Testing Session meeting.
- Epic Sunquest Results Testing Session meeting.
- Performed a EPIC Radiology Interface Kickoff Meeting
- Build Message Definition to handle ORU messages per sample messages
- Waiting on Epic to add Provider Names/codes Lab Codes and Radiology Report Types
- ProAccess 5.3 PROD Deployment: worked with Medicity & the client on testing & validation of data in PROD environment, additional planning of data for Pilot, issue escalation/research/resolution.
- ProAccess 5.3 CERT Testing: assisted Medicity in researching testing issues in CERT environment with the cleint application teams, assisted with prioritizing testing & product issues, performed re-testing after CERT deployments to confirm testing & product issues were resolved.
- Documentation: tracking of ProAccess 5.3 CERT & PROD issues/updates/resolutions during testing & retesting on HIE SharePoint for the cleint and in Rally for Medicity.
- Project Management: PM related reporting and correspondence with Medicity for HIE project. Review with CHS and Medicity of project deliverables, updated Pilot scope & timelines, and updated PROD interface deployment timelines, internal & external client Support Procedures.
- Advanced the Outgoing Documentation Interface to Meditech:
- Communicated with Meditech and found which format they will/will not accept;
- Worked with Epic to produce “plain text” ED Summary Report. Discussed content and value. Mapped “RTF” ED Summary Report to identify codes and markup to possibly strip in engine;
- Building Blocks for 13 Surescripts interfaces complete, resent “Connectivity Questionnaire” to Networks for completion. Waiting for go ahead to test;
- Waiting for an assigned resource to build Quest Orders & Results
- Waiting for any go-ahead on Incoming & Outgoing Quest Lab Interfaces;
- Waiting for Epic Testing Go-Ahead on 13 SureScipts interfaces;
- Trying to define RTF vs Plain Text issues with Meditech.
- Assigned Carestream, Impaq Mosaic, CathLab Safety Surveillor, Clinipro, Scottcare TeleRehab interfaces
- Meetings on Carestream
- Scope Explosion- want to add a new entity to the November go live with no proper client MRN involved
- Started laying out routes for Carestream Radiology interface
- Familiarized self with coding and set up guidelines in use by in house group
 |
|
877.303.3377
The services provided by Orchestrate Healthcare will
allow us to meet the interfacing and data migration deadlines required
on a very large and critical implementation project.