877.303.3377
|
Feb 27
2010
|
Healthcare Technical Services Projects for Feb 26Posted by admin in Untagged |
|
- Completed a review/revise of the e*Gate production implementation plan
for client after receiving some great feedback from review team regarding the
initial draft.
- Completed build of the client e*Gate interface modules in PROD on
Thursday night 2/25. Completed initial
test of connectivity prior to starting the modules. Completed the final ADT backload as part of
the production implementation steps prior to the cutover to the live ADT feed.
- Completed successful re-test of the A06 and A12 transactions after
receiving feedback from Intego that their application did not properly handle
the original test. They modified their
code to properly handle the A06 (much like an A01) and also the A12
(Cancel/Undo Transfer after A02).
- Modified the interface modules in TEST to pull in ADT messages from
PROD. Subsequently turned on the live
ADT to Intego on Tuesday morning 2/23 and then monitored the interface
throughout the week. No issues to
report. Followed up with the team and
received positive feedback, so will continue with the plan to cutover from TEST
to PROD next Monday night 3/1.
- Completed the first draft of the production implementation plan for
this interface.
- Worked with the team to schedule two integrated testing sessions for
Monday 3/1 and Tuesday 3/2
- Received report from a client ancillary site that ORU reports where
being duplicated within Allscripts.
Completed detailed research of the e*Gate log files, corresponded at
length with Allscripts and also worked directly with client lead regarding
possible VPN issues. Client lead agreed
to turn on a packet capture and to adjust the connection timeout from 12 hours
to 7 days to see if this could rule out the VPN as a contributing factor. Based on my research into the issue,
presented options for pursuing a solution.
The first option involves additional research to review possible flaws
in the implementation of an HLy MPPL Server/Receiver in Allscripts. The second option involves using a custom
e*Way connection that I have that implements an HL7 MLLP client and would
replace the existing TCP/IP HL7 e*Way Adapter.
The custom e*Way connection would make it possible to report exactly how
this Allscripts flaw is violating the rules of HL7 MLLP and also provide an
avenue for customizing the e*Way connection to handle its eccentricities
without causing duplicates within Allscripts.
- Using Remote Assist, I conducted eGate Training for new hires for the
client.
- Create new Batch modules
- Modifed existing code in response to user request
- Review specifications for new interfaces.
- Manage assigned tickets in client’s incident reporting system
- Conduct tests
- Report results
- Modify code in response to test results
- Organize move to production utilizing client’s go live procedures
- Created new Project in JCAPS 5.1.3 to
process Lab Result messages to the ancillary Clinical Work
Station system
- Created new Connectivity Map for Lab
Result messages to the ancillary Clinical Work
Station system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for Lab Result messages to the ancillary Clinical
Work Station system in JCAPS 5.1.3
- Created and configured new Deployment
Profile for Lab Result messages to the ancillary Clinical Work
Station system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for Lab Result messages to the ancillary Clinical
Work Station system in JCAPS 5.1.3
- Created new custom Object Type
Definition to be included on the EpicAdt
OTD
- Created new Project in JCAPS 5.1.3 to
process Vascular result messages to the ancillary Clinical
Work Station system
- Created new Connectivity Map for Vascular
result messages to the ancillary Clinical Work
Station system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for Vascular result messages to the ancillary Clinical
Work Station system in JCAPS 5.1.3
- Created and configured new Deployment
Profile for Vascular result messages to the ancillary Clinical
Work Station system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for Vascular result messages to
the ancillary Clinical Work Station system in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process result messages to the ancillary Clinical Work
Station system
- Created new Connectivity Map for
processing result messages to the ancillary Clinical Work
Station Alpha system and configured
with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing result messages to
the ancillary Clinical Work Station Alpha system
- in JCAPS 5.1.3
- Created and configured new Deployment
Profile for processing result messages to the ancillary Clinical
Work Station Alpha system in JCAPS
5.1.3
- Performed build and deploy on
Deployment Profile for processing result messages to
the ancillary Clinical Work Station Alpha system in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process result messages to the ancillary Clinical Work
Station Beta system
- Created new Connectivity Map to
process result messages to the ancillary Clinical Work
Station Beta system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing result messages to
the ancillary Clinical Work Station Beta system in JCAPS 5.1.3
- Created and configured new Deployment
Profile for process messages to the ancillary Clinical Work Station Beta system
in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for process messages to the ancillary Clinical Work Station
Beta system in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process result messages to the ancillary Clinical Work
Station system
- Created new Connectivity Map to
process result messages to the ancillary Clinical Work
Station system and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition to process result messages to
the ancillary Clinical Work Station system in JCAPS 5.1.3
- Created and configured new Deployment
Profile to process result messages to
the ancillary Clinical Work Station system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile to process result messages to
the ancillary Clinical Work Station system in JCAPS 5.1.3
- Performed ADT connectivity testing
between CareCast-JCAPs 5.1.3-Epic
- Performed Orders connectivity testing between
CareCast-JCAPs 5.1.3-Epic
- Performed ADT connectivity testing
between McKesson-JCAPs 5.1.3-Epic
- Performed Orders connectivity testing
between M2-JCAPs 5.1.3-Epic
- Created new Project in JCAPS 5.1.3 to
process ADT messages to the ancillary Midas system
- Created new Connectivity Map for
processing ADT messages to the ancillary Midas system and
configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for processing ADT messages to
the ancillary Midas system in JCAPS 5.1.3
- Created and configured new Deployment
Profile for processing ADT messages to
the ancillary Midas system in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for processing ADT messages to
the ancillary Midas system in JCAPS 5.1.3
- Gathered data requirements from M2, Onchology, PACS
system team.
- Configured FTP Inbound/Outbound eway to get/put the files from/to
FTP server.
- Went through existing interface logic for filtering criteria and to
understand existing logic.
- Developed OTD's for Orders/results/charge interface data to
get from/send to Epic.
- Configured HL7 Tcpip eway to send data to and from Epic, Onchology, M2
& PACS system.
- Developed Interfaces to & from send real time data to
Epic, Onchology, PACS interfaces.
- Developed Interface to send ADT, Orders, Results &
Charges data to & from M2, MLA, PACS & Onchology systems.
- Developed technical spec for ADT, Orders, results &
Charges data for Onchology, M2, MLA & PACS systems
- Created environment for Intefaces.
- Tested ADT, Orders, Results & Charges data flow between Epic,
Onchology, MLA, PACS systems.
- Environment interaction: JCAPS 5.1.3, Epic, HL7 2.5,
MLA, M2,ONCHOLOGY, PACS, Interface explorer, FTP server, AIX.
The expertise provided by
Orchestrate Healthcare has been invaluable to my company.