877.303.3377
|
Feb 20
2010
|
Healthcare Technical Services Projects for Feb 19Posted by admin in Untagged |
|
- Modified Java Collaboration Definition
to extract email addresses from file on
server instead of them being hardcoded.
- Modified, validated, and compiled Java
Collaboration Definition for EPIC ADT in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile EPIC ADT JCAPS 5.1.3
- Created new Project From Epic to MedAptus
in JCAPS 5.1.3 to process Epic ADT messages to MedAptus ancillary system
- Created new Connectivity Map From Epic
to MedAptus and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition From Epic to MedAptus in JCAPS 5.1.3
- Created new HL7 TCPIP External System From
Epic to MedAptus under designated domain in JCAPS 5.1.3
- Created and configured new Deployment
Profile From Epic to MedAptus in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile From Epic to MedAptus in JCAPS 5.1.3
- Created new Project for ADT from Epic
to Optimum in JCAPS 5.1.3 to process ADT messages to ancillary Optimum system
- Created new Connectivity Map for ADT
from Epic to Optimum and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for ADT from Epic to Optimum in JCAPS 5.1.3
- Created new Batch Local File External
System for ADT from Epic to Optimum under designated domain in JCAPS 5.1.3
- Created and configured new Deployment
Profile for ADT from Epic to Optimum in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for ADT from Epic to Optimum in JCAPS 5.1.3
- Created new Project for ADT from Epic
to RapidLinkGVSV in JCAPS 5.1.3 to process ADT messages to ancillary RapidLink
system
- Created new Connectivity Map for ADT
from Epic to RapidLinkGVSV and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition for ADT from Epic to RapidLinkGVSV in JCAPS 5.1.3
- Created new HL7 External System for
ADT from Epic to RapidLinkGVSV under designated domain in JCAPS 5.1.3
- Created and configured new Deployment
Profile for ADT from Epic to RapidLinkGVSV in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile for ADT from Epic to RapidLinkGVSV in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process charge messages from the ancillary RapidLink system
- Created new Connectivity Map to handle
the charge messges from RapidLink and configured with needed components in
JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition to handle the charge messges from RapidLink in
JCAPS 5.1.3
- Created and configured new Deployment
Profile to handle the charge messges from RapidLink in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile to handle the charge messges from RapidLink in JCAPS 5.1.3
- Created new Project in JCAPS 5.1.3 to
process charge messages from the ancillary Xim system
- Created new Connectivity Map to handle
charge messages from Xim and configured with needed components in JCAPS 5.1.3
- Created, validated, and compiled new
Java Collaboration Definition to handle charge messages from Xim in JCAPS 5.1.3
- Created and configured new Deployment
Profile to handle charge messages from Xim in JCAPS 5.1.3
- Performed build and deploy on
Deployment Profile to handle charge messages from Xim in JCAPS 5.1.3
- Gathered data requirements from PMM Inventory team.
- Configured FTP Inbound eway to get the files from FTP server.
- Developed OTD for Inventory data to get from Epic.
- Configured HL7 Tcpip eway to send data to and from Epic system.
- Developed Interfaces to & from send real time data to
Epic interface
- Developed Interface to send ADT, Orders, Results &
Charges data to & from Cerner Radnet, PACS
- Developed OTDs
for Cerner Radnet Adt, Orders, Results & Charges data(PMM)
- Developed
technical spec for ADT, Orders, results & Charges data to &
from EPIC
- Created
environment for Intefaces.
- Environment
interaction: JCAPS 5.1.3, Epic, HL7 2.5, Cerner Radnet, PMM, Interface
explorer, FTP server, AIX.
- Corresponded with the Financial team lead regarding “Medicaid” codes,
explaining the State requirement and the methods used to identify a preliminary
list of insurance plan codes that are considered “Medicaid” codes within
Meditech. She provided a short list of
the Medicaid codes that are now. As a
result, I updated the code to eliminate the data map file and simply check
against the standardized list of Medicaid codes for all ministries.
- Updated the code to consolidate the data map files for the main campus and
lab facilities so that the CLIA, Description, Address and Phone data are now
maintained in a single data map file.
- Updated the e*Gate Java code to load the data map file data into
“Hashmap” objects that will available in memory across invocations of the
“executeBusinessRules” method as opposed to performing data map lookups for
each invocation as messages are received.
This greatly improved the performance of the collaboration rule script
based on a controlled test to measure the throughput before and after the
changes. I made this change because the
expected daily message traffic is substantial based on the fact that all six
ministries will be feeding lab result messages through the collaboration rule
script.
- Completed changes to merge transaction processing based on detailed
testing of the various merge transactions supported by Meditech and also the
Intego HL7 requirements for merges per Intego.
In short, Meditech delivers the previous Account Number in MRG.1 and
Intego expects it in MRG.3 per the HL7 Standard. Meditech delivers the previous Account Number
in MRG.1. So, changed the script to map
MRG.1 to MRG.3 for the A18 (Account Number Merge) transaction.
- Completed basic message testing working with Larry Meadows who verified
that each ADT transaction was properly processed by the Intego
application. Testing this week included
merge transactions for both Account Number (A18) and Medical Record Number
(A40/A44) as well as testing of Cancel Transfer (A12), Pre-admit (A05) and
Outpatient to Inpatient Transfer (A06).
- Prepared and researched process, then began the backload of ADT
messages from production Meditech for client into the production server
starting from 2/1 forward through Friday 2/19.
From this point until the cutover next week to the production eGate
server, will continue to pull and send the production “eater” files for ADT’s
as they become available from the “eater” e*Way. Each file contains 10,000 ADT messages and
are closed/completed approximately once every two days.
- Completed the first draft of the
client’s e*Gate production implementation plan.
Bookmark
Email This
7 Comments
 firleng
March 26, 2011 118.41.159.132 Votes: +0 |
Thanks for sharing your article, very support you continue to publish more articles. Thanks.Also share some some great fashion product, hope you like it.homme neckties report abuse
vote down
vote up
|
 dresses
April 09, 2011 122.194.54.45 Votes: +0 |
Thanks for sharing your article，aa report abuse
vote down
vote up
|
 sale
April 09, 2011 74.82.188.93 Votes: +0 |
Thanks.Also share some some great fashion product, hope you like it.http://www.google.com homme neckties google report abuse
vote down
vote up
|
|
sale
April 09, 2011 74.82.188.93 Votes: +0 |
[http://www.google.com google] report abuse
vote down
vote up
|
 bags
April 09, 2011 59.174.193.134 Votes: +0 |
nsactions supported by Meditech and also the Intego HL7 requirements for merges per Intego. In short, Meditech delivers the previous Account Number in MRG.1 and Intego expects it in MRG.3 per the HL7 Standard. Meditech delivers the previous Account Number in MRG.1. So, changed hehou report abuse
vote down
vote up
|
 nicy
April 09, 2011 59.174.188.71 Votes: +0 |
louis vuitton report abuse
vote down
vote up
|
|
bags
April 09, 2011 59.174.193.134 Votes: +0 |
homme neckties report abuse
vote down
vote up
|
Write comment
Orchestrate was sensitive to our budget constraints. They were easy to work with ... overall a very upbeat and positive experience.