My Blog
A short description about your blog
- Assisted with Medicity integration backlog management.
- Worked on Medicity client grid setup, opt out options for subscribers, fielded data output questions.
- Performed testing on ODM data flow through the Medicity Grid.
- Prepared the systems for a Medicity CERT deployment on Wednesday.
- Centura Issues resolution handled via Medicity Grid.
- Ran approximately 700 ADT and 200 Rad messages from Medicity Prod to cert. Documentation and triage of issues as well as troubleshooting of issues with QA.
- Completed PM 101 training with client; reviewed all PM gate documentation that is expected for each project
- Scheduled 3 hours with project member on 5/10 to complete an abbreviated EPM training class
- established EPM connectivity to MS Project Pro and oriented to client’s MS Project Server project portfolio, timesheet functionality, and project websites for Reference Lab, e-Prescribing, Rad ClinDoc
- Quest & LabCorp Reference Lab Interfaces Project
- simplified Sharepoint website
- started new project timeline
- participated in physician meeting where two major decisions were reached; created decision log for project website and added physician decisions to the log
- reviewed all existing timelines and all other PM gate documentation
- Project is ‘on hold’ until contracts are complete
- My determination is that project is currently in the clients“Planning” phase and will assist to finalize project scope.
- Radiology Clinical Documentation Project:
- simplified Sharepoint website
- reviewed existing timelines and all other PM gate documentation
- sedation documentation detail is the only piece of the project that has been worked on extensively with the ASAP team since sedation is going live with ASAP in the next few months.
- e-Prescribing Project:
- This project is scheduled to go-live in the next month. Assisted with training and project management to ensure timeline success. Attended certification call with Surescripts, which will determine the feasibility of it’s golive date. Other than my current duties, working with the client and adding my assistance where needed to help meet a successful go-live during the project timeline.
- Radiology Build is 90% complete. Now waiting on Vendor and Epic to finish their changes to test.
- Connected the new Carestream routes to input and output routes.
- ADT messages process from input all the way to tcp client outgoing. Test system not ready to receive.
- Order messages process from input all the way to outgoing but test system not ready to receive.
- Scheduling messages process from input all way to outgoing but test system not ready to receive. These will have some tweaks required once Carestream gets their test system set up.
- Route for physician updates is completed but EPIC does not have their output piece built yet. Waiting on EPIC.
- Update of charge logic completed and processing to EPIC and stripping off the MRN for IDX is complete.
- Results and Order modification route processes messages from start to finish properly.
- Took over all radiology calls for the duration
- Mentored two other team members in Rhapsody.
- Set up a weekly interface call for Carestream Interfacing.
- Started work on ScottCare TeleRehab Advantage intersystem.
- Meditech ORU & ORM interfaces deployed to test.
- Designed, coded & deployed custom Ensemble service to auto-update NPI table instead of current manual process.
- Finished Rhapsody testing of client’s Imaging Interfaces.
- Was assigned new Rhapsody interfaces to test. Began preparing Test Scripts and testing.
- Created folder of 25 MDM HL7 messages for Doctors practice.
- Created folder of 50 MDM Hl7 messages for Family practice.
- Conversion for eMDS Lab Results Interface initial planning meeting – Coordinated and scheduled meeting with Physician Practice along with eMDS vendor representative. Hosted the meeting on Tuesday 5/3 after providing an agenda and supporting documentation for the meeting.
- Physician EMR Interface project kick-off call – Attended meeting on Tuesday 5/3 to discuss this project. The meeting went well, but due to the ambitious nature of representative’s plans (wants to place orders in Meditech via HL7 interface inbound to Meditech), decided to request a second meeting with additional team member participation and guidance this time around.
- e*Gate Update 2 Project – Worked to obtain remote desktop access to the lap top that was recently updated to install a virtual machine (VMWare). The machine already has the current version of e*Gate installed, so designated the virtual machine for the e*Gate Update 2 install. Completed installation of the full e*Gate Update 2 suite (Participating, Registry, GUI’s, e*Way Addons and ETD Addons) to the virtual machine. Subsequently, completed a series of e*Gate build tasks (created e*Way configuration, created e*Way Connection configuration, created collaboration, etc.) against the “Epic_Test” schema on registry AEGT11T:3700 and did not experience any issues. Early returns are showing the virtual machine strategy to be a fully functional and extremely convenient solution to supporting both e*Gate environments from a single lap top.
- Conversion for eMDS Lab Results Interface – Worked identify the Excel spreadsheets that document all lab test/result mnemonic changes for the client conversion. Created streamlined versions of these spreadsheets to isolate just the department, mnemonic and description for each Meditech laboratory dictionary entry. Shared the streamlined documents with team members for additional review and discussion. Discussed at length the impacts of these changes (OBR.4 and OBX.3 in the HL7 ORU message) on the eMDS interface. Ultimately, discovered that the eMDS interface will accept and store the new values without any issues. Identified that the “linking” tool on the eMDS side will require some changes once the new HL7 messages and associated lab test/result codes will be received by eMDS in an un-linked state. Integration team member identified to handle this re-linking from 7/1 on as new messages are filed into eMDS.
- Mapped out the changes necessary to support lab results from the new Meditech C/S environment to the eMDS system. The routing and transformation rules changes were: MSH fields used to verify that a given ORU message is from Meditech (as opposed to Alverno), OBR mapping for the accession number, addition of provider checking for the repeating OBR.28 (Copy To) field, modifications to data map and code to support the provider mnemonic change for specific physician practice (PERMI3 to PERMI03). Subsequently, pulled the transaction archives for lab results from DJ.TEST and pushed them through the newly updated interface code to ensure that all routing/transformation rule changes functioned as intended. All tests were ultimately successful, but required some re-work along the way. Once the changes were complete and tested, worked to identify the test patient that we needed. I registered this patient in DJ.TEST, then used the resulting ADT’s PID and PV1 segments to create a set of test messages to be used for next week’s integrated testing after pulling some specific lab result ORU messages from the DJ.TEST archives. Modified these ORU messages to use the test patient PID and PV1 segments and also modified key fields in the PV1 and OBR to point to Dr. Dayhoff’s Meditech provider mnemonic.
- Support for resolution of Lab Mnemonic data map file issue – Received some less than promising feedback from Oracle regarding the data map file issue that we were experiencing. Decided to set up some code to “validate” the data map and ultimately found that the data map file contained 2 records that contained non 7-bit ASCII printable characters. Fixed the 2 records and provided the updated data map file to the client. Received an additional request to “validate” a couple more data map files. Subsequently, set up a simple e*Gate collaboration based utility that reads the data map files one record at a time, checking for characters that are not 7-bit ASCII. Was able to fix a similar issue with the new file that Jan provided and will use this utility in the future if these sort of issues are encountered. Closed the Oracle service request once I confirmed that the issue Jan was experiencing was resolved.
- Support for Physician interface go-live – Worked with Physician to add a “TXA” HL7 segment to the outbound structure for his interface. Worked step by step through the method of using the SSC Wizard to add the new segment to a cloned version of the original ETD that was being used for both input and output.
- Datanex DRA SFTP interface – Supported a couple days of manual SFTP transfers to/from Sentry this week as needed per email requests.
- Participated in Epic Integration Team Meeting
- Made progress on ADT from EPIC to Impac Mosaiq Radiological Oncology System Route.
- Began unit testing Technical Charges interface from Impac Mosaiq Radiological Oncology system to Epic .
- Thoroughly reviewed all documentation available on the NYSIIS Immunization Registry interface.
- Crafted email to NYSIIS contact as to status of initial test file results. Assigned additional interfaces:
- EPIC to/from MedSelect Rx Drug Dispensing System
- ADT FROM EPIC TO MedSelect
- Pharmacy Orders FROM EPIC to MedSelect
- Charges FROM MedSelect to EPIC
- Physician Credentialing system
- Staff Master File Interface to EPIC
- RHIO interfaces
- Results FROM EPIC to Client RHIO
- Orders FROM EPIC to Client RHIO
- ADT FROM EPIC to Client RHIO
- Medicity Project Management correspondence with client regarding remote access and status of pipeline priority list.
- Received training from team member via TeamViewer on creating Interface Test Cases from code in DataGate messages. He provided a sample Rhapsody Test Plan and messages, working through code to develop test case.
- RIS Charges mapping and routing completed.
- RIS ADT mapping and routing completed.
- RIS Scheduling mapping and route completed
- Developed a plan for handling charge files with Brian on site to minimize changes other systems will be required to make.
- Completed and tested the Charge file processing with the current file layout. Carestream will add an MRN column which is required for EPIC.
- Added a process to take the new file and strip out the MRN column and save so the old IDX system will not have to be altered to accept the new column.
- Completed ADT route and mappings. Discovered some issues with ADT^A18 merge messages and the ADT^A45 message has to become an ADT^A18 which then leads to the issues the system appears to have accepting A18s.
- Started looking at the specs and requirements for the following interfaces:
- Wittbio Cath Lab
- Safety Surveillor Infectious Disease control system
- Clinipro Diabetic Monitoring system
- Scottcare TeleRehab
- Worked on trouble shooting some save and restore issues in Rhapsody.
- Worked on some lookup table issues in Rhapsody.
- Provided Rhapsody oversight for one of the new team members.
- Prep for Medicity cert deployment.
- Reconciling all Medicity QA, Cert and Prod packages to schedule weekly deployments.
- Analysis of CORHIO QA/Cert/Prod packages.
- Cert deployment, successful. One defect remains open for the client DB Parser, which was resolved later in the week.
- Attended Epic Integration Team Meeting
- Made progress on ADT from EPIC to Impac Mosaiq Radiological Oncology System Route .
- Made progress on Technical Charges interface from Impac Mosaiq Radiological Oncology system to Epic .
- Thoroughly reviewed all documentation available on the Immunization Registry interface.
- Completed SCM registration/update test plan build.
- Assist with provider load from Standish/Tawas into SCM.
- Interfaces built for Epic Inbound Testing:
- Muse DFT Charges to Epic
- SiemansRMS DFT Charges to Epic
- Documentation
- EPIC/Rhapsody Project Peer review
- Rhapsody testing
- Mapping and Design requirements
- Epic Radiology Results Testing Session meeting
- Epic Sunquest Results Testing Session meeting
- Epic Weekly Interface Team meeting
- Epic Integration Project Plan issues Meeting
- Radiology Interface Vrad Team Meeting
- Tested Route ADT from Star HLO
- Built Route to handle ORU results from Vrad to Mckesson Star
- Conversion for eMDS Lab Results Interface – Met with client to discuss the interface which they developed a while back and continues to maintain over time. Pulled the production copies of all ETDs and Collaboration Rules and moved them into place in the TEST environment on AEGT03. On AEGT03, completed changes to the collaboration and collaboration rules in order to synchronize the test modules on AEGT03 with the production modules.
- Conversion for eMDS Lab Results Interface – Without changing the actual collaboration rule code added detailed comments for each business rule within the two key collaboration rules “crMTC_RTR_DAYHFV6.class” (Routing) and “crPhysician_ORUv2.class” (Transformation) for the Meditech Lab Results interface to eMDS for TMG. Using the detailed comments added to the code, created document to list all key routing and transformation rules that may require changes for the conversion from Magic to C/S for the Lab Results interface. Subsequently, pulled a few days worth of production data and pushed it through the interface modules on AEGT03. Also, worked with the client to identify the Excel spreadsheets on the X: drive that document the current (Magic) vs. new (C/S) lab test/result mnemonics and descriptions which I will share with TMG’s eMDS team after tailoring it to the interface impacts for lab test mnemonics (OBR.4) and lab result mnemonics (OBX.3).
- Conversion for eMDS Lab Results Interface –Was provided a custom version of the Conversion interface questionnaire and I sent that questionnaire to the physician requesting that he review/respond to the questions and also to get things rolling for the initial conference call. Received feedback from various team members and subsequently requested availability for initial conference call and was able to schedule a call for Tuesday 5/3 at 1:00PM. Included on the call will be a representative from EMR vendor eMDS as well as client representative for the eMDS system.
- DRA SFTP interface for client site – Was finally able to test the ”get” collaboration for this interface once the first production ”dra_complete” claims file was made available on the Sentry SFTP server. Worked with colient to confirm that I should copy it to the NEBO server in the agreed upon NEBO folder and once I was given the go ahead, ran the “get” collaboration and it successfully completed all steps to “get” the file from the Sentry SFTP server and copy it to the designated NEBO folder. Later in the week, completed a series of manual runs for both the “put” and “get” steps. Currently waiting for confirmation from client before setting the day forward e*Way schedule for this interface. The client prefers manual runs of the interface until issues with NEBO processing are worked out and implemented. Also, completed a change to ensure that empty files are NOT sent to Sentry for the “put” collaboration. I made this change when I discovered that the Meditech claims file deliver process sometimes delivers empty files which should not be sent to Sentry.
- Support for Physician interface go-live – Worked with provider contact to identify issue with the HL7 message exchanged with physician office’s lab results interface. Identified via log file research that the outbound HL7 e*Way was reporting an MLLP rules violation (EOD character not received) perpetrated by the downstream’s system’s HL7 inbound server/listener.
- Support Lab Mnemonic datamap file issue – Received request from client to research issue they were experiencing with an e*Gate datamap file. At first glance, could not identify any issues with the file, so opened Service Request with Oracle support describing the issue and attaching the associated datamap file.
- Scheduled and held status call for Project RED interfaces on Thursday 4/21. Talked with team members at length before the call. Based on their research, it is clear that Project RED requirements call for a “Discharge Medication List” and that the Pharmacy Orders HL7 interface will not provide that data. Identified that the discharge medication list is collected via the OAM/RXM application modules within Meditech and there is no HL7 interface available for that module at this time. We are however scheduled to proceed with the implementation of the ADT HL7 interface for all ministries expect PSMH which will not be turned on until after the conversion go live scheduled for 7/1.
- VendorFTP schema FTP interfaces. Completed renaming of Multi-mode e*Way modules within this schema to use the “ewBatch” naming convention for Datanex, WealthEngine and Medmined e*Ways. Documented the collaboration-level schedule for all collaborations within the above e*Ways. Subsequently, defined e*Way start/stop schedules for each e*Way to ensure e*Way up-time coverage for the collaboration-level execution schedule. This coming week, will incorporate the e*Way and collaboration level schedule settings into the Requirements document for each of the above interfaces for Datanex, WealthEngine and Medmined.
- Wealth Engine SFTP. On Monday 4/18, identified that both Batch e*Ways for Wealth Engine could not connect to the Wealth Engine SFTP server. Notified Wealth Engine who subsequently resolved the issue and requested that I re-send the last two days files. Completed the re-sends after the connection issue was resolved.
- Wealth Engine SFTP. Worked at length to get this interface working in both directions by the end of the week. Identified the fact that first two Meditech extract files were empty and communicated this. This issue was resolved and subsequently we SFTP’ed that file to Wealth Engine. Once the initial file was delivered, we had trouble getting the return file back from Wealth Engine. These issues were resolved on the Wealth Engine side. Once that issue was resolved, successfully retrieved via SFTP the first return file from Wealth Engine and confirmed that e*Gate was able to copy the file to the Y drive network folder. This completes the work to bring Wealth Engine live.
- Datanex NEBO “ub_04” FTP interface . On Monday 4/18, identified issue with the NEBO server to e*Gate server (AEGT19) SyncCopy scheduled task. In short, it stopped copying new “ub_04” claim files to AEGT19 around 3/18. Notified System Admin for NEBO server of the issue and he quickly resolved the issue. All “ub_04” claim files forms from 3/18 forward were copied over via SyncCopy and subsequently processed by e*Gate and FTP’ed to Datanex as part of normal processing which is designed/coded to handle multiple files each day in case things get backed as they did this time when the SyncCopy scheduled task was inadvertently disabled on the NEBO server.
- ResponderNet ADT interface support (3 hours) – Received request to help create and use a new ETD to allow the delivery of an ADT^A18 (Account Number merge) in the format required by the ResponderNet application’s inbound ADT interface. In short, they needed to send the PV1 segment “after” the MRG segment for the A18 and a new ETD was required to make this possible. We created the new ETD using Web-ex session to allow them to see the process of using the SSC Wizard to create custom HL7 ETD’s and subsequently, we completed the collaboration rule changes and recompile to support the A18.
- EHR Meaningful Use Requirements Analysis for client e*Gate SRE and JCAPS. Downloaded the “45 CFR Part 170” document from the ONC web site http://healthit.hhs.gov and began reviewing the detailed list of Meaningful Use Stage 1 requirements included in the document. The goal is to identify those MU requirements that are relevant to the health care industry’s use of HL7 Interface Engine software. Based on that, provide an assessment of e*Gate SRE’s and JCAPS capabilities with regards to meeting the MU requirements (e.g. One MU requirement involves using the CCD/CCR standards (HL7 v3 based standards) to transmit and receive patient clinical data documents (medications list, allergy list, problem list, etc..) and JCAPS is the clear choice because of its more robust and advanced tools for building interfaces that must encode/send and decode/receive) “XML Schema based” CCD/CCR documents).
- e*Gate Update 2. Completed work on the first draft of the e*Gate SRE Update 2 installation step/notes document and sent this document out to the team along with a status email on the implementation of e*Gate Update 2. Also, worked to confirm that 32-bit applications are “enabled” on the ACN016/ACN016 Windows Server 2008 R2 servers. Added (via “regedit”) the necessary Windows Service definitions to allow the AEGT11T registry to run on the ACN016 node and to allow the AEGT12T registry to run on the ACN015 node in the event of failovers which automatically moves logical server/drives after re-boots and failures for a given node.
- Developed 4 Rhapsody ADT Routes – Epic ADT Implementation
- Started 4 ADT Rhapsody Maps – Epic ADT Implementation
- Developed 2 Rhapsody Charge Routes – Epic ADT Implementation
- Started 2 Charge Rhapsody Maps – Epic ADT Implementation
- Started Research on 2 Eligibility Routes and Maps
- St. Lukes Rhapsody Datagate Conversion:
- Route and Documentation Review Datagate Interfaces, Naming conventions, Site layout, requirements (hr)
- Datagate to Rhapsody migration (1hr)
- Integration Team meeting - Tues (1hr)
- Interfaces built for Epic Inbound Testing including Muse ORU Results to Epic, Xcelera ORU Results to Epic, CoPath ORU Results to Epic, SiemansRMS ORU Reports to Epic including documentation.
- Rhapsody testing.
- Mapping and Design requirements
- Epic Radiology Results Testing Session meeting
- Epic Sunquest Results Testing Session meeting
- Epic Weekly Interface Team meeting (0hr)
- Build Message Definition to handle ORU messages per sample messages
- Waiting on Epic to add Provider Names/codes Lab Codes and Radiology Report Types
- Competed Sunrise Radiology configuration and administration training.
- Development of ePI test plans
- 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
- Rhapsody Datagate Conversion, Route and Documentation Review Datagate Interfaces, Naming conventions, Site layout, requirements, Rhapsody testing.
- EPIC review of Invision ADT Route, Sunquest Lab Route, including Documentation review, Mapping and Design requirements and Epic Interface Task meeting
- Reviewed Surescripts build items, worked complete Epic’s Surescripts Connectivity Questionnaire.
- Worked to setup Ingenix connections.
- Worked on Outgoing Integration Interface. Tried to get to look at other installations of this interface to Meditech. Began review of outgoing RTF file and how it could be converted to plain text for Meditech;
- Continued pursuing the evasive Quest interface specs.
- Waiting for any go-ahead and specs for Incoming & Outgoing Quest Lab Interfaces;
- Waiting for application team to advance 13 SureScipts interfaces I have completed the Integration Building Blocks for;
- Waiting on Epic and RTF to TXT conversion technology review to advance documentation interface.
- Datanex. Attended weekly status meeting for this project on Tuesday 4/5.
- MCHIE. Attended initial project planning meeting with MCHIE representatives and client team.
- Datanex SFTP for DRA Tool. Worked with the project team after some confusion over the content of the first extract file to finally deliver the first file with production Medicaid outpatient claims to the Datanex SFTP server via the e*Gate automated ”psftp” interface. Currently waiting on Datanex to make available the first DRA’ed claims file in order to run the second “get” step of the e*Gate interface for Datanex.
- Wealth Engine SFTP. Completed production implementation of the e*Gate interface code to “VendorFTP” schema (AEGT19). Received new Wealth Engine SFTP server credentials and updated the newly established “psftp” .BAT scripts to use the new credentials. Completed successful run of the first part of the interface which “puts” a file to Wealth Engine. Currently waiting on word on when we will receive the first return file from Wealth Engine so that we can run the “get” piece of the e*Gate code to retrieve the file from the Wealth Engine SFTP server.
- Completed detailed review of two Project RED application specification documents and sample “After Hospital Care Plan” document. Created first draft of the Project RED interface requirements document including excerpts from the Project RED HL7 interface specifications document and Meditech HL7 interface specifications document where appropriate. Compiled list of questions using the client integration team standard template along with additional questions specific to the proposed Project RED interface implementation. Included this list of questions in the first draft and then sent these same questions to management for review and feedback on the next call.
- AEGT11 Registry Service Issue. Researched GUI client connectivity issues with the production AEGT11 registry after initial signs seemed to point to the installation of the Update 2 registry (AEGT11T – listener port 3000) on ACN015. Per request from the team, shutdown and removed Resources defined to ACN015 for the Update 2 Registry and two Epic_Test schema control brokers then updated (via “regedit”) the listener port to NOT use port 3000. Subsequently directed my attention to investigating the AEGT11 registry issues in the live environment. Identified that the “-mc” maximum connections parameter was set to “1024” for the AEGT11 registry service start up script. Identified that the aggregate number of e*Gate modules (BOB/eWay/IQ Manager) defined for the e*Gate schemas within the AEGT11 registry was approximately 1000 modules. e*Gate System Administration Guide research told me that the registry accumulates client connections from users (GUI sessions – Designer/Manager) and from e*Gate modules when they are “started”. Worked with Lori to update the “-mc” parameter from 1024 to 2048 on Wednesday morning 4/6 and to shutdown/restart the AEGT11 registry service without having to re-boot the server itself. Since that time, no issues with GUI connectivity have been experienced by e*Gate users. Based on these events, it is reasonable to assume that the AEGT11 registry service re-stabilized because it was now configured to allow > 1024 client connections and that the “-mc” threshold was exceeded on around 4/1 when the new “CS_SouthernRegion” schema’s modules were “started” for the conversion.
- e*Gate Update 2. Opened service request with Oracle support per the “rawInput()” call issue that is listed in the Known Issues list from the Update 2 Readme.txt file. In short, the service request was a request for additional information regarding the actual impact of using “rawInput()” in collaborations with regard to the reduction of the memory footprint for these collaborations. The feedback told us what we needed to know which is that these collaborations will continue to function properly if we choose not to address each with the addition of “saveInboundImage()” call within “userInitialize”, but they that the memory footprint will be larger than it needs to be without it. Clearly, we should implement the changes as part of the Update 2 installation if we want to follow the vendor recommendations understanding that this change is solely about reducing memory footprint/usage for e*Gate collaborations within the Update 2 environment.
- MCHIE Project. Pulled the documentation from the Illinois HIE web site and received documentation from the MCHIE team. Began development of the initial draft of the client Interface Requirements based on these documents and from information gathered on the initial project kick-off call with MCHIE and client representatives.
- ProAccess 5.3 PROD interface deployment: worked with Medicity & the cleint on activating PROD interfaces for HIE Pilot, testing & validation of data in PROD environment, additional planning of data for Pilot.
- CERT Testing & Issue Resolution: assisted Medicity in researching testing issues in CERT environment with the client application teams, assisted with prioritizing testing & product issues, performed re-testing after CERT deployments to confirm testing & product issues were resolved.
- Documentation: tracking of 5.3 CERT & PROD issues/updates/resolutions during testing & retesting on HIE SharePoint for the client and in Rally for Medicity.
- Project Management related reporting and correspondence with Medicity for HIE project. Review with the client and Medicity of project deliverables, updated Pilot scope & timelines, and updated PROD interface deployment timelines. Submitted client remote access forms for Orchestrate Consultants.
- NPR Extract Conversion. Completed final change to the e*Gate code for this interface to remove support for Charge Categories and CPT Codes (ZDG.1, ZDG.2 and ZDG.4). Subsequently, supported final round of integrated testing which was successful. On Wednesday 3/30 completed build/implementation of the e*Gate code in the production environment in advance of the conversion go-live on 4/1.
- State ELR Conversion. Completed changes in production for e*Gate module “bobSOI_ELR_TRX” to add new subscription for LAB results messages and modified the collaboration rules to support routing the messages within the ELR HL7 daily batch file.
- e*Gate Update Two. Completed the e*Gate SRE v.5.0.5 Update 2 installation for ACN015. Installed pre-requisite JDK 1.6.0_19 on the ACN015 C: drive. Installed registry host, participating host and GUI’s to logical server AEGT11T F: drive. The first attempt to install the software was unsuccessful due to an insufficient allocation of disk space for the logical drives (1.0 GB for each drive). As it turns out, the full installation of the e*Gate software required 1.2 GB of disk space. Subsequently, worked to allocate additional space (5.0 GB for drives targeted for just participating host and 10.0 GB for drives targeted for the complete install – Reg, Part and GUI’s) for each of the drives. Second attempt to install the software to ACN015 was successful since space issues were resolved.
- e*Gate Update Two. Completed steps to copy of the “Test” schema (via .rdb file and repository directory direct copy) from AEGT023 to AEGT11T. Renamed the schema, created user accounts for all members of the team, committed/promoted datamap files from current environment’s “default” schema to new enviroment’s “default” schema, renamed and updated hostname for schema’s participating host to be AEGT11T, updated “Run As User” parameter for each defined e*Gate module, updated DB path parameter for each JMS IQ Manager to point to the F: drive (instead of O: drive for current environment) and updated host name to point to AEGT11T for each JMS e*Way Connection.
- e*Gate Update Two. Built temporary BOB (copied from existing Meditech to Epic RAD Results transformation/routing BOB) that uses call to “rawInput()” since the original BOB did not include code that calls “rawInput()”. Recompiled the Java ETD’s that it uses to unmarshal/marshal HL7 RAD Results messages aqnd recompiled the collaboration rules (in order to compile each against JDK v1.6.0_19). Ran a test message through the BOB and the message was processed successfully and the “rawInput()” call successfully retrieved and logged the payload of the message. Need to open an issue with Oracle to understand better why the documentation states that all collaboration rules that use “rawInput()” must be updated to call “enableSaveInboundImage()”.
- e*Gate Update Two. Completed creation of the cluster resources for the AEGT11T registry, “Epic_Test” control broker and “Epic_Elgin_Test” control broker using the Failover Cluster Manager for Windows Server 2008 R2. Copied control broker start-up scripts from AEGT023 and modified them to accommodate the new Update 2 environment. Successfully tested stopping/starting the registry using the new Resource and used the new control broker resources to start/stop the control brokers for the testing I completed for the “rawInput()” issue. Use disaster recovery documentation as my guide for determining the proper Resource configuration settings for each component.
- e*Gate Update Two. Opened issue with Oracle support to see if it is even possible to install two different versions of the e*Gate GUI’s (Designer and Manager) on the same workstation. Received immediate feedback that clearly stated (and even pointed to FAQ that directly addresses this very question) that it is not possible to install both e*Gate SRE v5.0.5 GUI’s and e*Gate SRE v5.0.5 Update 2 GUI’s on the same workstation. Plan is to move forward with the approach of configuring a lap to use logical partitions (two of them) so that the current version of e*Gate can be installed on one partition and the Update 2 version can be installed on the second partition.
- Rhapsody Datagate Conversion. Route and Documentation Review Datagate Interfaces, Naming conventions, Site layout, requirements
- Rhapsody testing
- Epic Integration Implementation Activities including Documentation review, Mapping and Design requirements, Epic and Medical Imaging meeting as well as the Epic and Cardiology Meeting
- Attended Epic Team meetings Weds, and Thurs;
- Completed the “Building Blocks interface build for all of the Surescript interfaces;
- Struggled with Epic and worked through the Epic Print Services issues and all known problems for the Outgoing Documentation Interface. Now sending documents to Meditech;
- Reviewed the Quest Interfaces with client. Unable to build until Quest is signed.
- Waiting for any contract signing and go-ahead on Incoming & Outgoing Quest Lab Interfaces;
- ProAccess 5.3 PROD interface deployment: worked with Medicity & client on activating PROD interfaces for HIE Pilot, testing & validation of data in PROD environment, additional planning of data for Pilot.
- CERT Testing & Issue Resolution: assisted Medicity in researching testing issues in CERT environment with client application teams, assisted with prioritizing testing & product issues, performed re-testing after CERT deployments to confirm testing & product issues were resolved.
- Documentation: tracking of 5.3 CERT issues/updates/resolutions during testing & retesting on HIE SharePoint for the client and in Rally for Medicity.
- Project Management related reporting and correspondence with Medicity for HIE project. Review with the client and Medicity of project deliverables, updated Pilot scope & timelines, and updated PROD interface deployment timelines.
- Client Code set overview call
- Planning for sending rest of prod messages to cert
- Medicity Issue log management
- Removed ADT errors from queue
- Review UAT communication plan with client.
- Chaired Interface analysis discussion
- Worked on Medicity Cert Deployment bug fix
- Completed sending Prod messages through Client Cert
- Client Nexus Failure review and testing of PA
- Researched all submitted client medicity issues and added to list
- Organized and attended HL7 interface discussion meeting multiple project leads on Friday 3/25.
- e*Gate Update Two. Using e*Gate collaboration rule code completed last week that identifies active vs. inactive collaboration rules in a given schema, created new e*Gate collaboration rule component that removes inactive collaboration rule class files from a given schema’s export .CTL file.
- e*Gate Update Two. Using e*Gate collaboration rule code completed last week that identifies active vs. inactive collaboration rules in a given schema, created new e*Gate collaboration rule component that removes inactive collaboration rule artifacts from a given schema’s export .EXP file. Used in conjunction with the corresponding .CTL file processor my intention is to use this utility to trim down the list of collaboration rules that are defined to a given schema to just those collaboration rules that are “active”. This should significantly reduce the amount of lag time it takes to open the e*Gate Schema Designer and Manager especially for larger schemas like CS and PACS that have a tremendous amount of “inactive” collaboration rules. My intention is to use this utility to trim schemas on their way from the current e*Gate SRE environment to the new e*Gate SRE Update 2 environment.
- e*Gate Update Two. Worked to get prepared for the e*Gate Update Two installation to ACN015/ACN016 next week. Answered some questions regarding Windows OS version (Windows Server 2008 R2) and Java version requirements (JDK 1.6.0_19) for e*Gate Update Two. Also, worked to set up an Oracle support account for me to use for mining the knowledge base and for creating support tickets if necessary in the future. Also, provided final document that represents the output of my analysis of the “Known Issues” for e*Gate Update Two to the team.
- NPR Extract . Supported testing of the interface this week and researched a couple issues regarding the processing of Charge Categories and CPT codes from the NPR Extract file to the Midas BAR message.
- State Lab Reporting. Per request via email from the client, researched the issue of PID.13 (Patient Home Phone) and PID.14 (Patent Business Phone) being empty/null for LAB result messages for the Meditech Client/Server based ministries. Ultimately found that for the Client/Server sites, this data is present on ADT messages (so it is collected in Meditech ADM) but not present in LAB result messages. Pulled this research together into an email and sent it off stating that we could request a Meditech custom to add PID.13 and PID.14 to the Lab result messages if this is considered an important/critical issue. As of today (Wednesday 3/30), have not heard back concerning this issue.
- Charge file processing support. Worked to identify formatting issue with “charge” files. Found that for the files being used to try and re-send charges that the HL7 segments were terminated with Hex “0D0A” instead of just Hex “0D”. Fixed the charge file he was working with to replace all “0D0A” with “0D” and returned that file to the client, which he then used to re-send charges per an issue he had while on call.
- ProAccess 5.3 CERT environment deployment: worked with Medicity & client on updates and hot fixes to 5.3 CERT, prioritizing testing & product issues, and with retesting following CERT deployments.
- CERT Testing: assisted Medicity in researching issues in CERT environment with client application teams, assisted with performing re-testing after deployments to confirm testing & product issues were resolved.
- Documentation: updated ProAccess Codeset Maintenance Policy, created CHS ProAccess Medication History and CHS ProAccess Patient Search documentation, tracking of 5.3 CERT issues/updates/resolutions during testing & retesting on HIE SharePoint for CHS and in Rally for Medicity.
- Project Management related reporting and correspondence with Medicity for HIE project. Review with client and Medicity of project deliverables, scope of Pilot, and updated timelines.
- Continued work on ADT registration/updates test plan to ePI.
- Assistance with troubleshooting of ordering providers not filing to Sunrise Clinical Manager, to resolution.
- Analyzed and re-sent charges that failed in Eclipsys.
- Create troubleshooting documentation for Natus sleep studies.
- Continued testing of orders to Natus.
- Daily assistance creating reports to help reconcile orders sent to GE PACS.
- Assistance testing new reports from Muse.
- Attended ePrescribe Kickoff Tuesday. Reviewed building blocks, record list, task list for implementation, Epic’s online documentation, and all other documentation. Downloaded the Epic Guides & manuals for implementation.
- Debugged the Outgoing Documentation Interface, changing System Definition items, added reports to the lists, sent several messages, am stopped now waiting for Epic to fix EPS parameters;
- Waiting for any go-ahead on Incoming & Outgoing Quest Lab Interfaces;
- Waiting for Epic on 13 SureScipts interfaces I have been assigned and have begun documentation and guide/manual review;
- Waiting on Epic to complete EPS parameters to continue work.
- Rhapsody Datagate Conversion. Route and Documentation Review Datagate Interfaces, Naming conventions, Site layout.
- Rhapsody Route testing.
- Centura code sets delivered
- Conducted Micro Interface call
- Championed Aetna Compliance Session
- Medicity Cert Package Preparation
- Patient Merge call with Client.
- Client cert issues list completed and sent to Administration for review.
- Client Cert package deployment with verification.
- e*Gate Update Two. Completed work building and testing the e*Gate BOB/Collaboration based utility for reading through all collaboration rule class’ .java source files in the e*Gate production registry’s collaboration rules “runtime directory to identify the list of collaboration rules that use the “rawInput()” method call. Added feature this week to use the .exp file generated from a schema export to identify “active” vs. “inactive” collaboration rule class files. This allows the utility to focus only on “active” collaboration rule class files which are the only ones that absolutely must be fixed at the time of the e*Gate Update 2 upgrade/conversion. Also, set up the bulk of the code within a local “custom” method which then allows for easy expansion of the scope of the utility to include additional schemas. There are approximately 15-10 schemas that need to be analyzed for the “rawInput()” method call. This is the method call that has been identified as requiring changes once the move is made to e*Gate Update Two.
- CPACS Vascular Reporting. Early in the week, researched production log files and associated HL7 message traffic and found 2 tables that were not accounted for during testing. These tables each included rows that exceeded the 77 character limit for eliminating the wrapping that makes table data appear unreadable within Meditech. Added code to support the additional 2 tables, tested it in the e*Gate TEST environment for PACS, then implemented the new code in the production environment.
- Datanex for DRA tool implementation. Based on information gathered at the status meeting, the file exchange requirements were reduced from a 3-step put/get/put to a 2-step put/get. Subsequently, modified the module to remove support (collaboration) for the third step (put). Also, worked out the specifics for where (e*Gate AEGT19 path) to have Meditech write the claim file containing claim files for Medicaid outpatient visits. Also, received the path for dropping off the DRA’ed claim files returned from Datanex via the SFTP “get” step. Used the e*Gate user account “ACL005-ADMIN” on ACN010 account to confirm that the account has necessary permissions for writing the file. Currently waiting on word that the first test claim file was generated and placed in the target directory on AEGT19.
- Wealth Engine SFTP. Performed initial research and discovery in the initiation for the implementation of the SFTP for WealthEngine. Confirmed that a formal submission of the “template” for the extract file is required by their new site implementation process to fulfill administrative requirements. Also, worked to have the permissions updated for the drop off directory on the Y drive to grant the e*Gate user account “ACL005-ADMIN” on ACN010 write permission on the target directory.
- NPR Extract . Supported integrated testing that was completed late in the week after completing a successful dry run test with a production NPR extract file. 3 test abstracts were completed in Meditech, the extract file was generated and delivered to e*Gate. e*Gate successfully processed all 3 transactions and all 3 were filed without errors into Meditech. Currently waiting on word that the abstracts look good Midas and that all DX//Procedure/Provider, etc.. data looks good in Midas for all 3 abstracts.
- Reviewed the Rhapsody Route Configurations and map designs.
- Weekly TCon with the client regarding testing strategy.
- Continued documenting data flow diagram for phase1.
- Testing Mapping logic message filtering and conditional logic testing.
- Continued sleep study related orders and reports testing.
- Daily reporting on orders sent to PACS.
- Activation preparation tasks.
- Testing of new EKG Stress Test reports from Agfa PACS.
- Participated in meetings related to the preparation for ePI configuration and testing.
- Assisted with troubleshooting issue where ordering provider not making it to SCM.
- Identity Setup Investigation on the Epic Project.
- Created “DNP client ITM” Background Monitor in POC for Team’s use
- Reviewed Documentation Interface triggers and PV’s. Modified System Variable, Profile Variables, and went through ASAP process triggering messages into the interface.
- Began debugging EPIC Documentation Interface issues.
- Working with Quest contact for Incoming & Outgoing Quest Lab Interfaces & any go ahead on the 13 SureScipts interfaces I have been assigned.
- Medicity operations call for the scheduling of Cert/Prod Interface.
- Identified doubts, establishe codesets and received client sign-off of interface data flow.
- Conducted Cert analysis with the creation of issues log.
- Resolved Transcription message issues that are processed by the Medicity Grid.
- Creation of Medicity Executive Plan to provide a high level overview of project status, goals and current timelines. Well received by HIE board.
- Created Medicity results dropbox at two pilot practice sites.
- Research / Discovery is providing dropbox capabilities via the Medicity GRID to a rehabilitation hospital with partnership to the Local Medical Center.
- Reviewed Rhapsody Route Configurations and map designs.
- Conducted a TCon with the site regarding their Rhapsody design strategy.
- Designed a mapper using the Rhapsody Map Designer to illustrate best practices, while on site.
- Drafted a best practices document for recommendations for the interface project.
- Documented a data flow diagram for the Datagate to Rhapsody Interface project.
- Reviewed Test Scripts for message filtering and conditional logic testing
- Testing pa and Monitoring Nexus.
- Located database parser issue with the Centura code sets.
- Performed a post implementation review with client.
- Managed initial data gathering for analysis by Medicity.
- Participate in meetings to prepare for EPI configuration and testing.
- Created a consolidated ADT testplan for ePI.
- Helped troubleshoot document MLM issues to resolution.
- Created daily reports summarizing orders flowing to PACS.
- Interface testing.
- Created weekly report summarizing un-aliased fields coming from Cerner.
- Attended weekly Datanex status meeting for this project.
- Attended weekly CPACS status meeting for this project.
- CPACS Vascular Reporting – This week was go-live week. Worked to monitor Vascular report HL7 message traffic as it flowed from CPACS to Meditech ITS for both facility locations. There were several issues that needed to be addressed this week. Unfortunately, the production HL7 message formats were NOT in line with the same formats from testing with regard to patient demographic / visit information in the first 20 or so lines of the report. So, had to adjust the code to support the production formatting for the first 20 lines of the report. Also, during the go-live week, had to make several code adjustments based on feedback from the client that were not realized during testing.
- e*Gate Update Two – Began work on building an e*Gate BOB/Collaboration based utility for reading through all collaboration rule class’ .java source files in the e*Gate production registry’s collaboration rules “runtime directory to identify the list of collaboration rules that use the “rawInput()” method call. This is the method call that has been identified as requiring changes once the move is made to e*Gate Update Two. Completed about 50% of the work on this utility. Once the utility is completed, will use the resulting output report to work through all of the collaboration rule classes that need to be modified per the e*Gate Update Two “Known Issues” list.
- Conversion for Transolutions – Received email with questions regarding the cutover from Magic to CS for the Transolutions interfaces. Worked to identify the method implemented for handling the cutover for the conversion for Transolutions. The idea is to take traffic from Transolutions, identify those reports that are attached to Magic patients and route those messages to Magic and those reports that are attached to CS patient and route those messages to CS. The plan is to ensure that this same code is implemented for the second facility conversion.
- For Medicity ProAccess 5.3 CERT environment deployment, I worked with Medicity & site on updates and hot fixes to 5.3 CERT, prioritizing testing & product issues, and with retesting following CERT deployments.
- For CERT Testing, I assisted Medicity in researching issues in CERT environment with CHS application teams, assisted with performing re-testing after deployments to confirm testing & product issues were resolved.
- Documented the tracking of 5.3 CERT issues/updates/resolutions during application & integration testing on HIE SharePoint for the site and in Rally for Medicity, maintain Dashboard of CHS CERT Issues for Medicity.
- Project Management related reporting and correspondence with Medicity for CHS HIE project. Review with CHS and Medicity of project deliverables, scope of Pilot, and updated timelines.
- Participated in tours of the radiology departments for the Client at their client facilities and clinics.
- Participated in planning and kickoff activities for the ePI and RIS.
- Reviewing interface specifications and Project Management documentation for RHIO deployment.
- Supporting the Medicity Nexus Product for client.
- Mentoring staff members on Medicity best practice support methodology.
- Worked on the ProAccess 5.3 CERT environment deployment with Medicity & the client on updates and hot fixes to 5.3 CERT, prioritizing testing & product issues, and with retesting following CERT deployments.
- Assisted Medicity with CERT Testing, researching issues in CERT environment with the client application teams, assisted with performing re-testing after deployments to confirm testing & product issues were resolved.
- Created ‘Pilot Practice Fact Sheet’ and ‘Test Issues Dashboard’ for Medicity, tracking of 5.3 CERT issues/updates/resolutions during application & integration testing on HIE SharePoint for client.
- Project Management related reporting and correspondence with Medicity for cleint HIE project. Review with the client and Medicity of project deliverables, scope of Pilot, and updated timelines.
- Helped facilitate the scripting of the Hemo reports, converting them to PDF before moving them to the destination folder.
- Updated Mirth interface code to allow Natus to properly handle order cancels from Cerner.
- Conducted analysis of interface logs, looking for un-aliased fields from Cerner.
- Provided regular reporting of orders going to PACS.
- Testing of reports to Cerner Imaging.
- Supported Activation ADT 3NSMED interface for Lawson Point of Use.
- Assisted with ADT testing and issues resolution
- Begin work on Go-Live integration checklist
- Created New test Node on Medicity Grid to handle practice at remote site.
- Created new users in master user group in Medicity user administrative module.
- Created
- Monitor the BETA environment CENTRAL MPI and Escalate the findings to the concerned.
- Worked on Access manager URL (#) and provided workaround for client.
- Worked with client on adding users as requested by client facilities, but could not complete because the users where seen when imported the specified ldap user group. Waiting on client to comeback on this.
- Checked if Nextgate HL7 Binding component Supports IP Address configuration and provided the feedback,
- Checked for C32 Errors on BETA environment
- Test Plan build started for Rhapsody client.
- Discussions with client to go over best practice with their current Rhapsody deployment. Incorporated Clients needs with hybrid best practice approach to provide the client with a very efficient Rhapsody migration plan off their eGate engine. Client approved. Plan initiated.
- Ensemble client having issues with external client changing their HL7 feed format. Updated their schema to identify the new fields and map appropriately. Working with out issue.
- Assisted in the establishment of a VPN secure connection so Multiple Medicity accounts could transfer their data for technical analysis at Medicity.
- Client scheduled kick-off finalized with implementation of Medicity GRID, ProAccess and Nexus software suites.
- Utilization of eGate documentation to build test plan scenarios.
- Created a Medicity Practice troubleshooting guide that the practice could use in the event they lost connectivity with the GRID.
- Client called requesting an urgent build. Created a file to HL7 production in Ensemble to handle Materials Management data from McKesson to EPIC.
|
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