Difference Between Macro and routine?

what are the difference between Deepsee and Ensemble , and how to access the ensemple .Please Tell me

Can anyone explain me how to create a dynamic session in CSP?

I am learning cache in beginning level . But confused .Give an idea for how to i learn cache easily and improve programming level

I'm running into difficulty calling a javascript method from a Zenmethod. I pass in a parameter, but in the javascript method the parameter is undefined. Here is the code:

...

NewBie's Corner Session 16 Introduction to New Concepts

Welcome to NewBie's Corner, a weekly or biweekly post covering basic Caché Material.

A number of new concepts are introduced in this session that will be developed more fully in subsequent sessions. It is necessary to at least introduce these concepts here because they are all interrelated.

Older style of MUMPS Programming

Creating and working with the new SDA extensions for storage of custom data elements

In HSCore 15.01, there is a new way to store custom data elements. HealthShare now had the ability to use custom extensions on many SDA elements.

This article will:

1. Show how to set up your system to use SDA extensions
2. Create a new SDA extension property
3. Use the new SDA extension property in HL7 transactions
4. Interact with the new data
5. Show new SDA extension used in a customization of Patient Summary Report

Are Excercise parts avilable in documentation of InterSystems cache . Please Give the link. Thank you

I have the following Ensemble request:

Class MyApp.MyRequest Extends (%Persistent, Ens.Request)
{
Property idToTokenArray As %ArrayOfDataTypes;
}

On SMP Testing service page it looks like this:

But my attempts to set idToTokenArray have not yielded any positive results so far. How do I need to fill it?

Hi,

I create a cache class program. Its compile it. But how to run it?

Please send one sample program with output

This is the fourth article in a series on iKnow demo applications, showcasing how the concepts and context provided through iKnow's unique bottom-up approach can be used to implement relevant use cases and help users be more productive in their daily tasks. Previous articles discussed the Knowledge Portal, the Set Analysis Demo and the Dictionary Builder Demo, each of which gradually implemented slightly more advanced interactions with what iKnow gleans from unstructured data.

This week, we'll look into one more demo application, the Rules Builder Demo, in which we'll build on previous work but again climb a step on the level ladder, implementing a more high-level use case than in the previous ones. The idea came from an opportunity where we were asked to help the customer in the finance sector make sense of vast volumes of contract data. They wanted to semi-automate the extraction of logical rules from that text (in fluent legalese!), so they could be fed into other systems. While this was an exciting use case to work on (and more on it in this GS2016 presentation), we've also used it in other cases, for example to extract mentions of ejection fraction from Electronic Health Records.

NewBie's Corner Index - Links to connect to all NewBie posts.

NewBie's Corner Session 1 Installing Caché

Date range queries going too slow for you? SQL Performance got you down? I have ANOTHER weird trick that SQL Developers don't want you to know!*

This is the third article in a series on iKnow demo applications, showcasing how the concepts and context provided through iKnow's unique bottom-up approach can be used to implement relevant use cases and help users be more productive in their daily tasks. Previous articles discussed the Knowledge Portal, a straightforward tool to browse iKnow indexing results, and the Set Analysis Demo, in which you can use the output of iKnow indexing to organize your texts according to their content, such as in patient cohort selection.

This week, we'll look into another demo application, the Dictionary Builder demo, in which we'll marry iKnow's bottom-up insights with top-down expertise, organizing our domain knowledge into dictionaries that are composed of the actual terms used in the data itself. Sticking to a top-down approach only, you'd risk missing out on some terminology used in the field that a domain expert sitting in his office wouldn't be aware of.