#Ensemble

Hello,

In my project, I am calling a store proc on third party database. I am using SQL Gateway and ODBC. Everything is working fine until the store proc changed. In store proc they have changed the return alias name for a column. In Ensemble Snapshot I am not seeing the modified alias name until I restarted the whole Healthshare instance.

Here is my question, is there any other way? We do not want to take the instance down if it happens after we go live.

Thanks

Raghu

Hi,

I'm trying to create an Ensemble workflow with a custom task form that includes a dynaform zen component.
Is it possible to do that? Any sample code?

Thanks for your help

Blaise

Learn how to start troubleshooting productions.

Presenter: Maxim Vershinin
Task: Easily extend your solution’s range of interoperability
Approach: Build Java-only business services and business operations that exploit open-source Java libraries

Problem: The title states the problem Open source java libraries exist for hundreds of protocols and formats. This session explains how you can easily build java only Business Services and Business Operations to that exploit these libraries to extend the range of interoperability.

Content related to this session, including slides, video and additional learning content can be found here.

Presenter: Louise Parberry
Task: Reduce the need for skilled developers to define and normalize data from outside sources
Approach: Use the Ensemble Record Mapper and other tools to automatically define comma-delineated and fixed-width data structures

If you need skilled software developers to define and normalize data coming from business partners or customers, you probably have a backlog of unsatisfied requests. The record mapper and other tools allow analysts to define comma delimited and fixed width data structures without needing a developer and this session explains how this can be incorporated into an application to create an efficient and effective way to clear that backlog.

Content related to this session, including slides, video and additional learning content can be found here.

I am pleased to announce that Caché and Ensemble 2015.2.3 are now available as maintenance releases.
For a complete list of the corrections in 2015.2.3, please review the release notes.

Caché and Ensemble 2015.2.3 are available now for the same platforms as 2015.2.2

The complete set of supported platforms, including specific point releases and/or patches, is detailed in the Supported Platforms document.

Hi -

I was looking at the “Purge Data Management” page, and one of the “Record Types” is the “I/O Log” which sometimes doesn’t clear when you purge all of the message.

But I’m not sure what it’s actually reporting as “I/O Log” messages (and I can’t find anyplace to view what is being considered I/O Logged Messages - so I can understand what’s happening)

Can anyone shed some light on these messages?

Whichever way you want to look at it, their numbers are impressive... growing revenue year-on-year of 69% is amazing... and now they are opening DCs in Canada and India...

http://cloud-computing-today.com/2016/01/29/1074342/

--

Do you use any public cloud? Any private one?

Have you ever needed to find a record for a particular person in your inbound data stream?

Searching messages will enable you to find messages using an array of search capabilities.

When you create an Ensemble production your namespace acquires a new class definition. For example here is what the class that defines the Demo.Loan.BankUSProduction production in the ENSDEMO namespace looks like when opened in Studio:

We are beginning a project to switch over to a differnt EMR for our inpatient system, and we are wondering if others out here have worked on a similar project and how did you handle your Ensemble environment?

Currently, we use one namespace for all of our HL7 interfaces. Has anyone used a separate namespace for a project to keep the build separate until go-live? What were the pros/cons for you using a different namespace? Or did you use one and what issues did you have because of it?

If you've got more than one developer on a project, do you each work in your own namespace? Or do you all use a common namespace?

Through my work at George James Software I have encountered many different Caché and Ensemble development setups. At risk of over-generalizing, the older and more established users of InterSystems technologies seem more likely to have all their developers working in a common namespace, whereas the newer 'converts' tend to favour giving each developer their own namespace.

What is the recommended approach to handle the following scenario: Large number of HL7 messages are serviced via Ensemble. Those messages are then transformed and routed to an Operation which calls a web service which does a number of different activities. If will do address normalization, location geo coding, MPI lookup and resolution, and insert into a SQL Server database to stage for an analytics product. Unfortunately all of this work takes time and the first thing that happens in the web service is a lock taken out on the Patien in SQL Server.

I'm working on a proposal for a deployment tool development project and I was wondering if anyone had any experience with such a thing.

We use Healthshare and implementations for new clients are tedius and lengthy. Lots of ensemble service, registry value, lookup tables, namespaces and other things have to be created and configured.

I would like to create a Zen or CSP page based deployment tool that can do all this with a few parameters and some custom code.