877.303.3377
|
Feb 13
2010
|
Healthcare Technical Services Projects for Feb 12Posted by admin in Untagged |
|
- 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.
Orchestrate was sensitive to our budget constraints. They were easy to work with ... overall a very upbeat and positive experience.