Hi, Community!

I'm glad to announce UK Technology Summit 2016 started!

#ISCTech2016 tag will help be in touch with all is happening in the Summit.

You are very welcome to discuss the Summit here in comments too!

My organization has been tasked with parsing raw EDI 271 messages into JSON strings in order to feed a downstream application. A few key details about the task:

Hello All,

I'm new and learning about Intersystems products. So I'd like to know what's the difference between Ensemble and HealthShare?

As far as I can see, looks like HealthShare uses Ensemble and could perform everything Ensemble does.

It would be convenient to be able to fetch the whole query result in one operation instead of looping through every row. A fetch_all() method or something similar would provide this functionality I guess. Is there a reason why this is not implemented?

I have a persistent class where I am logging each CCDA I receive. I want to store all of the providers associated to that CCDA (many to one). In a relational database, I would have a child table with a foreign key to the primary table. I'm guessing the equivalent to Cache would be

1. Create a custom class (ProviderList) with the properties I want to store.

2. Add the class as a property of my CCDA persistent class.

Property Providers as Array of ProviderList (SQLProjection = "table/column";

Am I on the right track?

Here you have an easy way to write and execute COS code from your unix scripts. This way one does not need to write routines or even open Studio or Atelier. It can be an option for simple and small actions for instance things like installation tasks or compiling.

See sample bash script (compile.sh) to compile classes:

I need to create a KPI similar to the DeepSee.Model.KPIs.DemoTrendLines kpi in Samples. This kpi supports a scorecard widget with a trend line. It shows patient counts by city with a trend line of the count of patients over a decade. What I want is to show the trend line based on the average allergy score ([Measures].[Avg Test Score]). A pivot table query that shows the data I would want to base the trend line on is:

The values are PIXPDQ, user and admin. What exactly do these mean?

I'm trying to do some correlation and look at the class source but I thought I'd post here too.

InterSystems is pleased to announce that Caché and Ensemble 2015.2.5 are now available as maintenance releases.

At Global Summit back in April, in his keynote speech, John Paladino mentioned that improvements to our documentation search were being made. You might have wondered, since things seemed to go quiet, whether anything was really happening. Well, we had an internal demo of some of the upcoming features recently, and the new capabilities look really cool – searching documentation has been frustrating for InterSystems staff too! So, I thought it might be good to pass on a few details to give a taste of what is coming. Of course, InterSystems will be putting together much better information

How to identify a patient of an encounter?

Doing the following query in Edge we are able to list the records of all patients.

I want select all records of a particular patient.

SELECT top 10 * FROM HS_SDA3_Streamlet.Encounter

We are happy to announce InterSystems Learning at Learning.InterSystems.com, a new and more robust learning platform.

Very new to this side of cache....

So, currently in the habit of keeping all users forever, up to over 5000... ? is what if we decided to start deleting old users who have been gone from the company, how would it affect any account level information? notes, payments etc.... Is there any documentation anywhere that would answer this or describe this process or maybe best practices??

Sorry if this seems stupid but i am working on a proof theory for work.

A few people wrote to me asking about the infrastructure behind the Atelier Server implementation. Its neat and a worthwhile story to share so I am writing it up here as a post on the community. I want to go in to a little detail on why it was needed and then I will outline in detail how we went about implementing this.