|
Healthcare Technical Services Projects for March 12 |
- 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.
 |
|
877.303.3377
Orchestrate Healthcare assessed our immediate issues and proposed a training solution that met our needs as well as worked within our budget