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.
i develop my LogUser Method on my rest API , the scenario is as follow :
when user enter his login & password , i check first in my table if he exists (this stape is done), now i want know how generate acces token from authorization server , i've as idea to call the "%OAuth2.Server.Generate" which is implemented on the configuration party (we find the correspondint attached screenshot ), but i don't know if i'm sure , we find here the developped method:
I've written several custom classes to add additional search capabilities to the user / clinician search defined in HS.UI.Registry.User.Find. I've tested it out, and it looks and works how I'd like it to, but I've run into a snag when trying to implement it.
The documentation for registering custom user interface pages shows a table of about 50 configuration registry keys for UI pages, but it only lists:
I'm trying to connect to one of our Ensemble servers Cache database from a C#-windows form . I'm running the client from my local computer with OS win7. Using .NET FW ver 4.5.2 in the client.
ODBC local setup using "InterSystems ODBC35"
In this ODBC konfigurationview i can put my userID and password and try a testconnect (or ping). And that run successful.
However, we don't want to leave credentials in the ODBC-configuration it self (open up for anybody to use the source) but instead send it from the klients.
I'm VERY novice on all things "OpenAM", and beyond knowing that Caché supports working with OpenAM, I have nothing else to go on.
The documentation doesn't seem to be very deep on the nature of how this works beyond a single paragraph saying it's supported for Single Sign On (SSO).
I'm looking for guidance on how best to normalize Height and Weight values to standard units. For example, to accept height as Feet/Inches, Inches, and Centimeters from various sources, but always display Feet/Inches in Clinical Viewer, etc.
If anyone has done this before, please share details of how it was implemented. Things I'd be specifically interested in:
Let's consider you would like to efficiently store your historical data in a similar structure than the one used for your current data, but without sharing the same physical storage (ie : not in the same global). What is the most efficient way to do it ?
If one of your packages on OEX receives a review you get notified by OEX only own YOUR package. The rating reflects the experience of the reviewer with the status found at the time of review. It is kind of a snapshot and might have changed meanwhile. New with this edition: Reviews by other members of the community are marked by * in the last column.
https://www.youtube.com/embed/E9jBHljk9To [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]
Suppose you want to create your ObjectScript library to be distributed via ObjectScript Package Manager. And there is an obvious question: what is the naming convention on the packages and class names?
This post is a introduction of my openexchange iris-python-apps application. Build by using Embedded Python and Python Flask Web Framework. Application also demonstrates some of the Python functionalities like Data Science, Data Plotting, Data Visualization and QR Code generation.
Features
Responsive bootstrap IRIS Dashboard
View dashboard details along with interoperability events log and messages.
If one of your packages on OEX receives a review you get notified by OEX only on YOUR package. It reflects my experience with the status I found at the time of my review. It is kind of a snapshot and might have changed meanwhile.
This post provides guidelines for configuration, system sizing and capacity planning when deploying Caché 2015 and later on a VMware ESXi 5.5 and later environment.
Hello everyone.
I present this project to the contest. The export module is essential in many of my projects and is often used in all my product servers.
Hi Community, we continue to gather feedback about Data Loading & Packaging. In particular, we're interested in hearing your impressions on some of the new capabilities added with InterSystems IRIS 2021.2 We'll be using this feedback to improve InterSystems IRIS, so please feel free to share any details and feedback:
Note: this is the same survey we already published during the contest, on Global Masters and Discord. If you already participated, you don't have to do it again. Thank you for the feedback!