|
Mar 20
2010
|
Healthcare Technical Services Projects for March 19Posted by admin in Untagged |
|
- 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



Orchestrate Healthcare assessed our immediate issues and proposed a training solution that met our needs as well as worked within our budget