#HealthShare

17 Followers · 1.4K Posts

InterSystems HealthShare is a healthcare informatics platform for hospitals, integrated delivery networks (IDNs) and regional and national health information exchanges (HIE). HealthShare includes health information exchange, data aggregation, workflow, text analysis, and analytics technology.

Learn more

Edit
Question Nupur kumar · Aug 23, 2016

For message bank implementation, in Ensemble->Enterprise Portal->Message Bank Viewer the Search based on basic or extended criteria is not working, for instance if i have to find a message with some known session Id, & i add this in my extended criteria, the search shows no results , whereas that message exists in the portal.

Please suggest why is it  not working.

Thanks

0
0 33
Edit
Question Raghu Kodumuri · Sep 9, 2016

Hello,

We have exposed a REST service for external vendors to call and post the data. The content type is 
application/x-www-form-urlencoded. Service reads the data from Form variable (strData).
 
This service works as long as data in the Form variable is less than 32KB anything more than that 
size CSP gateway is sending the truncated request to superserver.
 
Is there any configuration that I am missing? or is there any size restriction on 
Form variable or there is an issue.
0
0 0
Edit
Question Scott Beeson · Oct 11, 2016

I've worked with our Healthshare instance for almost 2 years now and I still can't answer so many basic questions like "How many searches were performed today".  

Two of the reasons (and there are many) are simply the size and complexity of the ATNA table.

To avoid this issue, I'm considering a custom Ensemble/Cache class that would log each ATNA event type to a separate and simpler reporting table.

I wanted to see if anyone had any experience or advice on this front.

0
0 18
Edit
Question Scott Beeson · Mar 13, 2017

Okay, maybe not like I'm 5, but can anyone explain it like I'm a Javascript/SQL developer?

From one of our contracted developers:

ISC built this custom XUA Creator class and the MHC Customized Role to pass messages around from instance/server to instance/server (BUS to REG, etc.
The user’s roles have either HSGroup_WrittenAuthorization or HSGroup_InformedOptOut, plus one of the 4 %HS_ roles.
Based on the user’s roles, it turns the HS roles text into a number, by adding 1, 2, 4, 8, 16, 32 to the value.  
When the message is received by the XUA Processor, it turns the MHC role code number back into
0
0 120
Edit
Question Scott Beeson · Mar 21, 2017
cvc-complex-type.2.4.a: Invalid content was found starting with element 'sdtc:raceCode'. One of '{"urn:hl7-org:v3":ethnicGroupCode, "urn:hl7-org:v3":guardian, "urn:hl7-org:v3":birthplace, "urn:hl7-org:v3":languageCommunication}' is expected.

I'm getting the error above while trying to use the NIST validation tool on a CCD created by Healthshare.

Here is the full <patient> element:

      <patient>
        <name use="L">
          <family>TESTPATIENT</family>
          <given>ZZKIDJULY</given>
        </name>
        <administrativeGenderCode code="F" codeSystem="2.16.840.1.113883.5.1"
0
0 0
Edit
Question Amit Kumar · May 15, 2017

Our requirement is to fetch the SDA to get the some clinical data from aggregated SDA. Will this soap service work for our requirement. "HS.Gateway.Access.WebServicesClient"?

Please review the code and let me know.  Also while I am running testing the code in sand box getting this error "<ZSOAP>zInvokeClient+203^%SOAP.WebClient.1"

Set tSearchRequest = ##class(HS.Message.SearchAndFetchRequest).%New()
Set tGatewaySearch = ##class(HS.Gateway.Access.WebServicesClient).%New()
#DIM tResponse AS HS.Message.SearchAndFetchResponse
Set tSearchRequest.MPIID = tMPIID 
#DIM tSDA As HS.SDA3.Container
#DIM

0
0 15
Edit
Question Jenna Makin · Jun 1, 2016

I have been experimenting with the concept of transforming HL7 input into a CDA document and am running into a little problem.  Let me describe my setup

First I have a HealthShare production with three simple components.

1.  I have a Enslib.HL7.FileService which looks in a specified directory for files containing HL7 messages to process.  That service picks up the message and passes it to a custom business operation which is setup to transform it to CDA.

2.

2
0 29