Healthcare Technical Services Projects for March 05

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.