877.303.3377
|
Jul 18
2011
|
Healthcare Technical Services Projects for July 17Posted by admin in Untagged |
|
- Continued preparation of Rhapsody test Scripts and testing.
- Production remediation meeting and sent BOM for Prod Deployment for review.
- Reviewed all in process data sender’s code sets (with Myriah) for
- • Participated in the following discussions:
- RIS ADT Mapping call
- Weekly ePI status call
- Weekly RIS status call
- • Updated the RIS ADT mapping document to describe each translation variable coming from three registration system
- • Created provider load file for single facility, in preparation for the 7/18 activation of this facility with SCM core.
- • Scheduled Campus wide merge testing calls.
- Prod remediation meeting and sent BOM for Prod Deployment to Preston for review.
- Kick-off or Medicity orders plan.
- Reviewed all in process data sender’s code sets for corrections to be made prior to cert deployments.
- Working to complete cert package, defect failed QA.
- Tracking QA packages and other outstanding defects that need to be addressed.
- Continued preparing Epic to Orion Rhapsody Test Scripts and testing.
- Approval of Phase 1 Medicity results processing by client. Project Plan finalized and distributed to the Medicity client team.
- Met with client to determine port assignments and connectivity timeline for Medicity Results inbound.
- Updated Medicity Project workbook. This workbook is used and shared with client showing current contacts, issues, pilot medical facilities, pilot practices, meeting schedule, and Organizational structure.
- Met with client to discuss the new e*Gate Update 2 environment (ACN015/ACN016). Shared with her the Installation Steps/Notes document and walked her through the documented steps for copying a schema from the current environment over to the new ACN015/ACN016 environment. Continued to provide support and feedback throughout the week for any questions that they had regarding the ACN015/ACN016 environment or the VM configuration for their lap tops.
- Received request to investigate issue with code for Transolutions interface for the conversion. Client attempting to set up the code to handle OBR.28 (Copy To) processing per Meditech inbound ITS HL7 requirements and to handle the case when Transolutions returns a CC provider without a provider mnemonic. Initially, client was experiencing an String index out of bounds exception, so I researched the code, modified it to eliminate the exception and to meet the requirements for OBR.28 processing and turned it back over to Larry once the testing was complete and successful.
- Researched the heat log for this work request and spun my wheels a bit here because of the confused and verbose nature of each update to the heat log. Ultimately, worked out the correct port to use and how to make the routing change happen. Subsequently, emailed client requesting a time early next week to schedule the implementation of this routing change.
- Worked to help client understand the formal process required by existing Engine for setting up each ministry on the system’s SFTP interface. Sent out multiple detailed emails describing the role of e*Gate within the interface framework and the dependency on Meditech extract jobs to generate the file and for the establishment of a drop-off directory for the file that is retrieved/returned.
- Received request to make a change to the interface mapping for OBX.15 (Producer). client wanted to see the “Description” instead of the “Code” for the performing laboratory (called Producer in HL7 vernacular). Completed the change and tested it before moving it into production. Also, worked with him in an attempt to investigate the issues he is experiencing with the “Quarantine” folder for patient matching for inbound lab results to his Medinformatix system. Ultimately, helped the client realize that the limitations are with the patient trait matching business rules on the Medinformatix side and that there was nothing I could do with the message format to avoid the amount of traffic he sees hitting the “Quarantine” folder because most of the lab results he receives from hospitals are for patients that do not yet exist in his Medinformatix patient index.
- Completed work to document Meditech delivery service information (MIS Outbox) for all outbound interfaces defined within the Meditech LAB database which includes both Lab Orders and Lab Results. Subsequently, completed work to generate field level detail message metrics for both each ministries lab orders and lab results interfaces.
Orchestrate Healthcare assessed our immediate issues and proposed a training solution that met our needs as well as worked within our budget