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:
I'm stuck on how to show the top 15 payers and then also show the percentage of the total amount paid for each one. The total amount is what was paid by all the payers not just the top 15.
With a routine like this one, you can quickly calculate how many lines of code you are working with. And it is not only for routines, it works for classes because remember that classes generate routines !
I have a list of about 100 MPI IDs that I would like to run a report on. I want to list times that any data for these patients were accessed. Currently in "Managed Reports" we have a "Disclosure Report" which I think was a custom development effort, but it is per-patient.
I have a SQL query for the ATNA log but I'm not confident in its accuracy, so I thought I'd reach out and see how other Information Exchange's might get this data.
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
Beginner’s guide to RESTful Application Program Interface (API) design and documentation. Through the example you will learn some common pattern for RESTful API.
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.
The goal of this writing was to illustrate how to restore backup before the patch would be applied. The alert notes that:
The risk can be avoided by applying journals from the beginning of the journal file that was switched to at the start of the backup, rather than accepting the default of starting from the journal marker position.
Having non-patched Caché 2015.1.4, I ran sample database backup and restore just to get where I should answer "No". Collecting journal info from the backup log:
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.
Is this available anywhere (for Health Connect)? I've found a few presentations but they are aimed at entry level.
We're looking at supporting more and more FHIR, REST plus OAuth interfaces in future. I've built some of this into older versions of HealthShare and Ensemble but it's desirable to move to supported versions.
We would be using Healthshare as a facade to other systems.
As some customers recently received new license keys, I received some questions why their new license does not seem to work, other than the expiration date being reached. So far I was able to solve all of them with this short list of things to look at.
Do you find yourself commonly adding code actions to your data transformations? If so, what do these contain? Is there a reason you choose to add a code action over creating a custom function that you can call?
InterSystems has corrected a defect that may result in missing updates when utilizing Caché online backup.
This defect is present in all Caché and Ensemble versions 2015.1.x, 2015.2.x and 2016.1.x, and all HealthShare distributions based on those versions. It affects all platforms and operating systems except backups of OpenVMS cluster databases.
We are interfacing through Ensemble with an application that does not like diacritic signs in text. I have been searching for a way to strip these signs from the HL7 messages that get send to that application. The problem in short is we have an incoming HL7 message with e.g. é (or ë, á etc), this goes into Ensemble. In the outgoing message the é should be replaced with an e.
This text is a continuation of my article where I explained the structure a Caché database. In this article, I described the types of blocks, connections between them and their relation to globals. The article was purely theoretical. I made a project that helps visualize the block tree - and this article will explain how it works in great detail.
By update
