|
Healthcare Technical Services Projects for July 31 |
- Completed Datagate to Rhapsody test Scripts and testing.
- Completed remaining client single system merge testing. Documented findings.
- Final cleanup of client providers in SCM.
- Review of ADT translations to RIS and testing preparation.
- ePI and RIS related meetings and correspondence.
- Revision and review of ePI issues list
- continued calls with Medicity PM to track status & timeline, verified interface will be live with ProAccess 5.3 upgrade and forwarded screenshots as examples to client.
- Conducted meeting to vet Use Cases, User Scenarios, and IHE Profiles documentation to provide direction to vendors for on-site meeting on Aug 8 with Medicity & Greenway, forwarded approved draft documentation to vendors with requests for more information & missing dates.
- Completed VPN configuration for client to access Medicity Grid Hospital Node & Orders Work List, tested & verified connectivity.
- Conducted training session with IT support staff for PDL, provided training reference guides to eHP Program Manager & Director
- Attended technical conference call on Wednesday 7/27 to discuss next steps for the project, specifically the sending to the initial 60 day production data backload for each data type.
- Arranged and participating in meeting to discuss the issues with Meditech’s HL7 outbound interface for BBK and PTH lab result messages and their impact on the Epic project.
- Completed research of several BBK and several PTH production lab results, then sent out email to the team describing the format issues I encountered along with the “corrupt” PV1 issue I observed. My research essentially confirmed what the internal analyst already discovered 3 years hence, but was able to communicate these issues to the entire team before any commitment was made to share this data until Meditech can be engaged to resolve the format and corrupt PV1 segment.
- Began work to pull from the data archives 60 days of data for all six ministries and all 4 data types over to the ACN015 server’s C: drive in preparation for the backload which will need to be turned on as soon as the SOW. Also, started the e*Gate module builds for the components that will be minimally required to support the backload. To start off, I have defined 4 new event types, 4 new outbound HL7 e*Ways and 4 new feeders. Began development on simple Collaboration that I will use to ensure that all messages MSH.4 value is consistently sent based on the message source ministry on their way out to target system. Completed testing and moved into place within the ADT feed.
- Completed changes, testing and production implementation based on a change to filter out NTE segments (under OBX segments) that are cluttering up their displays with redundant reporting the performing laboratory name and address (already reported in OBX.15).
- Began production data research focused on the Meditech ITS value OBR.20 (Report Department) which is the field that will be used to distinguish what client considers to be Radiology Reports from what it considers to be Transcribed reports. Meditech sends all ITS report types via the same data feed (port) so e*Gate routing rules will be necessary to route them to MCHIE via separate data feeds (ports). Completed research, yielding a list of Meditech Report Departments that are currently being used for each ministry.
- During my research of the production ITS report data, discovered that Meditech is not sending “HIM” (OBR.20) reports outbound. Communicated this information to client, who confirmed my findings and added to the list “CAR” reports which were also not turned on. Subsequently, completed e*Gate routing and code research necessary to identify the modules that process ITS reports in order to ensure that the change to turn on “HIM” and “CAR” reports will result in no impact on these modules and associated interfaces. Confirmed that no changes were necessary (one BOB was identified and it had logic to only send reports for a specific list of Meditech Report Departments which did not include “HIM” or “CAR”), but that changes would be necessary for one BOB at remote site for specific provider practice interface. I made the changes in TEST to ensure that the new “HIM” and “CAR” reports will not be sent to the practice once they are turned on and completed series of tests to ensure that the code changes were sound. Subsequently, moved these changes into production and notified the team once that was complete. By the end of the week, reports were turned on to all outbound facilities.
 |
|
877.303.3377
The expertise provided by
Orchestrate Healthcare has been invaluable to my company.