Hello. New to the forum and was hoping I could get some expert help here. I have one data set that is using CHD Logic to combine Procedure and Diagnosis codes to define Sensitive data and flag the record for additional protected filtering. The files coming in define what is flagged and the Clinical Info Rule and Clinical Info Type are tied to the flag in the file which identifies it as a additional protected record.

0 1
0 384

The class %Compiler.UDL.TextServices arrived in 2015.1, bringing us methods for exporting a class in UDL format (i.e. looking just like we're used to seeing it in Studio), and importing a UDL format definition back into a namespace. Some source control tools including our Deltanji are now able to use UDL format, resulting in diffs that are easier to understand.

1 1
0 306

Hello everebody,

I'm begenning with intersystems, and i woul like to customize the screen patient Search psorposed by HealthShare,

i have to change the form and delete some fields....

the name of the standard page is 57772/csp/healthshare/hsaccess/HS.UI.PatientSearch.cls

if someone can help me that's greet

0 1
0 400
Article
· Apr 24, 2017 1m read
Diagnosing the cause of <PROTECT> errors

If your application is raising <PROTECT> errors and you're finding it hard to work out why, here's a way to get additional information.

First, if auditing is not already enabled, turn it on:

Then use "Configure System Events" (highlighted above) and locate the event named %System/%Security/Protect. In the screenshot below I used the Filter field to do this (type "protect" - highlighted below - and press TAB):

4 1
0 2.3K

I have a HL7 schema listed within Healthshare that is marked as 'Standard' however this doesn't appear to not a standard schema and more of a custom one created (there are very specific Z segments within it) that has somehow been marked as a standard. Is there a way to change it from a Standard to Custom? I realise that this cannot be completed within Healthshare but is there a way to change this within Studio?

Thanks

0 1
0 292

We have a program set up in the HealthShare Facility Registry. And we have some patients enrolled into this program. In the HealthShare Registry management, we set up following consent policy for this facility (we call it program), Default Block Except: Block data except for the groups specified below, unless overridden by patient. There is no program in the Selected Programs so the consent should be applied to everybody.

0 1
0 614
Article
· Feb 14, 2017 1m read
Portal tip: The inconspicuous Menu button

Amongst the large fonts and chunky icons of Portal's pages, the Menu button in the top left corner is easily overlooked:

When clicked, it often produces the following menu:

When I remember it's there, I find the "View Console Log" option particularly handy.

I wrote "often" above because I've also noticed that the Menu contents change when I'm on a page within the Ensemble section of Portal:

4 1
0 520

Hi,

I have Healthshare/Ensemble version 2015.2.1.

I created Business Operation in my ENSDEMO namespace that will connect to an external REST endpoint to send data to this external REST Service.

I also created an http service in Home>Healthshare>Service Registry, under the Service Type: http. I entered the REST endpoint Name, Host, SSL Configuration, and URL.

0 1
0 622

Hello,

I am interested in working with a third-party API in my instance of the Community Portal. I was curious as to how you all work with third-party apis. Do you typically connect directly from within a ZEN Mojo Page or do you route the request through an operation in the management portal? Are there any sort of best practices I should be aware of?

Thanks,

Bob

0 1
0 300

I needed to pass through a file with Ensemble but the operation wasn't writing some filenames as given because the EnsLib.File.PassthroughOperation 'sanitizes' filenames removing characters that are not valid on some operating
systems;
09000655_AEDC_C3344059_A&#47;E_Martin Browne_09000655_201706221018.pdf
09000655_AEDC_C3344059_A#47E_Martin_Browne_09000655_201706221018.pdf

1 0
0 1K

Hi, Community!

A sophisticated alerting solution lets you solve problems quickly and proactively. So, check the new video:

Proactive Alerting: Advanced Approaches for Alerting Solutions

https://www.youtube.com/embed/IeALdbVn0uI
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

2 0
0 334

InterSystems is pleased to announce the availability of the following maintenance releases:

  • Caché and Ensemble 2016.2.2
  • HealthShare Health Connect v15.021 on two core technology releases, 2016.2.2 and 2017.1.0

Caché and Ensemble 2016.2.2 are available on the same platforms as 2016.2.1

1 0
0 532

HealthShare HealthConnect and Information Exchange version 15.03 support import transformations from C-CDA 2.1 to SDA. You can find these transforms in your installation's csp/xslt/SDA3 directory. For general information about import transforms, see "CDA Documents and XSL Transforms in HealthShare" in Overview of Health Connect.

Among the enhancements to import functionality added in connection with C-CDA 2.1 support is the ability to preprocess your C-CDA input files prior to the transformation done for import.

2 0
0 1.1K