|
Healthcare Technical Services Projects for Oct 24 |
- Transolutions New Report Type – Attended status conference call with the
- Submitted initial draft of future radiology dataflow for the different healthcare facilities. Comparing this dataflow to the contract, to make sure that they are in sync.
- Review completed on CT and XR test plan documents.
- Submitted SR to Cerner regarding configuration related questions/changes.
- Documented electronically, the results of the US testing on the test plan spreadsheet.
- Met with Special Medicine group to gather questions regarding future state interface functionality.
- Reviewed future state cardiology-related interface diagrams.
- In eGate TRE (DataGate), moved 51 interfaces to multiple production table environments in order to accommodate Sun/Solaris system pfile limitation. Created a fourth production table and moved interfaces around for maximum utilization. System downtime which included 2 system reboots as well as this move, was performed in under 2 hours. Validation of production interfaces was completed in less than one hour.
- Supported Soft Lab interface implementation work.
- Primary Support Resource (PSR) in supporting first clinic go-live.
- Monitoring queues in Epic Bridges and JCAPS 513.
- Solved some issues in JCAPS as messages were queued up because of bad message.
- Performed testing of 3 interfaces in JCavaCAPS for ADT, Lab Orders and RX Orders.
- Performed some test scenariosfor ADT in EPIC with the help of Colleague.
- Created deployment profiles for all about 180+ interfaces to point to dev box.
- Assisted in Eclipsys – Cerner ADT Testing.
- Coded and Implemented Charge File creation and ftp translators from Cerner to Eclipsys.
- Researched the PNS, CPT, NDC, and UBS upload and add/edit functionality of the Eclipsys PFM product.
- Worked with Nash staff to provide file formats for upload and add/edit data to be used by report creators.
- Assisted in the identification issues with the existing methodology used to assign physician IDs on SoftMed and the creation of a resolution process for physicians that practice at multiple locations and want to receive their results via the Medicity Novo Grid.
- Assisted in the creation of a Medicity Implementation Analyst job description.
- Contacted AllScripts EMR vendor to discuss interoperability with Medicity and the client’s HIS. Established a go-forward plan of action.
- Created a Business Approval document that will be used to document and denote approvals at the director and "C" level along with task responsibilities, task timelines and accountability.
- Created a Medicity Initial contact document that will be used to assist novice or new employees in what questions to ask, items of discussion and items to track as well as visual talking points on Medicity as well as client methodologies.
- Integration Team Meeting – Attended status call on Monday 10/18.
- Datanex – Attended kick off meeting for this project on Monday 10/18.
- Medmined– Continued working with client to support their build. The focus of our single session this week (Thursday 10/21) were procedures for performing file (feeder) to file (eater) testing for all three of the ADT collaborations (ADT, A17 and A34). We also covered developer/unit testing topics like using the e*Gate Manager, dropping files for testing, viewing log file content for testing confirmation, viewing test message output, etc.
- Training/Tutorial Sessions – Completed some preparatory work on Tuesday morning then held four WebEx sessions Tuesday through Friday. Used the training agenda document and “Training” schema data flow diagram document previously built for training sessions as guide for this set of sessions. By the end of the week, I had demonstrated the build steps for the "Training" schema and demonstrated a series of message tests. Next week, training will continue actually allowing students to build the "Training" schema themselves with my guidance.
- Datanex– Began the development of the client Interface Requirements specification document for these interfaces. Completed build of eGate infrastructure (ADT, A17 and A34) for this interface for client in the eGate “conversion” environment. Built the initial collaboration rule class for the ADT, performing for now straight copy of the segments that are required by the Datanex inbound ADT interface. Plan is to complete initial testing and to send a sample ADT file to Datanex with examples of each of the Meditech ADT event types.
- Datanex – Completed detailed review of the Datanex FTP Setup and Data Delivery Protocol document. Completed build of basic e*Gate FTP interface using the Batch e*Way for Java to be used for initial connectivity test and will serve as the basis for the more complex solution that will support the sending to Datanex each of the separate Meditech data extract files from separate directories (defined based on the Datanex FTP document).
- e*Gate 5.0.5 Update One – Completed build of an Excel spreadsheet to inventory/list all of the collaboration rule classes that are defined to the production e*Gate schemas for client. The build started with generating e*Gate Designer "View Summary" report extracts for the "Collaboration Rules" report for each production schema so each extract contains a list of collaboration rule classes defined to a particular schema. Modified the "shared" directory to mirror the list and specific names for each e*Gate production schema. Next steps are to copy production collaboration rule .java files over to the “shared” directory in preparation for the global searches that will be done for the known issues identified during our call last week.
 |
|
877.303.3377
I am very impressed with Orchestrate Healthcare’s professionalism ... industry skills and also with their communication — they are responsive experts.