In today's data landscape, businesses encounter a number of different challenges. One of them is to do analytics on top of unified and harmonized data layer available to all the consumers. A layer that can deliver the same answers to the same questions irrelative to the dialect or tool being used.

Executive Overview

In most organizations, events drive action. In financial services, for example, a stock dipping below a threshold price may trigger a sell order. In manufacturing, production may start when an order is received. In healthcare, an unusual increase in the number of patients registering in an emergency room could signal the start of a disease outbreak, calling for action on the part of medical staff and public health officials.

Mixing Object syntax with SQL is one of the nice features in Object Script. But in one case, it gave strange results, so I decided to isolate the case and describe it here.

Let's say you need to write a classmethod that updates a single property on disk. Usually, i would write that using SQL like this :

Presenter: Andreas Dieckow
Task: Securely store sensitive information
Approach: Give examples of data-at-rest encryption and data element encryption

Description: In this session, InterSystems will showcase how to use API calls to programmatically do everything using your own scripts. This approach is highly effective if you have recipe based settings and configurations that you would like to roll out in a controlled and fast fashion.

Problem: Implement Security relevant information correctly and how. Examples are Credit Card information, Sensitive information (e.g. SSN, Classified Information)

Solution: Data-at-rest encryption and data element encryption

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

NewBie's Corner Session 15 Executing Routines and Labels

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

Routines and Labels

Routines are computer programs with a number of executable code lines.

Labels (also called tags) are points in a routine that can be called (executed). They subdivide routines into manageable modules (or subroutines).

Routines, Subroutines/Modules and Functions

When analyzing data, there is often a need to look at specific indicators more thoroughly and to highlight sections of information of particular interest to a user.

For instance, examining the data dynamics for specific regions or dates can help us uncover some hidden trends and patterns that will allow us to make an informed decision about our project in the future.

Background

Most websites have a "Fav.ico" file that sets what the icon is for the webpage. Most users have multiple environments, Dev/Test/Live. Often it can be difficult at a glance to see which environment you are in at a time. Wouldn't it be nice to visually see what version you are in? In this example all the instances are called the same and are named "ENSEMBLE". Note that this is certainly IRIS FOR HEALTH as is used on 2022.1

The default Icon is IR

The guide “Extending Languages with %ZLANG Routines”
Tells you all details you need to know to extend your programming language.
EXCEPT: How to do it in a clean way.

This example of a %ZLANGC00.mac may show a possible approach
to get an easy to overview and to manage setup.
With less than 50 lines of code you might not be affected.
But if your Studio shows close to 1000 rows or more you may get in troubles.

FYI, on the Field Test page, the links highlighted below are currently broken:

UPDATE: this is now working again.

IRIS Megazord

In the first article about IRIS Megazord, Henrique explains what drove us to create such an application. It basic is a composition of these previous project which we did:

InterSystems IRIS offers various ways how to profile your code, in most cases it produces enough information to find the places where the most time is spent or where the most global sets. But sometimes it's difficult to understand the execution flow and how it ended at that point.

To solve this, I've decided to implement a way to build a report in a way, so, it's possible to dive by stack down

Introduction - Analyzing Textual Big Data

Big Data for Enriching Analytical Capabilities - Big data is revolutionizing the world of business intelligence and analytics. Gartner predicts that big data will drive $232 billion in spending through 2016, Wikibon claims that by 2017 big data revenue will have grown to $47.8 billion, and McKinsey Global Institute indicates that big data has the potential to increase the value of the US health care industry by $300 billion and to increase the industry value of Europe's public sector administration by Ä250 billion.

In this article, we will analyze the intricacies of setting up tables and graphs to improve the readability of data.

Logi offers a rich set of data visualization tools. You can find anything from a wide variety of chart templates to custom CSS styles. Understanding the assortment of settings and options can be quite difficult. First, we will create a chart and a table with default settings, and give them a presentable look using InterSystems Reports (powered by Logi Report).

Methods written in ObjectScript can use pass-by-reference arguments to return information to the caller. Python doesn’t support pass-by-reference arguments, so Embedded Python in IRIS doesn’t support them either. That's it, that's the end of the post, hope you liked it. 😉 But wait, what about the Classic Rock & Roll?