|
Jun 06
2011
|
Healthcare Technical Services Projects for June 5Posted by admin in Untagged |
|
- Preparation for Prod package deployment, review of package and issue resolution.
- Worked on the resolution of the Medicity/client Patient merge issue.
- Safety Surveillor
- Sent ADT and Lab samples to Premier
- Got Results route and Mapper completed
- Set up call with Premier
- Pharmacy Orders also sent to Premier- they now have to adjust to an RDE order message
- CareStream
- Got MFN messages configured and mapper in place for physician updates- Problem with EPIC and Morrissey interface. Also Wpic may not have the ability to transmit NY State ID # until after go live date.
- Sent samples to Jun for verification of the MFN messages sent to Carestream
- These were verified
- The MFN portion did not make the June 3rd deadline and may not make the go live date due to the Lack of NY State ID # by EPIC
- Scheduling testing is not complete because the files created with Room resources are not set up correctly. Mike D said the SER were not correct and they need to be redone. Will pass this back to Cadence group Monday as this prevented any testing completions.
- Lab Result messages are configured to process to Carestream results
- Set up the RHIO route- get positive acknowledgements in return
- Made adjustments to the NK1 phone number fields as they have a size limitation in Carestream- they are formatted differently than the phone fields in the PID segment.
- Biomedical
- ADT is working as are Results
- Completed test script for ADT
- Made changes in mapper to only send the 12 desired tests from Softlab instead of all tests in the message containing the one desired one.
- Telerehab
- ADT is working
- Completed Test Script for ADT
- Meditech 5.6 Upgrade Project – Message Metric Utility – Completed series of changes to the e*Gate message metric utility to add HL7 Field descriptions to the output report (via data map file with descriptions pulled from Meditech HL7 specifications and HL7 Standard document when Meditech specification document was not complete). Also, added separate reporting that adds Patient Type in addition to Message Type and Trigger Event to the message metric breakdown.
- Meditech 5.6 Upgrade Project – Message Metric Generation for ADT interfaces – Pulled 30 days worth of production data for each ADT interface (Midas and Pyxis) for each ministry that is currently live on 5.5. Pushed each set of data through the message metric utility and converted the output to Excel spreadsheets (via CSV imports from output text files). Modified each Excel spreadsheet to include two worksheets separating the regular Message Type / Trigger Event breakdown from the breakdown that adds Patient Type. Sorted all of the output within the spreadsheet to make things more human readable. Completed the generation of all metric spreadsheets for all ADT interfaces and moved the resulting spreadsheets up to this project’s folder on the X: drive per Jan’s request.
- Meditech 5.6 Upgrade Project – Test Status Spreadsheet for ADT interfaces – Using the message metric spreadsheets, updated the Test Status spreadsheets to reflect the HL7 ADT segment level content for each ADT interface (Midas and Pyxis) for each ministry. In total, there are 5 spreadsheets each with a separate HL7 ADT segment level content matrix for both the Midas and Pyxis ADT feeds. Copied the updated spreadsheet up the X: drive.
- Meditech 5.6 Upgrade Project – Acquire/Verify access to Meditech web-site, 5.5 environments and 5.6 environments – Worked at length to assess the level of access I currently have for the ADM and MIS modules within both 5.5 and 5.6 environments. Pulled together list of access that I currently do not have in the 5.5 environments and sent off the list to the project manager requesting the necessary access/permission changes. Once the changes were complete, verified my access. Also, once access was granted to the 5.6 environments, started poking around in that environment after receiving good direction from a team member on how to access the new environments via Citrix web client.
- Support for the JMS Null Pointer Exception issue – Continued to work with Oracle support on this issue with no success trying the steps suggested by Oracle support. Ultimately, solved this problem by consolidating all of the new e*Gate modules for the Senior Services schema under the “PressGaney” control broker. This eliminated the AEGT16 participating host from the schema. I had to create the Cluster Resource for the “PressGaney” control broker, but once that was complete, the issue was resolved. No more JMS exceptions and was able to continue his development and testing. Closed the associated Oracle Service Request once the issue was resolved.


I am very impressed with Orchestrate Healthcare’s professionalism ... industry skills and also with their communication — they are responsive experts.