|
Healthcare Technical Services Projects for August 7 |
- CareStream Charges are processing correctly through transmittal process.
- NYSID information is now processing
- Changed coding so Rhapsody will handle leading 0s on provider ids less than 5 characters in length.
- Asked to assist with internal Lab Charge Process using Rhapsody Engine for dataflow processing.
- Production deployment preparation with internal Medicity Team.
- Worked up outstanding Medicity Rally defects.
- Eclipsys planning for cross system merge testing.
- Eclipsys RIS ADT mapping activities.
- Created Eclipsys eLink interface documentation direct from code for Rhapsody migration project. Will take existing elink logic and perform efficiency analysis during the Rhapsody design process.
- eClinical Works practice Planner created, Primary Pilot Site-practice activated with message flow verified, and CERT version 5.3 deployed containing ADT interfaces and selected defect fixes. ADT was assigned to CERT. Transcription received approval in Development with promotion to QA expected Next week, Q/A sign-off the week after with CERT deployment the end of that week. Dropbox Template build completion scheduled next week.
- Lab – Data flow initiated from Cloverleaf to Nexus with data feed migrated from PROD to Cert Lab.
- Identified issued with OBR.7 not populating. Technical team working on a resolution to the field not populating.
- Client wide initiative for Physician satisfaction policy applied to the copy to physician matrix.
- Lab Orders HL7 2.3 Specification submitted to client.
- Path – Data flow initiated from Cloverleaf to Nexus with data feed migrated from PROD to Cert Path.
- Rad – Data flow initiated from Cloverleaf to Nexus. Data feed migrated from PROD to Cert Radiology next week.
- Currently testing Radiology dataflow and HL7 message integrity based on the Radiology Specification.
- ADT (Invision) – Interface delivered to QA. Some issues were identified with a number of these resolved. Promoted to CERT with testing of ADT scheduled for next week.
- Transcription – This is in Development at this time with projected promotion. To stay on task, QA sign-off is expected within 1 ½ weeks with deployment to CERT by end of the month.
- Anticipated result volumes across all facilities is currently being calculated by client.
- We have seen very good message flow through Lab and Radiology. There are still some testing to take place with specific identified issues (Rally Defects) currently being researched and resolved.
- Dropbox template build in development.
- All client users have access to the Baycare dropbox.
- Transcription interface rebuild required due to miscalculation of client in relation to their existing transcription interface. Working with client team to help identify efficiencies to expedite the process.
- Solution research to the issue where practices with multiple offices would like to have the OutReach Results routed to the office based on “location”.
- Multiple patient types across client systems add complexity to integration. Decisions were made regarding Grid filtering and patient type mappings. Some of this setup within Nexus and the Grid remains.
- Mined a total of 6 complete use cases from the production ADT message for remote site facility. For each use case, pulled together all ADT messages associated with a given patient visit/account into a data file, documented in the Use Cases spreadsheet each event that occurred for the given patient visit/account and pulled patient activity reports for each patient visit/account. At the end, provided detailed email to the team for using the above information to complete these use cases in the 5.65 environment for use in subsequent message comparison/contrasts.
- Meditech 5.65 Upgrade Project – For the first use case of the six that I mined from production, completed all ADM application events using the same exact patient information (except for SSN) into the 5.65 environment. Ultimately, was able to generate 5.65 messages that were analogous to the production 5.54 messages. Subsequently, completed detailed messages compares using work flow involving Interface Explorer message compare and also used Ultra-Edit text based compare to make up for some of the weakness’ of the Interface Explorer compare. Identified a handful of differences that most likely need to be addressed either with Meditech fix or e*Gate code to ensure exact matches between 5.54 and 5.65 messages.
- Meditech 5.65 Upgrade Project – Worked to create and then update the format and content of the composite message Discrepancies list which will contain ALL issues identified for ALL ministries for ALL data types so that when we are done, we have a list of discrepancies to address via Meditech fix or e*Gate coding.
- Meditech 5.65 Upgrade Project – In order to leverage the field level metrics that I previously generated, I used the metrics spreadsheets to create a new documents that should be used to check off each field that has been successfully tested for the 5.65 migration. Subsequently, reviewed all test results from first use case and updated the checklist accordingly. At the end, there were still a couple segments (DG1 and PR1) that have not been tested yet and a few fields on existing segment that have not been tested.
- Received request to answer a question regarding the uniqueness of the Filler Order Number field. Completed some research on this against production laboratory results data for all types and all sites and also worked to put the same question to the Meditech support team. Got the answers we needed from Meditech and provided response to client. Client also requested sample messages for all 4 sub-types, so pulled those from production, de-identified the patient and provider data within and shared with client.
- Worked at length to generate a list of specific questions regarding how client will handle Meditech’s particular nuances with Laboratory result messages with particular emphasis on Microbiology results.
- Received detailed request to track down the details on a specific patient’s specific lab test result HL7 message. Tracked the message down and provided detailed information to prove that the lab test event did in fact occur based on the transmit date, visit information and lab test information. It was ultimately discovered that the messages was re-processed recently causing confusion on his side regarding when the lab test was performed and where.
- Pulled production copy of the “PhysicianIntegration” schema and copied to “PhysicianIntegration_Conv” schema in order to re-synchronize production and test per request from the team once it was discovered that they were out of synchronization.
- Issue research/changes related to sunset of “Magic”. Received request to research an issue with messages backing up to the SOI ELR e*Gate transformation module. Ultimately identified that this module contained 2 subscriptions that were now obsolete based on changes that were made to sunset the “Magic” lab result feeds. Completed changes to remove the subscriptions, bounced the module, confirmed that backlog of messages was completely processed and notified the team.
 |
|
877.303.3377
The services provided by Orchestrate Healthcare will
allow us to meet the interfacing and data migration deadlines required
on a very large and critical implementation project.