HealthShare

Hi all,

is it possible to omit the typical XML header line

<?xml version="1.0" encoding="ISO-8859-1" ?>

when writing an the contents of a EnsLib.EDI.XML.Document  using the above mentioned operation. I´ve already digged into the config value Format. It only states that:

C(e) : output an XML header line declaring character encoding e. If e is empty use the encoding defined by the Adapter. If e begins with ! force the output stream's encoding. Note that this will be applied automatically for File Operations configured with a non-UTF-8 Charset

Hi -

I'm wondering if there is any sort of experience with trying to leverage things like fingerprint readers into any identity management interface. I'm wondering if the "output" of some fingerprint scanner (or face scanner, or eyeball scanner for that matter) is something that HealthShare Patient Index might be able to use?

Hi,

While HL7 Errors ACKs come back in the soap response, the HL7v2 Error ACK message is not processed. 

I used the SOAP Wizard to construct my classes, but the generated code doesn't handle the HL7v2 ACK.
Does health Connect have a class that handles this?

Failing an official solution should I go ahead and make make my own classes based on EnsLib.HL7.Operation.TCPOperation, but wrapping it with the generated SOAP handling code.

How have others dealt with this?

Hi,

I want to know if anyone tried calling a CDS service from Healthshare/Ensemble. Will that be similar to any other API or is there anything different in constructing CDS Hooks and consuming the CDS Cards received in the response? 

Hello,

currently we have a problem in development with the character set of the response message.

We are transmitting an HL7 message with an operation based on the EnsLib.HL7.Operation.HTTPOperation class.
We have changed this as follows.

Set pMsgIn=$$$NULLOREF, tHttpRequest=##class(%Net.HttpRequest).%New(), tHttpRequest.WriteRawMode=1, tHttpRequest.ContentType="APPLICATION/HL7-V2; charset=UTF-8"

Unfortunately, the ContentType character set is not read correctly in the response.

Hi,
I am facing issue during LDAP lookup like whenever I used product group parameter in AD explorer to search data from application I am getting empty result. If I set product group parameter as null then based on distinguished name result is generated in application. So if anyone knows about how LDAP works and how parameters are set in AD explorer then please let me know.

Thanks in advance.

I am new to CCDs and I have a question for you all.

I need to take in a CCD from our EMR, filter out sensitive data then send it on as a CCD.

All feedback is appreciated.

Thanks