877.303.3377
|
Apr 29
2011
|
Healthcare Technical Services Projects for April 29Posted by admin in Untagged |
|
- RIS Charges mapping and routing completed.
- RIS ADT mapping and routing completed.
- RIS Scheduling mapping and route completed
- Developed a plan for handling charge files with Brian on site to minimize changes other systems will be required to make.
- Completed and tested the Charge file processing with the current file layout. Carestream will add an MRN column which is required for EPIC.
- Added a process to take the new file and strip out the MRN column and save so the old IDX system will not have to be altered to accept the new column.
- Completed ADT route and mappings. Discovered some issues with ADT^A18 merge messages and the ADT^A45 message has to become an ADT^A18 which then leads to the issues the system appears to have accepting A18s.
- Started looking at the specs and requirements for the following interfaces:
- Wittbio Cath Lab
- Safety Surveillor Infectious Disease control system
- Clinipro Diabetic Monitoring system
- Scottcare TeleRehab
- Worked on trouble shooting some save and restore issues in Rhapsody.
- Worked on some lookup table issues in Rhapsody.
- Provided Rhapsody oversight for one of the new team members.
- Prep for Medicity cert deployment.
- Reconciling all Medicity QA, Cert and Prod packages to schedule weekly deployments.
- Analysis of CORHIO QA/Cert/Prod packages.
- Cert deployment, successful. One defect remains open for the client DB Parser, which was resolved later in the week.
- Attended Epic Integration Team Meeting
- Made progress on ADT from EPIC to Impac Mosaiq Radiological Oncology System Route .
- Made progress on Technical Charges interface from Impac Mosaiq Radiological Oncology system to Epic .
- Thoroughly reviewed all documentation available on the Immunization Registry interface.
- Completed SCM registration/update test plan build.
- Assist with provider load from Standish/Tawas into SCM.
- Interfaces built for Epic Inbound Testing:
- Muse DFT Charges to Epic
- SiemansRMS DFT Charges to Epic
- Documentation
- EPIC/Rhapsody Project Peer review
- Rhapsody testing
- Mapping and Design requirements
- Epic Radiology Results Testing Session meeting
- Epic Sunquest Results Testing Session meeting
- Epic Weekly Interface Team meeting
- Epic Integration Project Plan issues Meeting
- Radiology Interface Vrad Team Meeting
- Tested Route ADT from Star HLO
- Built Route to handle ORU results from Vrad to Mckesson Star
- Conversion for eMDS Lab Results Interface – Met with client to discuss the interface which they developed a while back and continues to maintain over time. Pulled the production copies of all ETDs and Collaboration Rules and moved them into place in the TEST environment on AEGT03. On AEGT03, completed changes to the collaboration and collaboration rules in order to synchronize the test modules on AEGT03 with the production modules.
- Conversion for eMDS Lab Results Interface – Without changing the actual collaboration rule code added detailed comments for each business rule within the two key collaboration rules “crMTC_RTR_DAYHFV6.class” (Routing) and “crPhysician_ORUv2.class” (Transformation) for the Meditech Lab Results interface to eMDS for TMG. Using the detailed comments added to the code, created document to list all key routing and transformation rules that may require changes for the conversion from Magic to C/S for the Lab Results interface. Subsequently, pulled a few days worth of production data and pushed it through the interface modules on AEGT03. Also, worked with the client to identify the Excel spreadsheets on the X: drive that document the current (Magic) vs. new (C/S) lab test/result mnemonics and descriptions which I will share with TMG’s eMDS team after tailoring it to the interface impacts for lab test mnemonics (OBR.4) and lab result mnemonics (OBX.3).
- Conversion for eMDS Lab Results Interface –Was provided a custom version of the Conversion interface questionnaire and I sent that questionnaire to the physician requesting that he review/respond to the questions and also to get things rolling for the initial conference call. Received feedback from various team members and subsequently requested availability for initial conference call and was able to schedule a call for Tuesday 5/3 at 1:00PM. Included on the call will be a representative from EMR vendor eMDS as well as client representative for the eMDS system.
- DRA SFTP interface for client site – Was finally able to test the ”get” collaboration for this interface once the first production ”dra_complete” claims file was made available on the Sentry SFTP server. Worked with colient to confirm that I should copy it to the NEBO server in the agreed upon NEBO folder and once I was given the go ahead, ran the “get” collaboration and it successfully completed all steps to “get” the file from the Sentry SFTP server and copy it to the designated NEBO folder. Later in the week, completed a series of manual runs for both the “put” and “get” steps. Currently waiting for confirmation from client before setting the day forward e*Way schedule for this interface. The client prefers manual runs of the interface until issues with NEBO processing are worked out and implemented. Also, completed a change to ensure that empty files are NOT sent to Sentry for the “put” collaboration. I made this change when I discovered that the Meditech claims file deliver process sometimes delivers empty files which should not be sent to Sentry.
- Support for Physician interface go-live – Worked with provider contact to identify issue with the HL7 message exchanged with physician office’s lab results interface. Identified via log file research that the outbound HL7 e*Way was reporting an MLLP rules violation (EOD character not received) perpetrated by the downstream’s system’s HL7 inbound server/listener.
- Support Lab Mnemonic datamap file issue – Received request from client to research issue they were experiencing with an e*Gate datamap file. At first glance, could not identify any issues with the file, so opened Service Request with Oracle support describing the issue and attaching the associated datamap file.
The expertise provided by
Orchestrate Healthcare has been invaluable to my company.