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:
EHR (Electronic Health Record) systems are modeled in a proprietary format/structure and are not based on market models such as FHIR or HL7. Some of these systems can interoperate data in a proprietary format for FHIR and other market models, but others can not. InterSystems has two platforms that can interoperate proprietary formats for market ones: InterSystems HealthShare Connect and InterSystems IRIS for Health.
Poor glycemic control is associated with a greater risk of miscarriage, NICU admission, operative delivery, and shorter gestational periods. Especially at risk are those with preexisting diabetes, who would benefit from maintaining near-normal glycemia before conception.
There is not just one class in this package: rcc.gstream.cls but also rcc.gstreamT.cls
While rcc.gstream works with direct access to the stream globals, the *T version uses a Process Private Global (PPG) as Temporary storage. using SELECT * FROM RCC.gstreamT WHERE RCC.useT('^jpgS')=1 and similar.
Comprehensive patient view, communication and data sharing, and population health management are key components
Federal agencies have been incenting healthcare providers to leverage their electronic health records (EHRs) to get patients involved in the management of their care. Most organizations, however, haven’t moved beyond patient engagement as an item to be checked off in order to receive meaningful use incentive funding.
A business case for the transition from eGate to InterSystems EnsembleÆ From interface engine to integration platform Healthcare IT is evolving so rapidly that the term "HL7 interface engine" may soon become extinct. Forces driving this evolution include:
Customers who switch to Caché from relational databases report that their average performance is up to 20 time faster, running on the same hardware, with no changes to the application. What is it about Caché that lets applications run so fast?
I am pleased to announce the next 2016.2 field test kit, 2016.2.0.605.0.
There are about a hundred changes from the previous field test kit, including the following fixes to problems found by those using the kits in the field:
Presenter: Kyle Baxter Task: Upgrade to a new version of Caché without concerns about slowing existing SQL queries Approach: Use the new Frozen Plans feature in Caché
Content related to this session, including slides, video and additional learning content can be found here.
Presenters: Pete Greskoff, Sebastian Musielak Task: Ensure high availability of your HealthShare deployments Approach: Discuss high-availability options and focus on HealthShare’s new support for database mirroring
With the new release of HealthShare, Mirroring is now support for high availability. This session will describe high availability options and focus on mirroring your HealthShare deployments.
Content related to this session, including slides, video and additional learning content can be found here.
Presenter: André Cerri Task: Use third-party visualization tools to present your DeepSee data Approach: Use DeepSee REST services to access DeepSee data from third-party tools
Come see examples of how you can use popular 3rd party data visualization tools to access your DeepSee data.
Content related to this session, including slides, video and additional learning content can be found here.
NewBie's Corner Session 2 Variables Set and Write commands
Welcome to NewBie's Corner, a weekly or biweekly post covering basic Caché Material.
Session 2 – Click on the Caché Cube in your system tray and select Terminal to try out the commands.
Variables
Like other computer programming languages, Caché uses Variables and the values they represent to control programming. Variables are elements that represent data values. Manipulating and interrogating variables is at the root of programming.
In a conference call earlier this week, a customer described how they built an iKnow domain with clinical notes and now wanted to filter the contents of that domain based on the patient's diagnosis codes.
Configuring an Ensemble production can be a challenging task involving a thorough understanding of the system and production functionality and a detailed understanding towards each configuration item. After successfully configured an Ensemble production, you might need to set up an identical production on the mirror environment, or deploy the production on a development system to a live system, or send a copy for diagnostic/debug purposes. Other times you might have spent some time designing a BPL/DTL and some other productions can use the same logic.
Today I helped someone solve a mystery. He had been trying to use the -U namespace argument of a csession command to specify the namespace in which to run a particular routine, and was puzzled when the routine could not be found.
We just faced an issue of the Atelier main menubar being disabled (greyed out) after upgrading the macOS development machine to High Sierra. I would like to share my findings about the issue and how to fix it.
The following post is a guide to implement a basic architecture for DeepSee. This implementation includes a database for the DeepSee cache and a database for the DeepSee implementation and settings.
How Tax Service, OpenStreetMap, and InterSystems IRIS could help developers get clean addresses
Pieter Brueghel the Younger, Paying the Tax (The Tax Collector), 1640
In my previous article, we just skimmed the surface of objects. Let's continue our reconnaissance. Today's topic is a tough one. It's not quite BIG DATA, but it's still the data not easy to work with: we're talking about fairly large amounts of data. It won't all fit into RAM at once, and some of it won't even fit on the drive (not due to lack of space, but because there's a lot of junk). The name of our subject is FIAS DB: the Federal Information Address System database - the databases of addresses in Russia. The archive is 5.5 GB. And it's a compressed XML file. After extraction, it will be a full 53 GB (set aside 110 GB for extraction). And when you start to parse and convert it, that 110 GB won't be enough. There won't be enough RAM either.
When you prepare your modules for ZPM (InterSystems Package Manager) it expects the certain directory structure for ObjectScript source files.
ObjectScript in your source folder need to be stored by types in the following subfolders. E.g. if you have the source folder named as /src the structure should be as follows:
In the previous part of this series, we saw how to include data in a portlet from within DeepSee. This used the built in data controller. In this part, we are going to be pulling in data from outside of DeepSee. This will include both information from within InterSystems IRIS and from the OS.
Why use this?
This is useful if you would like to create a dashboard that only contains information about your system. It is also useful if you want to display data about your system along side data that you have stored in DeepSee.