877.303.3377
|
Apr 02
2011
|
Healthcare Technical Services Projects for April 2ndPosted by admin in Untagged |
|
- NPR Extract Conversion. Completed final change to the e*Gate code for this interface to remove support for Charge Categories and CPT Codes (ZDG.1, ZDG.2 and ZDG.4). Subsequently, supported final round of integrated testing which was successful. On Wednesday 3/30 completed build/implementation of the e*Gate code in the production environment in advance of the conversion go-live on 4/1.
- State ELR Conversion. Completed changes in production for e*Gate module “bobSOI_ELR_TRX” to add new subscription for LAB results messages and modified the collaboration rules to support routing the messages within the ELR HL7 daily batch file.
- e*Gate Update Two. Completed the e*Gate SRE v.5.0.5 Update 2 installation for ACN015. Installed pre-requisite JDK 1.6.0_19 on the ACN015 C: drive. Installed registry host, participating host and GUI’s to logical server AEGT11T F: drive. The first attempt to install the software was unsuccessful due to an insufficient allocation of disk space for the logical drives (1.0 GB for each drive). As it turns out, the full installation of the e*Gate software required 1.2 GB of disk space. Subsequently, worked to allocate additional space (5.0 GB for drives targeted for just participating host and 10.0 GB for drives targeted for the complete install – Reg, Part and GUI’s) for each of the drives. Second attempt to install the software to ACN015 was successful since space issues were resolved.
- e*Gate Update Two. Completed steps to copy of the “Test” schema (via .rdb file and repository directory direct copy) from AEGT023 to AEGT11T. Renamed the schema, created user accounts for all members of the team, committed/promoted datamap files from current environment’s “default” schema to new enviroment’s “default” schema, renamed and updated hostname for schema’s participating host to be AEGT11T, updated “Run As User” parameter for each defined e*Gate module, updated DB path parameter for each JMS IQ Manager to point to the F: drive (instead of O: drive for current environment) and updated host name to point to AEGT11T for each JMS e*Way Connection.
- e*Gate Update Two. Built temporary BOB (copied from existing Meditech to Epic RAD Results transformation/routing BOB) that uses call to “rawInput()” since the original BOB did not include code that calls “rawInput()”. Recompiled the Java ETD’s that it uses to unmarshal/marshal HL7 RAD Results messages aqnd recompiled the collaboration rules (in order to compile each against JDK v1.6.0_19). Ran a test message through the BOB and the message was processed successfully and the “rawInput()” call successfully retrieved and logged the payload of the message. Need to open an issue with Oracle to understand better why the documentation states that all collaboration rules that use “rawInput()” must be updated to call “enableSaveInboundImage()”.
- e*Gate Update Two. Completed creation of the cluster resources for the AEGT11T registry, “Epic_Test” control broker and “Epic_Elgin_Test” control broker using the Failover Cluster Manager for Windows Server 2008 R2. Copied control broker start-up scripts from AEGT023 and modified them to accommodate the new Update 2 environment. Successfully tested stopping/starting the registry using the new Resource and used the new control broker resources to start/stop the control brokers for the testing I completed for the “rawInput()” issue. Use disaster recovery documentation as my guide for determining the proper Resource configuration settings for each component.
- e*Gate Update Two. Opened issue with Oracle support to see if it is even possible to install two different versions of the e*Gate GUI’s (Designer and Manager) on the same workstation. Received immediate feedback that clearly stated (and even pointed to FAQ that directly addresses this very question) that it is not possible to install both e*Gate SRE v5.0.5 GUI’s and e*Gate SRE v5.0.5 Update 2 GUI’s on the same workstation. Plan is to move forward with the approach of configuring a lap to use logical partitions (two of them) so that the current version of e*Gate can be installed on one partition and the Update 2 version can be installed on the second partition.
- Rhapsody Datagate Conversion. Route and Documentation Review Datagate Interfaces, Naming conventions, Site layout, requirements
- Rhapsody testing
- Epic Integration Implementation Activities including Documentation review, Mapping and Design requirements, Epic and Medical Imaging meeting as well as the Epic and Cardiology Meeting
- Attended Epic Team meetings Weds, and Thurs;
- Completed the “Building Blocks interface build for all of the Surescript interfaces;
- Struggled with Epic and worked through the Epic Print Services issues and all known problems for the Outgoing Documentation Interface. Now sending documents to Meditech;
- Reviewed the Quest Interfaces with client. Unable to build until Quest is signed.
- Waiting for any contract signing and go-ahead on Incoming & Outgoing Quest Lab Interfaces;
- ProAccess 5.3 PROD interface deployment: worked with Medicity & client on activating PROD interfaces for HIE Pilot, testing & validation of data in PROD environment, additional planning of data for Pilot.
- CERT Testing & Issue Resolution: assisted Medicity in researching testing issues in CERT environment with client application teams, assisted with prioritizing testing & product issues, performed re-testing after CERT deployments to confirm testing & product issues were resolved.
- Documentation: tracking of 5.3 CERT issues/updates/resolutions during testing & retesting on HIE SharePoint for the client and in Rally for Medicity.
- Project Management related reporting and correspondence with Medicity for HIE project. Review with the client and Medicity of project deliverables, updated Pilot scope & timelines, and updated PROD interface deployment timelines.
- Client Code set overview call
- Planning for sending rest of prod messages to cert
- Medicity Issue log management
- Removed ADT errors from queue
- Review UAT communication plan with client.
- Chaired Interface analysis discussion
- Worked on Medicity Cert Deployment bug fix
- Completed sending Prod messages through Client Cert
- Client Nexus Failure review and testing of PA
- Researched all submitted client medicity issues and added to list
Bookmark
Email This
6 Comments
 tiffany jewellery
May 19, 2011 221.138.17.158 Votes: +0 |
concerning the finished necklace. Sew beads onto the 2nd strand, after which drape and pinch another ending of that threaded string toward another http://www.westwoodloja.com/ge...twood.html report abuse
vote down
vote up
|
|
tiffany jewellery
May 19, 2011 221.138.17.158 Votes: +0 |
appropriate after that drape and pinch one ending within of the leftover beading chain strand to some placement concerning the finished necklace. Sew beads onto the 2nd strand, after http://www.westwoodtekoop.com/...twood.html which drape and pinch another ending of that threaded http://www.westwoodtekoop.com/...edels.html report abuse
vote down
vote up
|
|
tiffany jewellery
May 19, 2011 221.138.17.158 Votes: +0 |
appropriate after that enfold the chain near to the midpoint within of the one strand necklace and tuck it in position. take advantage of t http://www.westwoodtekoop.com/...ingen.html he especially ornam report abuse
vote down
vote up
|
 rt
May 27, 2011 209.17.170.64 Votes: +0 |
http://www.findingdream.com/wh...extensions report abuse
vote down
vote up
|
 chic Dresses
May 30, 2011 184.95.43.194 Votes: +0 |
The article is very good, I like it very much. report abuse
vote down
vote up
|
 juicy couture outlet
May 30, 2011 121.205.204.61 Votes: +0 |
Are you still complaining about the out-of-date style and plain-looking color? Don’t worry. http://www.juicycoutures-outlets.com is the God-bestowed angel to fresh your life with fashionable designs and colorful patterns. You can find as many beautiful http://www.juicycoutures-outlets.com as you can imagine. Enjoy yourself but don’t forget the way back home! report abuse
vote down
vote up
|
Write comment
I am very impressed with Orchestrate Healthcare’s professionalism ... industry skills and also with their communication — they are responsive experts.