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?

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?

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.

Hello,

This package may be of interest...

Link: https://github.com/litesolutions/cachedb-import

I have programmed this over a hunch, in order to facilitate the retrieval of source code from a Caché installation. It makes use of the Java API provided by Caché.

Right now, I use it as a means to salvage sources in order to analyze them using the SonarQube plugin I develop for my employer. Unfortunately this plugin is not open source.

I am calling for help here, on two fronts:

RESTful API Call From Cache to Particle.io Electron

Tom Fitzgibbon | Multidata | 212-967-6700 x537 | tom@mul.com

Summary: Simple Blink Tutorial for Particle.io Electron Device from Cache

Electron device is a tiny ARM processor ($40-$60) that connects to Particle’s world wide leased 2G/3G network (about $3/mo) and runs off an included LiPo battery. Using Cache’s %Net.HttpRequest you can send/receive data, control hardware and read sensors.

Step by Step (about 1 hour)

1) Get the Electron from store.particle.io.

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.

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.

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.

Hello! 

I'm trying to use iKnow but I get the following error "No iKnow-enabled namespaces found" in the Management Portal.

It was working on the 2015.2.2 version but now on 2016.2.0 it doesn't. I very new to Caché and iKnow so it's probably a simple problem. 

I was able to create a iKnow domain using the terminal and I can view it in the learning portal (http://localhost:57772/csp/sys/exp/_iKnow.UI.IndexingResults.zen).

So another topic that has been of interest to a number of people since the beta was put up last week is in regard to Studio Hooks and Atelier. This requires a bit of background and then some discussion of how the architecture of Atelier necessitates some changes and then what our current thinking on the subject is.

Hello! 

I'm trying to make a simple hello world program for iKnow but the documentation only shows examples using the scripting language or XML XData. 

The domain is already created and configured, what I hope for is to be able to work with the data in some high-level language. 

Is it possible to do something like this:

int domainId = 1;
IKnow iknow = new IKnow( domainId );
List concepts = iknow.getTopConcepts();

Any feedback will be greatly appreciated!

Attached is an example of a web service client that can be used to do a lookup against the CMS NPPES database to validate and retrieve information about a given National Provider Identification (NPI).

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.

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.