Update - current version does support the following https://docs.intersystems.com/hs20252/csp/docbook/Doc.View.cls?KEY=HSAPI_access_launch_viewer
Supported since at least 2024.2 but possibly earlier - search your documentation for "GetViewerURL" to be sure.
Hello Igor, you may need to add the following to the custom CSS file:
a {
pointer-events: auto;
}If you don't have one already, you may need to create it by copying:
<install_dir>/csp/healthshare/<viewer_namespace>/web/custom/HS/scripts/v2-template.css to
<install_dir>/csp/healthshare/<viewer_namespace>/web/custom/<SiteName>/scripts/system.css
I don't think this syntax works. I think the exclusion is for matching against wild cards, for example if you wanted to export all the globals called some*.gbl but exclude one or more of them. I don't think it deals with subscripts.
You may need to merge your global into a temporary global, kill the subnodes you want to exclude, export, and then merge the temporary global back to restore them. (or something similar)
I understand that this is probably not an option if the data is huge. Maybe InterSystems support (WRC) can help.
Hello Edward -
If you're referring to the Patient Summary reports, then access to that is controlled by the %Admin_Manage resource. You can edit existing roles or create new roles with access to that resource as you like.
If this isn't what you're asking, please elaborate. Thanks
-Bill S.
HealthShare development
Anna - yes, when you build your array of items to export, you can include expressions like:
set items("myGlobal(""x"").GBL") = ""
set status = $system.OBJ.Export(.items, myFile, myOptions)... and this will export ^myGlobal("x").
Clinical Viewer will support Single Sign On in the 2021.2 release.
One quibble: if the user creates the new class as User.Foo, as in your example, it will be situated in the VIEWERLIB database according to our standard namespace package mappings.
I think we don't want custom code to live there; rather, it should live in HSCUSTOM. By default, we have a mapping to HSCUSTOM for the package HS.Local ... should the new class be located in this package instead?
Hi Paul,
I'm a developer on the Clinical Visualizations team within the HealthShare development organization. This is the team that manages the Clinical Viewer.
Unfortunately at this time you can't link directly to a patient's chart. The Clinical Viewer works with the Access Gateway, and patient's data is not even present in the Access Gateway until the Access Gateway communicates with the Registry and the Edge Gateways to collect, deduplicate and organize the patient record. It then lives only transiently in memory in the Access Gateway while the Clinical Viewer displays it. When running the CV as usual, this all happens when you do a patient search and click on a patient in the result list: the Access Gateway requests, receives and stages the data before redirecting you to the actual viewer UI. The patient record isn't just sitting around available to the CV in advance.
Hypothetically we could create an API you could call, providing an MPIID or some other identifier, which would do the data management and then send you (or redirect you to) the appropriate viewer URL, but no such feature is currently available nor will it be in HealthShare 2019.1 (which we expect to release in the next few weeks). It would also raise questions about authentication if the user is not currently logged in to the Clinical Viewer app with a current web session.
We don't yet have a federation-wide universal authorization scheme in place, so any new incoming connection to the Clinical Viewer needs to log in. Otherwise, we would not be able to apply consent filtering and this would constitute a serious risk to patient data privacy and consent rules.
We are hoping to have more flexibility in this area available in future versions but for now it is not supported. If you think that this would be especially useful to one of our (actual or potential) customers, let us know. Feel free to email me at the address below.
-Bill Sherman
+1 (617) 577- 3641
HealthShare Development
InterSystems
Cambridge, MA, USA
Yes, it does work that way. If Cat is a subclass of Mammal, and Mammal is a subclass of Animal, then ##class(Cat).%IsA("Animal") will return 1.
Thanks, Stefan, we will look into this.