My Blog
A short description about your blog
- Continued ADT Unit testing and documenting results between Epic EMR and Witt ancillary system
- Continued ADT Unit testing and documenting results between Epic EMR and Xim ancillary system
- Continued ADT Unit testing and documenting results between Epic EMR and Integrated Health Record ancillary system
- Continued ADT Unit testing and documenting results between Epic EMR and IntelliDesk ancillary system
- Continued ADT Unit testing and documenting results between Epic EMR and Pyxis ancillary system
- Performed maintenance and troubleshooting on eManager performance issues that administered designated testing domains.
- Continued ADT Unit testing and documenting results between Epic EMR and Midas ancillary system
- Modified Java Collaboration Definitions in JCAPS 5.1.3 to resolve issues discovered during Interface Unit Testing
- Assisted client Integration Analyst with JCAPS 5.1.3 coding errors in Production environment
- Attended technical kick of meeting for OnBase Enterprise Scanning product.
- Participated in kick off call and began reviewing project related material and following up on initial questions from new client.
- Analysis of Intersystems Ensemble Interface Engine.
- Contacting system administrators of external system to provide connectivity
- Re-establishing the connections
- Looking for invalid records received from partner hospitals and making corrections and resending those records for processing.
- Resolving eGate and JCAPS alerts and fixing the runtime errors.
- Performing enhancements in existing JCAPS interfaces.
- Data files transfers to partner clinics over the weekend.
- Attending conference calls for Epic Change Control and other issues.
- Interface design and development for CAMS project using JCAPS.
- Developing new FTP interface in JCAPS.
- Powerscribe – Completed the e*Gate build and unit testing for the ORU reports interface from Powerscribe to Meditech. Created a new ETD to support the Powerscribe ORU message format. Completed transformation business rules based on the approved Powerscribe Reports interface HL7 specification document and used sample ORU message pulled from the same document for unit testing.
- Transolutions – Continued the ADT backload to Transolutions (from e*Gate TEST server AEGT03) and completed delivery of all ADT messages up to Thursday 4/29.
- Transolutions – Continued the ADT backload to Transolutions (from e*Gate TEST server AEGT029) and completed delivery of all ADT messages up to Thursday 4/29.
- Optivox ADT – Completed integrated test of all ADT message types with direct participation from Optivox.
- Optivox ADT – Completed integrated test of 50% of the ADT message types with direct participation from Optivox and will complete the final 50% of ADT message type testing early next week. Generated all ADT transactions from the Meditech C/S test system for client using 3-4 test patients to cover the list of ADT events required for testing.
- Allscripts – Received email reporting a recurrence of the duplicate report issue on Wednesday 4/28. Using the screen prints provided, tracked down the offending HL7 messages in the e*Gate log files for the reports interface. Discovered for each report that was duplicated in Allscripts, the associated HL7 report message was sent exactly once to the Allscripts server (also ACK’ed exactly once by Allscripts as well). Subsequently sent email to interface support at Allscripts reporting the issue along with my findings with a request for them to research the issue on the Allscripts side. As of Friday close of business, had not heard back from Allscripts.
- Physician Integration (eMDS) – Completed changes and unit testing to the “HL7TcpClientETD” custom e*Way connection code in order to add support for the eMDS specific MLLP envelope that is currently being used for message ACK’s from the eMDS application back to e*Gate. Added configurable parameter “EMDS Acknowledgment Envelope” and completed associated coding changes to support the new configurable parameter. Subsequently, implemented the updated “HL7TcpClientETD” code in the production environment for the eMDS and Fox Valley components that utilize “HL7TcpClientETD”.
- Automate DataGate Documentation - Received Client’s requested fields for report. Working on adding those to current script.
- Research Daily Charge Reports – Looking at automating reporting and validation based upon current script. Waiting on distribution lists and direction.
- Clean Up DataGate Test – Continue working on cleaning up/archiving.
- Clean Up DataGate Production – Coordinated scheduling with client.
- GE/IDX Charges to HealthQuest comm. client change project - Project will be in two phases. Phase I will be a new FTP process for charges (waiting on FTP information). Phase II will be removing the current route for GE/IDX charges to HQ. The port/comm. client will stay in play for other charges HQ receives. Project must be completed by June 8’s 3M coding golive. We would also like to use this opportunity to change the currently existing tcp/ip to HQ for charges from a custom code to a super client configuration.
- Xtend Physician Report Automation – Created a script that greps the interface records from the previous day’s inbound log file and creates a .rtf file which is emailed to the distribution list. Need to move this into a cronjob next week.
- HPF Test Interfaces – Begun initial research into duplicating production HPF interfaces for test. Do we have an HPF admin contact?
- SMS Siemens Radiology Interfaces Overview – Created an excel spreadsheet showing current radiology interfaces.
- Review GE RIS interface documentation – Working on the ADT interface gap analysis documentation. Can we schedule a meeting with ADT stakeholders (GECE/LW and GE RIS) during my next onsite week (May 3) to review?
- Optivox ADT– Completed e*Gate build and unit test (using messages pulled from production with feeders/eaters) of the routing and transformation business rules for the Meditech to Optivox ADT interface. Implemented all routing and transformation business rules based on the completed client interface requirements document for this interface (e.g. routing only IN, INO and ER patient types and suppressing updates for pre-admits and discharged patients).
- Optivox ADT – Successfully tested connectivity to the Optivox HL7 TCP/IP over MLLP server using the e*Gate HL7 e*Way. Also, successfully delivered the first test A01 (Admit) HL7 message to Optivox working directly with Optivox.
- Optivox ADT – Completed e*Gate build and unit test (using messages pulled from production with feeders/eaters) of the routing and transformation business rules for the Meditech to Optivox ADT interface. Implemented all routing and transformation business rules based on the completed Provena interface requirements document for this interface (identical to rules for Optivox ADT for Main Campus Facility).
- Optivox ADT – Attended weekly status meeting and discussed options for integrated testing. The first option being a conference call based integrated test with participation from multiple resources for testing and verification. The second option being a “test go-live” where production data will be routed through the e*Gate test system with daily status checks and data verifications to confirm that Optivox is properly receiving and filing all ADT messages. Representatives from both client locations stated a clear preference for the second option, so will plan on implementing the “test go-live” approach.
- Transolutions – Discovered that most of the collaboration subscription and publication definitions were missing for the e*Gate components for Transolutions Client on AEGT03 after some maintenance issues over the weekend. Redefined the missing collaboration mapping definitions along with the associated collaboration subscription and publication definitions.
- Transolutions – Pulled Meditech ADT message archives for client back to 4/1/10. Using these files, started the ADT backload to Transolutions (from e*Gate TEST server AEGT03) after coordination and scheduling. Completed the backload through Thursday 4/22 and will resume the ADT backload again next week.
- Transolutions – Pulled Meditech ADT historical message archives for PUSMC back to 4/14/10. Using these files, started the ADT backload to Transolutions (from e*Gate TEST server AEGT029) after coordination and scheduling. Completed the backload through Thursday 4/22 and will resume the ADT backload again next week.
- Powerscribe – Began the e*Gate build of the ORU reports interface from Powerscribe to Meditech for client.
- Continued ADT Unit testing and documenting results between Epic EMR and Witt ancillary system
- Continued ADT Unit testing and documenting results between Epic EMR and Xim ancillary system
- Continued ADT Unit testing and documenting results between Epic EMR and Dexter ancillary system
- Continued ADT Unit testing and documenting results between Epic EMR and IntelliDesk ancillary system
- Continued ADT Unit testing and documenting results between Epic EMR and Pyxis ancillary system
- Performed Orders Unit testing and documenting results between Epic EMR and Pinestar ancillary system
- Continued ADT Unit testing and documenting results between Epic EMR and Midas ancillary system
- Performed Initial Field by Field Testing of following coded interfaces
- Flowcasted ADT to EPIC
- Star(HBOC) ADT to EPIC
- SoftLab Orders/results to EPIC
- Softmed Transcription Messages to EPIC
- ImageCast Orders/Results to EPIC.
- Fixed Changes in Engine to incorporate smooth Testing as and when required.
- Gathered communication specifications for external target systems.
- Tested ADT for EPIC system.
- Patient Registered, Updated,Transfered and discharged to trigger events A04,A08,A02,A03.
- Performed unit testing for Cerner Radnet, PMM & PACS systems.
- Coordinated with Unit testing for Unit testing.
- Re-organized the JCD code to make it simple & understandable.
- Configured IP & Port numbers in JCAPS for Receiving systems PACS, Cerner Radnet & PMM.
- Performed analysis on Outbound data with focus on triggered A01, A02,A03,A04,A05,A06,A07,A08,A11,A12,A13,A18, etc.for unit testing.
- Environments utilized: JCAPS 5.1.3, Epic, HL7 2.5, MLA, M2,ONCHOLOGY, PACS, Interface explorer, FTP server, AIX
- Developed Interface ADT Script unit testing toolkit to use while testing with the Pyxis ancillary system
- Performed Interface ADT unit testing between Epic EMR and Pyxis ancillary system
- Developed Interface ADT Script unit testing toolkit to use while testing with the Clinical Workstation ancillary system
- Performed Interface ADT unit testing between Epic EMR and Clinical Workstation ancillary system
- Developed Interface ADT Script unit testing toolkit to use while testing with the Xim ancillary system
- Performed Interface ADT unit testing between Epic EMR and Xim ancillary system
- Developed Interface ADT Script unit testing toolkit to use while testing with the Witt ancillary system
- Performed Interface ADT unit testing between Epic EMR and Witt ancillary system
- Developed Interface ADT Script unit testing toolkit to use while testing with the Midas ancillary system
- Performed Interface ADT unit testing between Epic EMR and Midas ancillary system
- Developed Interface ADT Script unit testing toolkit to use while testing with the Dexter ancillary system
- Performed Interface ADT unit testing between Epic EMR and Dexter ancillary system
- Provided technical guidance in client selection of integration engine selection.
- Transolutions – On Tuesday 4/13, participated in 2-hour integrated testing session with the Transolutions team and my client. The entire test plan was executed and no issues were detected that would require e*Gate interface code changes. One issue was raised regarding processing of “CC” providers (OBR.28). cleint reported that “CC” providers were not processing (printing) for the report types defined within the “HCCPS” department. I checked the printing options for the report types in question and discovered that the flag that controls printing of “CC” providers was set to “N” to not print. Researched the same flag in production and it was also set to “N”. Subsequently sent email to my client explaining the issue. Cient will contact the department for confirmation/explanation of their report type print settings for “CC” providers.
- Optivox ADT – Completed review of the Optivox HL7 ADT interface specification document in advance of the kick-off meeting. The Optivox HL7 ADT interface specification is very simple, supporting a short list of HL7 ADT events, segments and fields.
- Optivox ADT – Attended/participated in kick-off meeting Wednesday 4/14 with Optivox. Requested feedback from site contacts regarding message filter business rules based on patient type, patient location or medical service.
- Optivox ADT – Completed first draft of the interface requirements specification documents for both client locations based on feedback received to date from site contacts. Delivered the drafts to the combined team from Optivox and client locations.
- Powerscribe – Completed final review, requested changes and provided integration team sign-off on the completed Powerscribe HL7 interface specification document received from Powerscribe. Also, received request for changes to the specification from the client contact based her review of the document. Discussed each request with her and agreed that they were changes that we should request. Subsequently sent email listing these requests for changes along with explanation for each requested change.
- Powerscribe – Completed e*Gate build and unit test (using messages pulled from production with feeders/eaters) of the transformation business rules for the Meditech to Powerscribe orders (ORM^O01) interface. Implemented all transformation business based on the approved version of HL7 interface specification that includes the client’s special processing (e.g. PACS formatting of the Meditech accession number). Implementation of routing/filtering business rules based on Meditech procedure mnemonics is still pending.
- Powerscribe – Completed e*Gate build and unit test (using messages pulled from production with feeders/eaters) of the routing and transformation business rules for the Meditech to Powerscribe ADT interface. Implemented all routing and transformation business rules based on the completed/approved HL7 interface specification that includes all client and special processing (e.g. convert ADT^A34 to ADT^A30 required by Powerscribe for medical record number merges and convert ADT^A08 to ADT^A31 for updates).
- Cleaned up Datagate/eGate TRE environment by archiving identified orphan or unused software components.
- Attended GE Centricity kick-off project conference call to discuss integration changes and requirements.
- Created new Project in JCAPS 5.1.3 to process Epic order messages to RapidLink ancillary system
- Created new Connectivity Map for the RapidLink ancillary system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new Java Collaboration Definition for the RapidLink ancillary system in JCAPS 5.1.3
- Created new HL7 TCPIP External System for the RapidLink ancillary system under designated domain in JCAPS 5.1.3
- Created and configured new Deployment Profile for the RapidLink ancillary system in JCAPS 5.1.3
- Performed build and deploy on Deployment Profile for the RapidLink ancillary system in JCAPS 5.1.3
- Made modification to Java Collaboration Definition jcdHL7Inbound and performed build and deploy all projects that use it
- Performed ADT unit testing between Epic and Dexter ancillary system
- Performed ADT unit testing between Epic and Clinical Work Station ancillary system
- Performed troubleshooting analysis and made modifications to Java Collaboration Definition on the Epic ADT to CWS project
- Performed ADT unit testing between Epic and Midas ancillary system
- Created Unit Testing Toolkits to be used during ADT unit testing with ancillary systems
- Made modifications to Object Type Definition otdKhnAdt to accommodate the use of ZIN segment
- Performed validation on Java Collaboration Definition jcdOutCCAdtCws0 after making modifications to otdKhnAdt and made appropriate changes
- Analysis of Intersystems Ensemble Specifications.
- Conference call with Knowledge transfer to client in using SalesForce web services for Eligibility integration. Follow up, by reviewing SalesForce API documentation and generating recommendation regarding engine to use. Assemble initial workflow documentation. Creation and detail introduction for Eligibility flow diagram.
- Generate write-up of our Meaningful Use capabilities.
- Analysis of SYNAPPS product documentation.
- Transolutions PCMC – Attended weekly status conference call. Worked with client to identify a list of test patients that I would admit/register in the Meditech test system in advance of integrated testing schedule. Completed the registration of the 3 test patients, updated the test plan spreadsheet with the test patient information, consolidated Barb’s updates to the test plan spreadsheet and emailed the finalized test plan to the vendor from Transolutions.
- Completed 50% of the e*Gate coding for the ORM^O01 to ADT^A08 translation piece of the partial orders solutions for the client after finalizing the format of the combined accession/procedure data field. Later in the week, received word from the client that an alternate “workflow” based solution had just been proposed and accepted which solves the orders based reports problem. Therefore, I stopped working on the translation piece with approval of the client.
- Attended weekly status conference call. Worked with client at separate site to identify a list of test patient types that I would admit/register in the Meditech test system in advance of integrated testing. Completed the registration of the 7 test patients and shared the list of test patient information with client admissions. Client then updated the test plan spreadsheet and emailed the finalized test plan to Debbie from Transolutions.
- Participated in 3-hour integrated testing session with the Transolutions team. The entire test plan was executed and no issues were detected that would require e*Gate interface code changes. One issue was detected regarding the “default/generic” transcriptionist mnemonic which was not yet defined for the client test system. Subsequently sent a detailed email describing the issue with a suggestion to standardize to “TRANSOL” for all current and future Transolutions implementations and to also eliminate the “warning” messages that are generated for each report currently filed via the Meditech inbound ITS interface.
- Worked with client contact after integrated testing to test his code change solution for the warning that is currently reported by the e*Gate HL7 e*Way’s that deliver ADT messages to Transolutions for each of the current live sites. The warning “message ACK MSA segment not terminated with carriage return” was first reproduced, then client contact implemented his change, another test was run and the warning message was not recorded, problem solved. Will work with the client contact and the Integration team this week to propose a date for implementing the change.
- Attended interface discussion/planning conference call. This meeting focused on the Powerscribe Reports to Meditech interface. Identified the requirement to transform multiple ORC/OBR pairs from Powerscribe into single ORC/OBR pair. Also, requested that Powerscribe send report lines as repetitions within a single OBX segment instead of sending each report line in separate OBX segments.
- Allscripts – Pulled production messages and pushed them through the TEST environment in order to generate the raw data in the e*Gate log file for the “Message Sent/Not Sent” Report. Generated an Excel spreadsheet from the raw data and emailed the resulting spreadsheet to the client for his review and possible feedback / request for changes.
- Performed audit of eGate TRE system including Test and Production environments.
- Created automated audit reports of eGate TRE port and routing information in csv format which are emailed to analysts on a regular basis.
- Created automated issue reports of eGate TRE orphan files that are not used in the environment – identification files (.isc), translation files (.tsc) and configurations (*.cfgs/*.sc). These csv reports are emailed to analysts on a regular basis.
- Gathered data requirements from ESI, HMS(RODs), Safety Surveillor.
- Configured Epic Inbound/Outbound eway to get/put the HL7 messages from/to Epic.
- Went through existing interface logic for filtering criteria and to understand existing logic.
- Prepared the Analysis document from the existing interface.
- Developed OTD's for ADT/Orders interface data to get from/send to Epic.
- Configured HL7 Tcpip eway to send data to and from Epic, ESI, Safety Surveillor, HMS(RODs) system.
- Developed Interfaces to send ADT information from Epic to ESI, HMS, Safety Surveillor systems.
- Developed technical spec for ADT, Orders data for ESI, Safety Surveillor and HMS systems
- Created environment for Interfaces.
- Tested ADT, Orders, Results & Charges data flow between Epic, Radnet, careCast & McKesson systems.
- Co-ordinated with testing team in Unit Testing.
- Working with environments JCAPS 5.1.3, Epic, HL7 2.5, MLA, M2,ONCHOLOGY, PACS, Interface explorer, FTP server, AIX.
- Installation of Intersystems Ensemble.
- Installation and review of Mirth
- Contacting system administrators of external system to provide connectivity resolution.
- Research/Resolution (RR) for invalid records received from partner hospitals. Invalid records corrected and resubmitted with valid process completion.
- Resolving eGate and JCAPS alerts and fixing runtime errors.
- Enhancements in existing JCAPS interfaces.
- Data files transfers to partner clinics over the weekend.
- Attending conference calls for Epic Change Control and other issues.
- Validating interface connection and data flow after firewall changes.
- Interface design and development for CAMS project using JCAPS.
- Allscripts – On Monday 3/29, sent detailed email requesting feedback per the new procedure/report codes that I have identified to support the last three bullet items from the original report type request: “Tilt Table”, “Coronary CT” and “Peripheral Angiogram”.
- Transolutions – Completed connectivity test with client and sent 2 ADT messages, one inpatient and one outpatient, successfully filing into Transolutions test system. Also, mocked up one ADT^A08 for the outpatient with an OBR segment and successfully sent this message to the client for his review and feedback.
- Transolutions – Pulled a block of production order messages for research. Began research of the production order data by first loading the data into an Excel spreadsheet using e*Gate log files to isolate and export the data from key fields. Focused research on the fields that will be required per the status call discussion of supporting orders for ECHO and CATH procedure reports. The fields are the external accession (OBR.2), internal accession (OBR.18), HL7 order status (ORC.1) and “meditech” order status (ORC.5).
- Transolutions – Began detailed research of the production e*Gate interfaces for PCMC orders to PACS. Focused research on the handling/processing of the key fields OBR.2, OBR.3, ORC.1 and ORC.5 since this processing will have to be carried forward for this new partial orders support Transolutions interface.
- Transolutions – Attended weekly status meeting and confirmed readiness for integrated testing start later this week.
- Powerscribe – Attended Wednesday 4/31 interface discussion/planning conference call. This meeting focused on the Orders to Powerscribe interface. Documented via email the interface routing/transformation rules that were decided/confirmed on the call, focused on the key field processing for accession numbers and order status.
- Powerscribe – Began detailed research of the production Meditech orders data for PSJMC by first importing the production data into an Excel spreadsheet using e*Gate log files to isolate and export the data from key fields. Research is focused on the key order fields OBR.2, OBR.3, OBR.18, ORC.1 and ORC.5.
- Created new Project in JCAPS 5.1.3 to process CareCast order messages to Pinestar ancillary system
- Created new Connectivity Map for Orders to Pinestar and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new Java Collaboration Definition Orders to Pinestar in JCAPS 5.1.3
- Created new HL7 TCPIP External System for Orders to Pinestar under designated domain in JCAPS 5.1.3
- Created and configured new Deployment Profile for Orders to Pinestar in JCAPS 5.1.3
- Performed build and deploy on Deployment Profile for Orders to Pinestar in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to process Orchard and M2 Rad result messages to Epic system
- Created new Connectivity Map for Radiology results to EPIC and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new Java Collaboration Definition for Radiology results to EPIC in JCAPS 5.1.3
- Created new HL7 TCPIP External System for Radiology results to EPIC under designated domain in JCAPS 5.1.3
- Created and configured new Deployment Profile for Radiology results to EPIC in JCAPS 5.1.3
- Performed build and deploy on Deployment Profile for Radiology results to EPIC in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to process Lab result messages from M2 to the Epic system
- Created new Connectivity Map for lab results to EPIC and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new Java Collaboration Definition for lab results to EPIC in JCAPS 5.1.3
- Created new HL7 TCPIP External System for lab results to EPIC under designated domain in JCAPS 5.1.3
- Created and configured new Deployment Profile for lab results to EPIC in JCAPS 5.1.3
- Performed build and deploy on Deployment Profile for lab results to EPIC in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to process Lab order messages from M2 to the Epic system
- Created new Connectivity Map for lab orders to EPIC and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new Java Collaboration Definition for lab orders to EPIC in JCAPS 5.1.3
- Created new HL7 TCPIP External System for lab orders to EPIC under designated domain in JCAPS 5.1.3
- Created and configured new Deployment Profile for lab orders to EPIC in JCAPS 5.1.3
- Performed build and deploy on Deployment Profile for lab orders to EPIC in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to process Radiology result messages from M2 to the Epic system
- Created new Connectivity Map for Radiology results to EPIC and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new Java Collaboration Definition for Radiology results to EPIC in JCAPS 5.1.3
- Created new HL7 TCPIP External System for Radiology results to EPIC under designated domain in JCAPS 5.1.3
- Created and configured new Deployment Profile for Radiology results to EPIC in JCAPS 5.1.3
- Performed build and deploy on Deployment Profile for Radiology results to EPIC in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to process Radiology order messages from M2 to the Epic system
- Created new Connectivity Map for Radiology Orders to EPIC and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new Java Collaboration Definition for Radiology Orders to EPIC in JCAPS 5.1.3
- Created new HL7 TCPIP External System for Radiology Orders to EPIC under designated domain in JCAPS 5.1.3
- Created and configured new Deployment Profile for Radiology Orders to EPIC in JCAPS 5.1.3
- Performed build and deploy on Deployment Profile for Radiology Orders to EPIC in JCAPS 5.1.3
- Created Object Type Definition template ZPM and added to otdEpicChg in JCAPS 5.1.3
- Created Object Type Definition template ZPY and added to otdEpicChg in JCAPS 5.1.3
- Developed and implemented clearVariables method in Java Collaboration Definition jcdHL7Inbound.
- Built and tested Mirth ADT receiver translator that passes to listening ADT server translator that writes certain fields to a comma delimited file.
- Held a conference call with client to help them understand functionality around ADT to Sunrise RIS and orders to RIS from Siemens.
- Created verbiage for Oracle SOA Suite 11g and Oracle Fusion Middleware capabilities for website.
- Allscripts – Received confirmation/approval from client per the list of procedure/report codes that I previously identified for addition to the client interface filter on Wednesday. On Wednesday night, I completed the production implementation of the new procedure/report e*Gate data map files and updated the production collaboration rule script to point to the new data map files.
- Allscripts – Completed the production implementation of custom e*Way Connection “HL7TcpClientETD” for this interface on Wednesday night along with the new data map file implementation.
- Allscripts – Completed development of the”HL7TcpClientETD” installation procedures and implementation procedures documents. Also, completed creation of the “gmeek.zip” file that contains all of the code/scripts for compiling/installing/implementing “HL7TcpClientETD”.
- Moved all of these files up to the shared file server and then sent an email to the team sharing a brief description of “Hl7TcpClientETD” and the location of the install/implement documents and “gmeek.zip”.
- Allscripts – There are three bullet items from the original report type request: “Tilt Table”, “Coronary CT” and “Peripheral Angiogram” for which the Meditech procedure/report code research was still pending. I completed additional research and identified 15-20 additional Meditech procedure/report codes that should be added to cover the final three bullet items and will send off after I performed a final check on the codes. I was able to identify the additional procedure codes by expanding my research to additional procedure categories CCL, CT, EPL and SP.
- Transolutions – Attended PCMC and PUSMC status calls. Completed some basic message testing of the PCMC and PUSMC e*Gate interface modules on AEGT029 and AEGT03 in preparation for integrated testing next week. Also, created an inpatient and outpatient ADT’s in Meditech for both PCMC and PUSMC for use during integrated testing next week.
- Powerscribe – Completed 50% of the initial draft of e*Gate interface design document for this interface based on an Orders and limited ADT feed from PSJMC Meditech to Powerscribe along with a reports interface from Powerscribe back to Meditech.
- Developing Flowcast Schedule Interface to EPIC Using JCAPS
- Developing Monitor to Monitor for the runtime components of Jcaps Environment
- Developing AS OB Results Interface to CDR Using JCAPS.
- Changed PMM mapping based on mapping document changes and discussions.
- PMM(the message type is :MFN) connectivity testing done between PMM and EPic.
- Performing Unit testing between Epic and Radnet with ADT messages.
- Performed Connectivity testing between Epic and HDM.
- Documented the ADT interfaces for Epic to HDM,Jathomas,Glucose, Orders to MLA.
- Participated in meetings with Epic.
- Unit testing the interface built for EPIC and CareCast.
- Assisted client staff in debugging the Interface and system errors.
- Reviewed the JCAPS interfaces built for passing HL7 messages between Epic and CareCast and Radnet.
- Tested FTP Inbound eway to get the files from FTP server and Local files.
- Tested HL7 Tcpip eway to send data to Epic system.
- Changes completed with unit testing of Interface to send ADT data to Cerner Radnet.
- Created environment for Intefaces.
- Deployment created using JCAPS eDesigner and deployed.
- COnfigured Domains created in eDesigner to add to eManager.
- Deployed deployment profiles by using eManager and AppServer console.
- At clients request, utilized remote access to conduct eGate Training for new hires.
- Supporting Day to Day (DtD) operations of eGate.
- Begin project to institute Unit Testing as part of the development cycle.
- Presented proposal to acquire unit testing tools such as UltraEdit and Hl7 Explorer
- Attended Client status meeting and participated in discussion and did some follow up on the issue of the work flow requirement to attach reports to orders in Meditech for departmental reports coming back from Transolutions.
- Completed the pilot of “HL7TcpClientETD” for this interface on Friday afternoon. Confirmed with Allscripts that no duplicate reports were created during the pilot. A total of 25 messages were sent to Allscripts during the pilot. Each time messages were available, “HL7TcpClientETD” connected, sent all available messages, then closed the connection. The plan is to implement “HL7TcpClientETD” in production Monday or Tuesday night this coming week.
- Completed additional research and analysis to identify the client specific Meditech procedure and report codes required to meet client requests for sending additional ITS report type’s for both Phase 1 and Phase 2. I reviewed each active Meditech procedure code’s description and each active report description (for departments RAD, CARD and MRES) and compared the descriptions to client’s requested list of reports and identified approximately 20 procedure codes and report types that we should add to the interface filter. Then sent an email to the management team, communicating the filter changes that we will hopefully make next week to add the new reports. Client user team is currently reviewing the list of procedure/report codes that I shared with them in Excel format. Once I hear back with confirmation from Management, the data map changes have been made and tested for the interface and are ready for production implementation.
- Worked with the client to have the “CARD” department turned on which moved us closer to sending the full list of report types on the user’s list since “CARD” report types were previously not sent through the interface. This change will also help provide a complete view for the “Do Not Send” reports that I will begin sending to the user. This report is pulled from log file entries and will be useful for identifying reports types that should be added to the interface feed, but were not identified up front for whatever reason.
- Completed 50% of the development of a 2-3 page install/support procedures document for the “HL7TcpClientETD” custom e*Way Connection. This document will ultimately include instructions for installing “HL7TcpClientETD” to a new e*Gate schema and also instructions for implementing “HL7TcpClientETD” for an e*Gate interface.
- Attended kick-off meeting and received copy of the Powerscribe HL7 Interface specification document. Completed detailed read/review of the document. Identified from the document and meeting that no ADT backload would be necessary, since Powerscribe pulls ADT data from the order HL7 message. Identified that Powerscribe supports ADT’s, but only wants updates (A30 translated from Meditech A08) and medical record merges (A31 – translated from Meditech A40/A44).
- Completed detailed research of existing e*Gate interfaces that use the PACS Orders feed from client both in the ProvenaHealthPACS e*Gate schema and the ProvenaHealthCS e*Gate schema. Identified that for each interface the message routing/filtering rules are based on the ORC.1 (Order Control – NW, CA and SC/XO) values and OBR.4.1 and OBR.4.2 (Procedure Category and Code) values. Identified that “XO/SC” are status update transactions.
- Revised PowerPoint presentation and conducted meeting illustrating the steps for integrating orders from a foreign EMR system.
- Continued training and development of ADT Receiver Mirth interface .
- Participated in meeting to discuss opportunities with HAP
- Modifications and Enhancements made to
client websites using Dreamweaver software.
- Technical input provided to client for
completion of their request for Information document (RFI).
- Created new Project in JCAPS 5.1.3 to
process Epic ADT messages to Individual Health Record ancillary system
- Created new Connectivity Map for
processing ADT to IHR system and configured with needed components in JCAPS
5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing ADT to IHR system in JCAPS 5.1.3
- Created new HL7 TCPIP External System for
processing ADT to IHR system under designated domain in JCAPS 5.1.3
- Created and configured new Deployment
Profile for processing ADT to IHR system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for processing ADT to IHR system in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process Radnet Radiology result messages to the Individual Health Record
ancillary system
- Created new Connectivity Map for
processing Radnet Radiology results to IHR system and configured with needed
components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing Radnet Radiology results to IHR
system in JCAPS 5.1.3
- Created new HL7 TCPIP External System for
processing Radnet Radiology results to IHR system under designated domain in JCAPS
5.1.3
- Created and configured new Deployment
Profile for processing Radnet Radiology results to IHR system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for processing Radnet Radiology results to IHR system in
JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process Epic ADT messages to RALS ancillary system
- Created new Connectivity Map to
process ADT to RALS system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition to process ADT to RALS system in JCAPS 5.1.3
- Created new HL7 TCPIP External System to
process ADT to RALS system under designated domain in JCAPS 5.1.3
- Created and configured new Deployment
Profile to process ADT to RALS system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile to process ADT to RALS system in JCAPS 5.1.3
- Performed connectivity testing between
the JCAPS 5.1.3 Epic Test environment to the Dexter ancillary system
- Performed connectivity testing between
the JCAPS 5.1.3 Epic Test environment to the IntelliDesk ancillary system
- Performed connectivity testing between
the JCAPS 5.1.3 Epic Test environment to the Pyxis ancillary system
- Performed connectivity testing between
the JCAPS 5.1.3 Epic Test environment to the Individual Health Record ancillary
system
- Performed connectivity testing between
the JCAPS 5.1.3 Epic Test environment to the Witt ancillary system
- Performed connectivity testing between
the JCAPS 5.1.3 Epic Test environment to the Xim ancillary system
- Performed connectivity testing between
the JCAPS 5.1.3 Epic Test environment to the MedAptus ancillary system
- Completed final draft of the e*Gate production implementation plan for
this interface. Added steps to install
MOVEIt (FTPS) software. Also added steps
to install MOVEit FTPS script and DOS .bat files developed for this interface.
- Received request from client to send an additional test file generated
from historical production data for the month of February for all six external
facilities. Pulled the production data
files, stripped PD1 segments from the production messages for two of these
sites, set up and executed the e*Gate interface test. Then sent the resulting output HL7 batch file
using MOVEit script and notified IDPH that the file was sent.
- Completed e*Gate code changes and testing to the SOI_ELR_TRX
collaboration rule script to stop inaccurate logging of CLIA lookup failure for
OBX.15.
- Completed draft of the e*Gate production implementation plan for client.
- Completed draft of the e*Gate production implementation plan for secondary
client site.
- Completed coding changes to custom e*Way connection “HL7TcpClientETD”
to add configurable parameter “Connect Only When Data Available”. This parameter when set to “YES” instructs
“HL7TcpClientETD” to connect to the remote system only when data is available
for the JMS input topic. This parameter
when set to “NO” instructs “HL7TcpClientETD” to connect to the remote system
when the e*Way is started.
- Completed coding changes to custom e*Way connection “HL7TcpClientETD”
to add configurable parameter “Maximum Number Connection Verifications Since
Last Send”. This parameter is only
relevant if the “Connect Only When Data Available” is set to “YES”. This parameter will close the connection to
the remote system once this threshold is met.
This threshold will be met once all data available for the JMS input
topic has been read/received and the message count is equal zero.
- Completed a thorough set of message testing of the changes to
“HL7TcpClientETD” custom e*Way Connection using high volumes of data and also
the introduction of dropped connections in the middle of high volume message
exchanges to ensure that two new configurable parameters are working as
designed.
- Added subscription to production client reports data from the TEST
e*Gate server in order to temporarily route production data through the custom
e*Way connection “HL7TcpClientETD”. Will
continue the test for the next week with the hope that the “Connect Only When
Data Available” protocol will eliminate the connection handling issues that are
currently resulting in duplicate reports within the client’s Allscript
application.
- Created new Project in JCAPS 5.1.3 to
process Master File messages for providers to the ancillary systems
- Created new Connectivity Map for
processing Master Files and configured with needed components in JCAPS 5.1.3
- Created and configured new Deployment
Profile for processing Master Files in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for processing Master Files in JCAPS 5.1.3
- Created new custom Object Type
Definition to be used as a template for a new OTD
- Created new Object Type Definition to
be used for messages destined to ancillary systems
- Created new Project in JCAPS 5.1.3 to
process Master File messages for providers to the ancillary Sunquest
system
- Created new Connectivity Map for
processing Master Files to Sunquest and configured with needed components in
JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing Master Files to Sunquest in JCAPS
5.1.3
- Created and configured new Deployment
Profile for processing Master Files to Sunquest in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for processing Master Files to Sunquest in JCAPS 5.1.3
- Started connectivity testing with the
ancillary system Clinical Work Station
- Performed modifications to resolve
issues with MRN and SSN format
- Started connectivity testing with the
ancillary system Dexter
- Started connectivity testing with the
ancillary system Midas
- Created new Project in JCAPS 5.1.3 to
process Epic ADT messages to the ancillary Relay Health system
- Created new Connectivity Map for
processing ADT to Relay Health and configured with needed components in JCAPS
5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing ADT to Relay Health in JCAPS 5.1.3
- Created and configured new Deployment
Profile for processing ADT to Relay Health in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for processing ADT to Relay Health in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process Epic ADT messages to the ancillary Pyxis system
- Created new Connectivity Map for processing ADT to Pyxis and configured
with needed components in JCAPS 5.1.3
- Created, validated, and compiled new Java Collaboration Definition for
processing ADT to Pyxis in JCAPS 5.1.3
- Created and configured new Deployment Profile for processing ADT to
Pyxis in JCAPS 5.1.3
- Performed build and deploy on Deployment Profile for processing ADT to
Pyxis in JCAPS 5.1.
- Completed build
of e*Gate components in production and completed cutover of the live ADT feed
from test to production.
- Identified
truncation bug with the “Copy To” field – HL7 OBR.28 – after the issue was
reported by Users. The provider mnemonic
was truncated to five characters when the mnemonic happened to be greater than
five bytes long. Tested the code change
and implemented the change in production.
Then completed the same code change for multiple remote site e*Gate
interfaces.
- Identified and
reported Meditech ITS inbound report rejections based on report type code
errors and provider mnemonic “PHYNS – Physician Non-Staff provider. Complete message re-sends after the necessary
Meditech dictionary entries were defined by client and all re-sent messages
filed successfully.
- Completed
integrated test of this interface working.
Three lead test results were tested with no issues.
- Completed e*Gate
changes and testing to implement filter rules for HL7 update (A08)
transactions. These changes filter out
A08 transactions for pre-admit patients and discharged patients.
- Completed e*Gate
configuration change to point to new Intego server at client site after pulling
together a conference call to discuss the timeline and impacts of the server
switch.
- Implemented
custom e*Way connection called “HL7TcpClient” that implements HL7 MLLP over
TCP/IP client in “TEST” for the client’s interface. Completed side by side test of “HL7TcpClient”
and the e*Gate standard “TCP/IP HL7 e*Way”.
Discovered that the “HL7TcpClient” reports “I/O Exception – connection
reset by peer” for the same conditions that cause the “TCP/IP HL7 e*Way” to
report the MLLP error “STX character not found”. In addition, Allscripts reported that they
only received one copy of the message for the “HL7TcpClient” test and two
copies for the “TCP/IP HL7 e*Way” test.
The conclusion drawn here is that it is worth piloting “HL7TcpClient”
for 3-4 days to see if it will resolve the duplicate report issue we are
currently experiencing. A final test if
planned for Monday afternoon with Allscripts.
- Completed initial
draft of the production implementation plan for this interface. Still need to complete the piece of the plan
that includes installing support for the MOVEIt software and associated MOVEit
FTPS script.
- Completed a review/revise of the e*Gate production implementation plan
for client after receiving some great feedback from review team regarding the
initial draft.
- Completed build of the client e*Gate interface modules in PROD on
Thursday night 2/25. Completed initial
test of connectivity prior to starting the modules. Completed the final ADT backload as part of
the production implementation steps prior to the cutover to the live ADT feed.
- Completed successful re-test of the A06 and A12 transactions after
receiving feedback from Intego that their application did not properly handle
the original test. They modified their
code to properly handle the A06 (much like an A01) and also the A12
(Cancel/Undo Transfer after A02).
- Modified the interface modules in TEST to pull in ADT messages from
PROD. Subsequently turned on the live
ADT to Intego on Tuesday morning 2/23 and then monitored the interface
throughout the week. No issues to
report. Followed up with the team and
received positive feedback, so will continue with the plan to cutover from TEST
to PROD next Monday night 3/1.
- Completed the first draft of the production implementation plan for
this interface.
- Worked with the team to schedule two integrated testing sessions for
Monday 3/1 and Tuesday 3/2
- Received report from a client ancillary site that ORU reports where
being duplicated within Allscripts.
Completed detailed research of the e*Gate log files, corresponded at
length with Allscripts and also worked directly with client lead regarding
possible VPN issues. Client lead agreed
to turn on a packet capture and to adjust the connection timeout from 12 hours
to 7 days to see if this could rule out the VPN as a contributing factor. Based on my research into the issue,
presented options for pursuing a solution.
The first option involves additional research to review possible flaws
in the implementation of an HLy MPPL Server/Receiver in Allscripts. The second option involves using a custom
e*Way connection that I have that implements an HL7 MLLP client and would
replace the existing TCP/IP HL7 e*Way Adapter.
The custom e*Way connection would make it possible to report exactly how
this Allscripts flaw is violating the rules of HL7 MLLP and also provide an
avenue for customizing the e*Way connection to handle its eccentricities
without causing duplicates within Allscripts.
- Using Remote Assist, I conducted eGate Training for new hires for the
client.
- Create new Batch modules
- Modifed existing code in response to user request
- Review specifications for new interfaces.
- Manage assigned tickets in client’s incident reporting system
- Conduct tests
- Report results
- Modify code in response to test results
- Organize move to production utilizing client’s go live procedures
- Created new Project in JCAPS 5.1.3 to
process Lab Result messages to the ancillary Clinical Work
Station system
- Created new Connectivity Map for Lab
Result messages to the ancillary Clinical Work
Station system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for Lab Result messages to the ancillary Clinical
Work Station system in JCAPS 5.1.3
- Created and configured new Deployment
Profile for Lab Result messages to the ancillary Clinical Work
Station system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for Lab Result messages to the ancillary Clinical
Work Station system in JCAPS 5.1.3
- Created new custom Object Type
Definition to be included on the EpicAdt
OTD
- Created new Project in JCAPS 5.1.3 to
process Vascular result messages to the ancillary Clinical
Work Station system
- Created new Connectivity Map for Vascular
result messages to the ancillary Clinical Work
Station system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for Vascular result messages to the ancillary Clinical
Work Station system in JCAPS 5.1.3
- Created and configured new Deployment
Profile for Vascular result messages to the ancillary Clinical
Work Station system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for Vascular result messages to
the ancillary Clinical Work Station system in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process result messages to the ancillary Clinical Work
Station system
- Created new Connectivity Map for
processing result messages to the ancillary Clinical Work
Station Alpha system and configured
with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing result messages to
the ancillary Clinical Work Station Alpha system
- in JCAPS 5.1.3
- Created and configured new Deployment
Profile for processing result messages to the ancillary Clinical
Work Station Alpha system in JCAPS
5.1.3
- Performed build and deploy on
Deployment Profile for processing result messages to
the ancillary Clinical Work Station Alpha system in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process result messages to the ancillary Clinical Work
Station Beta system
- Created new Connectivity Map to
process result messages to the ancillary Clinical Work
Station Beta system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing result messages to
the ancillary Clinical Work Station Beta system in JCAPS 5.1.3
- Created and configured new Deployment
Profile for process messages to the ancillary Clinical Work Station Beta system
in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for process messages to the ancillary Clinical Work Station
Beta system in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process result messages to the ancillary Clinical Work
Station system
- Created new Connectivity Map to
process result messages to the ancillary Clinical Work
Station system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition to process result messages to
the ancillary Clinical Work Station system in JCAPS 5.1.3
- Created and configured new Deployment
Profile to process result messages to
the ancillary Clinical Work Station system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile to process result messages to
the ancillary Clinical Work Station system in JCAPS 5.1.3
- Performed ADT connectivity testing
between CareCast-JCAPs 5.1.3-Epic
- Performed Orders connectivity testing between
CareCast-JCAPs 5.1.3-Epic
- Performed ADT connectivity testing
between McKesson-JCAPs 5.1.3-Epic
- Performed Orders connectivity testing
between M2-JCAPs 5.1.3-Epic
- Created new Project in JCAPS 5.1.3 to
process ADT messages to the ancillary Midas system
- Created new Connectivity Map for
processing ADT messages to the ancillary Midas system and
configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing ADT messages to
the ancillary Midas system in JCAPS 5.1.3
- Created and configured new Deployment
Profile for processing ADT messages to
the ancillary Midas system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for processing ADT messages to
the ancillary Midas system in JCAPS 5.1.3
- Gathered data requirements from M2, Onchology, PACS
system team.
- Configured FTP Inbound/Outbound eway to get/put the files from/to
FTP server.
- Went through existing interface logic for filtering criteria and to
understand existing logic.
- Developed OTD's for Orders/results/charge interface data to
get from/send to Epic.
- Configured HL7 Tcpip eway to send data to and from Epic, Onchology, M2
& PACS system.
- Developed Interfaces to & from send real time data to
Epic, Onchology, PACS interfaces.
- Developed Interface to send ADT, Orders, Results &
Charges data to & from M2, MLA, PACS & Onchology systems.
- Developed technical spec for ADT, Orders, results &
Charges data for Onchology, M2, MLA & PACS systems
- Created environment for Intefaces.
- Tested ADT, Orders, Results & Charges data flow between Epic,
Onchology, MLA, PACS systems.
- Environment interaction: JCAPS 5.1.3, Epic, HL7 2.5,
MLA, M2,ONCHOLOGY, PACS, Interface explorer, FTP server, AIX.
|
877.303.3377
The expertise provided by
Orchestrate Healthcare has been invaluable to my company.