My Blog

• 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

1. Conduct tests
2. Report results
3. Modify code in response to test results
4. 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.

• Modified Java Collaboration Definition  to extract email addresses from file on server instead of them being hardcoded.
• Modified, validated, and compiled Java Collaboration Definition for EPIC ADT in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile EPIC ADT JCAPS 5.1.3
• Created new Project From Epic to MedAptus in JCAPS 5.1.3 to process Epic ADT messages to MedAptus ancillary system
• Created new Connectivity Map From Epic to MedAptus and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition From Epic to MedAptus in JCAPS 5.1.3
• Created new HL7 TCPIP External System From Epic to MedAptus under designated domain in JCAPS 5.1.3
• Created and configured new Deployment Profile From Epic to MedAptus in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile From Epic to MedAptus in JCAPS 5.1.3
• Created new Project for ADT from Epic to Optimum in JCAPS 5.1.3 to process ADT messages to ancillary Optimum system
• Created new Connectivity Map for ADT from Epic to Optimum and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition for ADT from Epic to Optimum in JCAPS 5.1.3
• Created new Batch Local File External System for ADT from Epic to Optimum under designated domain in JCAPS 5.1.3
• Created and configured new Deployment Profile for ADT from Epic to Optimum in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile for ADT from Epic to Optimum in JCAPS 5.1.3
• Created new Project for ADT from Epic to RapidLinkGVSV in JCAPS 5.1.3 to process ADT messages to ancillary RapidLink system
• Created new Connectivity Map for ADT from Epic to RapidLinkGVSV and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition for ADT from Epic to RapidLinkGVSV in JCAPS 5.1.3
• Created new HL7 External System for ADT from Epic to RapidLinkGVSV under designated domain in JCAPS 5.1.3
• Created and configured new Deployment Profile for ADT from Epic to RapidLinkGVSV in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile for ADT from Epic to RapidLinkGVSV in JCAPS 5.1.3
• Created new Project in JCAPS 5.1.3 to process charge messages from the  ancillary RapidLink system
• Created new Connectivity Map to handle the charge messges from RapidLink and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition to handle the charge messges from RapidLink in JCAPS 5.1.3
• Created and configured new Deployment Profile to handle the charge messges from RapidLink in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile to handle the charge messges from RapidLink in JCAPS 5.1.3
• Created new Project in JCAPS 5.1.3 to process charge messages from the ancillary Xim system
• Created new Connectivity Map to handle charge messages from Xim and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition to handle charge messages from Xim in JCAPS 5.1.3
• Created and configured new Deployment Profile to handle charge messages from Xim in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile to handle charge messages from Xim in JCAPS 5.1.3
• Gathered data requirements from PMM Inventory team.
• Configured FTP Inbound eway to get the files from FTP server.
• Developed OTD for Inventory data to get from Epic.
• Configured HL7 Tcpip eway to send data to and from Epic system.
• Developed Interfaces to & from send real time data to Epic interface 
• Developed Interface to send ADT, Orders, Results & Charges data to & from Cerner Radnet, PACS
• Developed OTDs for Cerner Radnet Adt, Orders, Results & Charges data(PMM)
• Developed technical spec for ADT, Orders, results & Charges data to & from EPIC
• Created environment for Intefaces.
• Environment interaction: JCAPS 5.1.3, Epic, HL7 2.5, Cerner Radnet, PMM, Interface explorer, FTP server, AIX.
• Corresponded with the Financial team lead regarding “Medicaid” codes, explaining the State requirement and the methods used to identify a preliminary list of insurance plan codes that are considered “Medicaid” codes within Meditech.  She provided a short list of the Medicaid codes that are now.  As a result, I updated the code to eliminate the data map file and simply check against the standardized list of Medicaid codes for all ministries.
• Updated the code to consolidate the data map files for the main campus and lab facilities so that the CLIA, Description, Address and Phone data are now maintained in a single data map file.
• Updated the e*Gate Java code to load the data map file data into “Hashmap” objects that will available in memory across invocations of the “executeBusinessRules” method as opposed to performing data map lookups for each invocation as messages are received.  This greatly improved the performance of the collaboration rule script based on a controlled test to measure the throughput before and after the changes.  I made this change because the expected daily message traffic is substantial based on the fact that all six ministries will be feeding lab result messages through the collaboration rule script.
• Completed changes to merge transaction processing based on detailed testing of the various merge transactions supported by Meditech and also the Intego HL7 requirements for merges per Intego.  In short, Meditech delivers the previous Account Number in MRG.1 and Intego expects it in MRG.3 per the HL7 Standard.  Meditech delivers the previous Account Number in MRG.1.  So, changed the script to map MRG.1 to MRG.3 for the A18 (Account Number Merge) transaction.
• Completed basic message testing working with Larry Meadows who verified that each ADT transaction was properly processed by the Intego application.  Testing this week included merge transactions for both Account Number (A18) and Medical Record Number (A40/A44) as well as testing of Cancel Transfer (A12), Pre-admit (A05) and Outpatient to Inpatient Transfer (A06).
• Prepared and researched process, then began the backload of ADT messages from production Meditech for client into the production server starting from 2/1 forward through Friday 2/19.  From this point until the cutover next week to the production eGate server, will continue to pull and send the production “eater” files for ADT’s as they become available from the “eater” e*Way.  Each file contains 10,000 ADT messages and are closed/completed approximately once every two days.
• Completed the first draft of the client’s e*Gate production implementation plan.

• Created new Projects in JCAPS 5.1.3 to process Epic ADT messages to ancillary Witt system
• Created new Connectivity Map for Epic ADT messages to Witt and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition for Epic ADT messages to Witt in JCAPS 5.1.3
• Created new HL7 TCPIP External System for Epic ADT messages to Witt under designated domain in JCAPS 5.1.3
• Created and configured new Deployment Profile for Epic ADT messages to Witt in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile for Epic ADT messages to Witt in JCAPS 5.1.3
• Created new Project in JCAPS 5.1.3 to process Epic ADT messages to Xim ancillary system
• Created new Connectivity Map for Epic ADT messages to Xim and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition for Epic ADT messages to Xim in JCAPS 5.1.3
• Created new HL7 TCPIP External System for Epic ADT messages to Xim under designated domain in JCAPS 5.1.3
• Created and configured new Deployment Profile for Epic ADT messages to Xim in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile for Epic ADT messages to Xim in JCAPS 5.1.3
• Created new Project in JCAPS 5.1.3 to process ADT messages to ancillary Midas system
• Created new Connectivity Map for ADT messages to Midas and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition for ADT messages to Midas to be used by all Midas projects in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration for ADT messages to Midas in JCAPS 5.1.3
• Created new HL7 TCPIP External System for ADT messages to Midas under designated domain in JCAPS 5.1.3
• Created and configured new Deployment Profile for ADT messages to Midas in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile for ADT messages to Midas in JCAPS 5.1.3
• Installed and configured NetBeans.
• Installed and configured MySQL.
• Installed and configured Java.
• Technical RFP review and response for Northern HIE for infrastructure integration as well as client tier integration.
• Contacting system administrators of external system to provide connectivity
• Looking for invalid records received from partner hospitals and making corrections and resending those records for processing.
• Resolving e*Gate and JCAPS alerts and correcting complex the runtime errors.
• Data files transfers to partner clinics.
• Attending conference calls for Epic Change Control and other issues.
• Validating interface connection and data flow after firewall changes.
• Interface planning and design for new development in JCAPS.
• Development of CAMS projects interfaces.
• Develop new interface using JCAPS to transfer patients records to partner clinic's FTP server.
• Gathered data requirements from M2(Radiology), GE ViewPoint team.
• Configured FTP Inbound eway to get the files from FTP server.
• Configured HL7 Tcpip eway to send data to and from Epic system.
• Developed Interfaces to & from send real time data to Epic interface 
• Developed Interface to send ADT, Orders, Results & Charges data to & from Cerner Radnet
• Developed OTDs for Cerner Radnet Adt, Orders, Results & Charges data(PMM)
• Developed technical spec for ADT, Orders, results & Charges data to & from EPIC
• Created environment for Intefaces.
• Integration tasks for the following environments: JCAPS 5.1.3, Epic, HL7 2.5, Cerner Radnet, GE ViewPoint, Interface explorer, FTP server, AIX
• Completed code review with the team in two one-hour sessions.  We reviewed the client code in detail and discussed at length the e*Gate Java features that I utilized for the interface with particular emphasis on the use of the “Process” and “Runtime” classes to call and manage Windows script (.bat) from within an e*Gate Java collaboration rule script.
• Allscripts – Completed research of “Service Date” (OBR.7) issue reported by client and proposed solution to map “Admit Date” as the “Service Date” for all reports saving “Discharge Summary” where the “Discharge Date” is mapped for “Service Date”.  Completed the changes and tested. Bumped the version of the collaboration rule script and then moved the change into production.
• Allscripts – Reported issue with HL7 MLLP connection timing out during long periods of inactivity to Allscripts.  After discussions, the conclusion was made that this is not an application layer issue and that we will need to report the issue to our VPN experts for further research and investigation into possible timeout settings at the VPN level.
• Allscripts – Identified and then reported to client the fact that we are not yet sending reports associated with the “ECHO” and “STRESS” procedure categories.  Completed research into the “active” procedure codes for the above categories, ultimately creating comprehensive documentation that details the procedure codes that are currently included in the message filter to theclient.  Shared this information with the team so that he can choose the procedure codes that we need to add to the filter in order to provide “ECHO” and “STRESS” reports and also so that we can choose the proper reports for the client’s Phase 2 list.
• Intego Nurse Call – Completed 80% of the basic message testing with Intego through test patient registrations within Meditech, followed by control testing of the resulting HL7 messages.
• Completed testing of all ADT message types saving the “Merge” ADT transactions which will require changes before the testing is completed.
• Created a series of spreadsheets to document the data map content that I created for this interface to support CLIA, LOINC and HL7 table mapping required for this interface.  Then, developed and delivered an email to the team requesting approval and/or feedback on the content.  Received solid feedback from client on the lab test and result codes.  Waiting on feedback regarding the Medicaid plan codes per an email to the financial team.
• Completed changes to the collaboration rules script to prevent the sending of messages when certain conditions are not met within the business rules per suggestion from the team at code review.  The changes will prevent the sending of messages when CLIA lookups fail for ministry and/or laboratory and will create log file entries to report when these data map lookup failures occur so that they can be identified and fixed down the road.
• Transolutions – Supported some add-on testing that occurred throughout the week and also worked out a strategy regarding the backload of ADT’s in advance of the 3/1 live date for St. Mary’s.

• Entered into discussions for providing assistance during Sunrise Radiology implementation project.
• Created new Project in JCAPS 5.1.3 to process Epic ADT messages to ancillary Picis system
• Created new Connectivity Map for EPIC ADT to Picis and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition for EPIC ADT to Picis in JCAPS 5.1.3
• Created new HL7 TCPIP External System for EPIC ADT to Picis under designated domain in JCAPS 5.1.3
• Created and configured new Deployment Profile for EPIC ADT to Picis in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile for EPIC ADT to Picis in JCAPS 5.1.3
• Created new Project in JCAPS 5.1.3 to process Epic ADT messages to Dexter ancillary system
• Created new Connectivity Map for Epic ADT messages to Dexter and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition for Epic ADT messages to Dexter in JCAPS 5.1.3
• Created new HL7 TCPIP External System for Epic ADT messages to Dexter under designated domain in JCAPS 5.1.3
• Created and configured new Deployment Profile for Epic ADT messages to Dexter in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile for Epic ADT messages to Dexter in JCAPS 5.1.3
• Created new Project  in JCAPS 5.1.3 to process ADT messages to ancillary IntelliDesk system
• Created new Connectivity Map for Epic ADT messages to IntelliDesk and configured with needed components in JCAPS 5.1.3
• Created, validated, and compiled new Java Collaboration Definition for Epic ADT messages to IntelliDesk in JCAPS 5.1.3
• Created new HL7 TCPIP External System for Epic ADT messages to IntelliDesk under designated domain in JCAPS 5.1.3
• Created and configured new Deployment Profile for Epic ADT messages to IntelliDesk in JCAPS 5.1.3
• Performed build and deploy on Deployment Profile for Epic ADT messages to IntelliDesk in JCAPS 5.1.3
• Allscripts – Completed build of e*Gate components in production Monday 2/1.
• Allscripts – Attended Pre Go-Live status meeting Tuesday 2/2.
• Allscripts – Completed Go-Live to turn e*Gate components on in production the evening of Wednesday 2/3 and generally monitored the status of message processing the rest of the week and have no major issues occurred.  Message traffic was very light.
• Intego Nurse Call – Attended status meeting with the team 2/3 and received good feedback from Intego before, during and after the meeting with regards to message filtering requirements and identified that a VPN tunnel will not be necessary because the Intego server sits inside the client network.
• Intego Nurse Call – Completed changes to the message filtering business rules for this interface.  In short, the Intego system is only interested in seeing transactions that affect bed assignments, but is also interested in seeing transactions for Inpatient Pre-Admits.  Also, completed unit testing of the interface after completing the message filtering business rule changes.
• Intego Nurse Call – Received IP Address and Port Number information from Intego for their interface server and configured the e*Gate component to point to the IP and Port.  Completed connectivity test and also completed testing of one A01 transaction late Friday afternoon that was successfully filed into the Intego application.  Also generated a series of test ADT’s in the Meditech system that I have set aside for further testing Monday afternoon with Intego.
• Intego Nurse Call – Worked out a strategy with the team to complete basic message testing, then turn on a live feed from Client ADT to the Intego test system most likely late next week.
• Transolutions – Participated in two integrated testing calls for the client Thursday 2/4 and Friday 2/5.  Also supported some additional testing after the two conference calls to address issues identified during the calls.  Generally speaking, the testing went extremely well with no issues with the e*Gate components of the interface.
• Contacted client concerning the last test file that I sent on 1/25.  Client reviewing with results sometime next week.

• Gathered data requirements for GE and M2 (Rhapsody) system Interfaces.
• Preparing map document to build interfaces.
• Tested the interface built for EPIC and CareCast.
• Helped 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.
• Developed and Tested Interface to send ADT data to Cerner Radnet
• Developed technical spec for ADT data to send to EPIC and PMM
• Created environment for Intefaces.
• environment: JCAPS 5.1.3, Epic, CareCast, HL7 2.5, Cerner Radnet, PMM, Interface explorer, FTP server, AIX.
• Received test database and subsequently loaded it into SQL Server 2000 and 2008.  Made minor upgrade for code to allow Windows authentication, instead of user authentication.  Confirmed to work in both SQL Server versions on an Windows XP platform.
• Performed analysis of code producing a definitive estimate of the work effort involved.
• Created project in JCAPS 5.1.3 for Epic ADT to Medquest Transcription service
• Developed Java Collaboration Definition, Connectivity Map, and Deployment profile for prjOutEpicAdtMedquest
• Created project in JCAPS 5.1.3 to receive transactions from Medquest Transcriptions service
• Developed Java Collaboration Definition, Connectivity Map, and Deployment profile for prjInMedquestTrns
• Created project in JCAPS 5.1.3 to send Medquest Transcriptions to Epic Bridges
• Developed Java Collaboration Definition, Connectivity Map, and Deployment profile for prjOutMedquestTrnsEpic
• Configured Epic Bridges interfaces in POC environment with designated port numbers and IP addresses
• Configured JCAPS 5.1.3 project prjInEpicAdt to start receiving ADT transactions from Epic POC environment
• Performed troubleshooting and resolved issues with exceptions created from new ADT transactions
• Updated Object Type Definition otdEpicAdt to include Z segments being received from POC environment
• Perform build and deploy on ADT interfaces after update of Epic OTD was completed
• Developed ,Deployed  JCAPS Interfaces   
  • Flowcast ADT Inbound interface to EPIC
  • Star ADT Inbound interface to EPIC
• Performed Communication Testing end-to-end From Sending Systems to JCAPS to EPIC.
• Participated in EPIC First user validation sessions
• Completed detailed review of output file and log files for testing for lead lab results for the remaining Meditech Client/Server sites DA, DB and DC.  Identified additional Specimen Source Result Code (OBX.3.1) for identifying the blood draw source (venous/capillary).
• Completed another iteration of testing of approximately 5 lead lab result messages from each ministry and then delivered the output file to IDPH as promised.  This iteration addressed the issue of “UNK” strings in OBR.7 and OBR.14.  Requested that the file be run through the IDPH validation tool and currently awaiting feedback from IDPH.
• Created and distributed a summary status of the project that also included a suggested list of tasks remaining to complete final requirements and associated business rules and to prepare for, schedule and execute integrated testing.
• Conference with client and 3^rd party vendor to discuss initial development and financial analysis on regional Health Information Exchange (HIE).
• Provided technical integration resource requirements to successfully fulfill Phase 1 requirements based on HIE rollout with consideration to time constraints. 
• Completed a series of enhancements and refinements to the e*Gate collaboration rule scripts for Intego to simply the naming of components, add support for the PV1.18 field (Patient Type), eliminate extra delimiters for PID.5, PV1.3 and PV1.6.
• Updated the ADT Template spreadsheet to specify the IP Address for both the TEST and PROD e*Gate environments for client.  Also, completed detailed research of production ADT messages from CMC and of the HL7 specifications and dictionary values and used the output of this research to create a new tab in the ADT Template spreadsheet to list the codes set for PID and PV1 fields.
• Submitted the updated ADT Template spreadsheet along with a list of questions regarding possible data mapping/translation requirements from Meditech to Proven and also for possible message filtering rules centered on Meditech Patient Type and Status values.
• Worked with client to map out a schedule for defining the components early next week and to use a JMS push for the schema bridge from PACS to Physician Integration schemas.
• Completed a document in advance of the Integration Team meeting on site next week that will serve as an agenda for that meeting.  The document lists a series of topics to discuss for the client  and Allscripts e*Gate interface components that I’ve built.
• Resolving eGate and JCAPS alerts and fixing the runtime errors.
• Development of CAMS projects interfaces.

• Performed/ Documented Gap Analysis for Interfacing
  • FlowCast ADT and HBOCStar
  • ADT to EPIC
• Built Mapping document for Flowcast ADT , HBOC star ADT to EPIC
• Building JCAPS 6.2
  • Flowcast ADT Inbound interface to EPIC
  • Star ADT Inbound interface to EPIC
• Developed interfaces to route data between Epic and Radnet using JCAPS 5.1.3. 
• Development Includes JCD, OTD, Connectivity map and deployment profile. Configued Environment to talk to external systems.
• Developed interfaces to route data between Epic and PMM using JCAPS 5.1.3.
• Developed OTD's for PMM (Material Management) and Epic using JCAPS 5.1.3 OTD editor.
• Performed analysis and documented Pyxis Pocket Load/Unload to Epic ADS Load/Unload interface
• Created OTD otdPyxisChgPocket in JCAPS 5.1.3 to accommodate Pyxis Charges and Pocket HL7 messages
• Created OTD otdEpicPocket in JCAPS 5.1.3 to accommodate Epic ADS Load/Unload HL7 messages
• Created Java Collaboration Definition jcdOutPyxisPocketEpic to translate Pyxis Pocket HL7 message for Epic
• Created, built, and deployed Deployment Profile dpOutPyxisPocketEpic
• Performed alpha testing on prjOutPyxisPocketEpic using acquired data and Interface Explorer tool
• Performed troubleshooting and modifications to obtain successful acceptance of a Pyxis Pocket HL7 message in Epic Bridges.
• Validated previously created OTD's in JCAPS 5.1.3 after templates were relocated from SeeBeyond HL7 Library
• Created Java Collaboration Definition jcdOutPyxisChgEpic to translate Pyxis HL7 DFT messages for Epic
• Created, built, and deployed Deployment Profile dpOutPyxisChgEpic
• Created OTD otdEpicRxOrd in JCAPS 5.1.3 to accommodate EpicRx HL7 RDE messages
• Created OTD otdPyxisRxOrd in JCAPS 5.1.3 to accommodate Pyxis HL7 RDE messages
• Performed analysis to accommodate using a common JCD for Epic ADT going to multiple hospital facilities with Pyxis ADS.
• Completed changes to ELR ORU transformation script and associated data maps.
• Completed research of client production data and current EICU ORU transformation scripts to evaluate the potential need to implement data maps.
• Completed changes to the ELR ORU transformation script to implement initial data maps specific to HL7 critical fields.
• Trained new hires on eGate SRE MONK, incorporating Event Type Definitions, Building structures from scratch and using HL7 templates, Collaboration Rule Scripts, Developing Batch, File, TCP/IP eways inbound and outbound, Bobs and Multimodes, Dynamic Batch and DART eway, IQ manager,  IQ, IQ Administrator, JMS Administrator as well as understanding eGate directory structure and logs and understanding frequently used Unix commands.

• Mentored/Presented the Overall view of JCAPS Suite, along with each component that constitutes the project: eIndex, eXchange, eInsight, eBAM, eTL, eGate.
• Documented the Naming Convention that needs to be followed for the JCAPS components.
• Architected the JCAPS Flow.
• Architected the Exception Handling and Message Reprocessing mechanism for the JCAPS   Implementation.
• Studied and Documented existing eGate Flowcast ADT Feed as Is.
• Studied and Documented existing eGateStar ADT Feed as Is.
• Studied and Documented eGate LIS Results (Lab, Micro, Path) Feeds As Is.
• Developing JCAPS- Flowcast ADT Inbound interface.
• Coded Filter / Router.
• Incorporated XML Schema.
• Coded CDR outbound.
• Created and tested prj_DISCH_TO_LOGICR project in test environment.
• Tested prj_FR_DISCH project in test env, this is a FTP feed ADTs.
• Create and tested prj_LABOR_TO_ALLSCRIPTS project in test environment.
• Sent old ADT missing data to DEXTER using HL7 Interface Explorer.
• Removed IBUFFER inbetween LWADT and CWS so that there wont be any more data missing.
• Test prj_LWADT_TO_CWS project in test environment.
• Performed new installation of eGate SRE 5.0.5 on AIX server.
• Successfully imported v4.5.3 schema into new 5.0.5 environment.
• Created documentation outlining steps of eGate Unix server installation.
• Created documentation on how to create and configure JMS Queue Manager and Queues.
• Created new JMS Queue to start conversion of standard IQ’s to JMS Queues.
• Updated server OS to latest maintenance release to resolve JMS Queue manager issues.
• Created links between production server and upgrade server for data comparison.
• Changed logging levels on eGate components to give client desired results.
• Performed data analysis between production and upgrade servers for upgrade validation.
• Signoff of MPI data Business owners Requirements by MPI Management Committee.
• Creation of Controlled Test Scenarios for MPI Backload data.
• Unit Testing of Scenarios for specific requirements for Sunrise Clinical Manager.
• Functional and Integrated testing of MPI Static Load Interfaces. 
• Creation of Statistical throughput documentation incorporating all technical aspects of process
• Full MPI Backload Test analysis with remediation.
• Complete analysis of Test MPI Backload presented to MPI Management Committee.
• Full MPI Backload to Production with a less than .0005% Error rate of 9 million messages (3362 errors).
• Assisted Interface Management Team with realignment of staff to optimize skill sets.
• Attend CIO roundtable management meeting weekly.
• Creation of Dynamic Server Environment for dedicated development and testing of MPI Dynamic Load Process and Results Processing.
• Creation of Controlled Test Scenarios for MPI Dynamic data.
• Allocation of resources to expedite required tasks within multiple projects.
• Creation of multiple database environments (PRODCOPY2, PRODCOPY3, PRODMPI) for different staging events for Sunrise Clinical Manager.
• Unit testing of MPI Dynamic on DUG environment.
• Limited volume testing of MPI Dynamic combination of DUG/Test Environment Servers.
• Time analysis performed on MPI Dynamic results.
• Remediation testing for MPI Dynamic Interfaces.
• Unit testing of Radiology, Laboratory, Transcription Results process.
• Functional Testing using Controlled test Scenarios with Business Analysts.
• Expanded volume testing of MPI Dynamic Process.
  

• MPI Test Plan & Static MPI Load Process Review.
• Worked with MPI data Business owners for Requirement approval.
• Identification of coding issues in Static MPI translator.
• Creation of Unit Testing Scenarios for specific requirements for Sunrise Clinical Manager.
• Testing of Static MPI Translator “as is” with Scenarios to verify coding issues.
• Correction of known coding issues in Static MPI Translator.
• Unit retesting  of Static MPI Translator.
• Dataflow Verification for Static MPI Translator.
• Logic Verification for static MPI translator.
• Development of Eclipsys eLink translators for MPI
• Coding/Testing and Verification of the Enterprise Number Logic
• Migration of 27 JCAPS 5.1.3 interfaces into production from test / development
• Move JCAPS repository from Newt2 to Newt. Newt2 was given to another team and a new host will be bought for the EAI team at some point in the future.
• Continue eGate training with David and help out with a couple of issues in his HBS ADT collaboration.
• Work with Joe on Quality Compass java collaborations. This is the first set of java translations he’s written - everything else has been monk up until now.
•  Added a staging directory to the outbound batch ERMX process in eGate. This should help prevent “file collisions” with the inbound loader process running on phalen.

 

1. Move JCAPS repository from Newt2 to Newt. Newt2 was given to another team and a new host will be bought for the EAI team at some point in the future.

2. Continue eGate training with David and help out with a couple of issues in his HBS ADT collaboration.
 
3. Work with Joe on Quality Compass java collaborations. This is the first set of java translations he’s written - everything else has been monk up until now.
 
4. Added a staging directory to the outbound batch ERMX process in eGate. This should help prevent “file collisions” with the inbound loader process running on phalen.