Ensemble

Syndicate content 72 

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.

0   0 1
0

comments

112

views

0

rating

Presenter: Mark Massias
Task: Present complete, contextualized information to the people who must act as part of a (mostly) automated business process
Approach: Give examples of using InterSystems’ workflow engine.
 

More and more business processes are automated, but sometimes a person needs to make a decision. In some cases policies require an individual to approve an expenditure, or when loading data a person needs to sort out exceptions where the data in not clear. This session explains how to include people in business processes in a way that presents the user with a complete context for the decision they have to make.

Problem: Using human workflow to fix business process problems.

 

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

0   0 2
0

comments

140

views

0

rating

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.

+ 2   0 1
0

comments

371

views

+ 2

rating

This will be a stretch to be useful, but it was sorta fun.  If you just so happen to have a use case to make your HealthShare productions talk to a Slack channel, this is the Business Operation for you.

In Slack, it is a dead simple process to enable an incoming web hook:

  • Name It
  • Give it an Icon or Emoji
  • Declare a Channel to Interact With

One you supplies those, it spits out a URL that you can go to town posting to your channel using that endpoint.

Last comment 1 April 2016
+ 8   0 6
405

views

+ 8

rating

I am pleased to announce the field test of Caché and Ensemble 2016.2 -  an exciting new release with improvements on many different fronts.

The entire product team at InterSystems looks forward to your participation in the field test and feedback over the coming months.

Some of the more profound changes in 2016.2 include:

Last comment 29 March 2016
+ 6   0 8
838

views

+ 6

rating

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?

Last answer 29 March 2016
0   0 1
0

comments

172

views

0

rating

I am happy to announce the immediate availability of  Caché and Ensemble 2016.1.

The highlights of 2016.1 are

  • Significant improvements in JSON support
  • Continued advances in SQL performance
  • Database scalability improvements
  • New REST services for DeepSee

These and other new features are summarized in this video introduction to 2016.1

For complete technical details of what’s changed in 2016.1, review the Caché release notes and the Ensemble release notes.  

Last comment 18 March 2016
+ 7   0 1
749

views

+ 7

rating

We have to route messages in a Process Class by their source (using either the SourceConfigName from the Message Header or the Source in the Message Body.  

The inputs are standard HL7 messages from different Services but need to be routed on to different Processes depending on where they come from (not my design & I can't change it now) does any one have any suggestions how I could do this?

Thanks

Last comment 15 March 2016
0   0 2
0

answers

320

views

0

rating

Has anybody managed to get Enterprise Monitor to work to monitor multiple namespaces on manay instances?

I am hitting an issue trying to get a local instance namespace working.

I have this error for my first local namespace sytem configured.

"Ensemble encountered an error while loading this page"

Last comment 11 March 2016
0   0 3
0

answers

150

views

0

rating

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?

Last comment 8 March 2016
0   0 3
0

answers

227

views

0

rating

When my COS code is executing in a Caché process it might want to interact with the host operating system. For the purpose of this post I'm focusing on a Windows host, but much of it applies to other host OS platforms as well.

A common example of host OS interaction is when my process wants to read from or write to a file. What credentials will apply when Windows is checking whether or not to allow me access to the file?

To answer that we need to consider another question. How did our process start?

Last comment 8 March 2016
+ 3   0 6
501

views

+ 3

rating

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.

Last comment 7 March 2016
+ 2   0 7
0

answers

551

views

+ 2

rating

We have a situation where we want to detect and ignore documents/records at the earliest possible point based on certain criteria.  We have an existing "CDA Preprocessor" in the workflow which is an XSL transform.  This is what our contractors are planning to utilize to "filter" these documents.  This doesn't really make sense to me.  I see XSLT as a way to manipulate the contents of a document and filter certain peices of data.  In my brain, I would use an Ensemble business rule to detect the criteria and route the document as necessary.

Last comment 4 March 2016
+ 1   0 4
0

answers

212

views

+ 1

rating

The cdirectmgr utility will no longer be included with product distributions beginning with the Caché 2016.2 release . This was an older VB application (predating the Caché cube) which allowed users to define server connections for Visual M/Caché Direct applications. As VB 6 is no longer supported by Microsoft, we will no longer ship this component. The same functionality is already available from the cube utility.

It is also posted in Compatibility blog.

Last comment 4 March 2016
0   0 3
160

views

0

rating

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.

Last comment 4 March 2016
+ 1   0 5
0

answers

405

views

+ 1

rating

Zen Reports has offered multiple choices for direct printing including use of Adobe Reader or Foxit reader. Recent changes in Windows 10 and in the readers themselves have made it no longer possible to invoke these readers from background processes in Windows 10 and all future versions. Because of this Zen Reports will no longer support printing with these tools on Windows 10.

Windows 10 support was added for 2015.1 and 2015.2.  On Windows 10, the only option for direct printing with Zen Reports will be Qoppa JPDFPrint.

Last comment 3 March 2016
0   0 2
162

views

0

rating

I have been meaning to make a post about this topic for a few weeks and the other day an issue came in through the WRC about it so it seems this is a conversation we should be having. I want to begin by taking a few moments to explain "Why Atelier" then we can talk about what this means in the general sense for Studio and Atelier and Caché developers. We have wrestled with what to do with Studio for years. When I moved to Product Management in 2008 this was already a "thing". At the time we could not reach a consensus. Some felt Studio was fine as is.

Last comment 3 March 2016
+ 8   0 6
2940

views

+ 8

rating

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.

Last comment 1 March 2016
+ 1   0 5
0

answers

628

views

+ 1

rating

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

Caché and Ensemble 2015.1.4 are available today for the same platforms as 2015.1.3.
The complete set of supported platforms, including specific point releases and/or patches, is detailed in the Supported Platforms document.

+ 1   0 1
0

comments

86

views

+ 1

rating

Hi all,

I was wondering, what is your favourite public cloud provider?

What is your level of engagement with the cloud provider? Are you testing their infrastructure? In which case I'd expect you being progressing a parallel test with at least a second provider ;-) Or, are you already running a production environment?

--

 

OK, so, let me be the first one to share my experience with one specific cloud provider.

Last comment 26 February 2016
+ 2   0 5
0

answers

282

views

+ 2

rating

Hi,

We do have a production including a SOAP.OutboundAdapter that make a request to a .NET WCF Service. The response from that service vary in size. When it come to large one, we talk about maybe 8000 records (with 6-8 attributes per record) in xml, the adapter always give a timout. Even if we put a high number of seconds or set -1. After 1 1/2h still nothing get back. It's just standing there and waiting for ever.

Last comment 12 February 2016
0   0 3
0

answers

255

views

0

rating

I'm writing some custom functions for use in a routing rule.  I have a few that are working, but right now I'm trying to use one that has no parameters.  Typically this would be a sub instead of a function, but I'm not familiar enough with Cache to know what I need to do here. 

Here is the code:

Last comment 11 February 2016
0   0 4
0

answers

230

views

0

rating