Hi Guys,

Migrated our system from Ensemble 2014 to 2018 and but for some reason my tasks keep getting the attached error not sure why?

Thanks

We are receiving the report in text format and it has special characters like ', - like that in the text. Source system is using the UTF8 encoding format hence the text is showing as ' � ' . Is there a way to convert the utf8 to actual character in the DTL.

Thank you,

Hi guys,

we converted from Ensemble 2014 to 2018 and now getting the attached error which looks like Manage Method don't exist anymore, has it been replaced by a new one?

Thanks

I am creating a new HL7 DTL item. I put the from as HL7 and the to as XML, hence, those Ens classes were loaded into the new DTL. However, on the map screen, both the left and the right column only show 'source' and 'target', and no other fields. I pictured that when I included these classes, both columns would pull the corresponding 'schema' to show all the to/from fields, but, they did not. Is that right?

We are using a DTL transformation to take HL7 and transform into custom XML. But the nodes in the resulting XML are appearing out of sequence - and therefore failing validation against the schema.

The XSD schema for the XML looks fine when imported into Ensemble: root node in the XSD looks like this:

And shows in Ensemble like this:

Hi ,

I receive below JSON from a https outbound operation

{
"Link": "www.sample.com",
"Practice": [
{
"Node": "Record1"
}
]
}

I am able to read Link as - JSON.%Get("Link")

How can I read Node value ?

Everytime I try to send a POST FHIR bundle I'm getting the following response: 404 Not Found. I'm not really sure why, although it works fine with a GET!

This is an example:

Response:

It might be something related to request path but not really sure.

And this is the HTTP service I'm using

Is it possible to generate INFO level logging events from within a routing rule?

TRACE level events and debugging are easy enough, but we have a case where we have a rule where we want to log messages that are not routed for further processing in the event log as INFO events - in production tracing will be turned off, so TRACE level events won't be visible.

We are doing healthcare interface development.

Developers have Ensemble installed locally on their laptops - code will be developed locally then deployed to integration, test/UAT and ultimately production servers in due course.

One of the other applications we are developing around happens to utilise an Iris desktop client to a remote Iris server. We want to have the application available on the developers laptops alongside the local Ensemble instance.

Hi group,

I am trying to take the InterSystems HL7 Interface Specialist certificate test.

So is this an open book test? is there any Lab involved with vm? I did the search but I am not able to find such information.

I am trying to find out more information before I actually take the test.

Thank you

We have classes in a Production environment that are causing us some issues - example attached.

When we export them from the production environment the XML contains a snippet like the following:

<UDLText name="T">
<Content><![CDATA[
//Property any As list Of %XML.String(XMLNAME = "any", XMLPROJECTION = "ANY") [ SqlFieldName = _any ];

]]></Content>
</UDLText>

When imported and compiled into an Ensemble instance this class works as expected.

Hi Guys,

I'm using the following to display JSON content in an areatextbox, but I would like to change a value in my JSON before displaying it in my areabox?

Hello,
Please, we would need your help 🙂:

In a development environment, we have added quite a few presentation contexts to the DICOM configurations (the associations). We would need to find a way to export them from this environment to make it easier for us to import them in PRO (and avoid doing it by hand one by one).

I need a DTL to handle this.

Any ideas appreciated.

For all Prosthetics orders:
when ORC-1(Order Control) is "NW" (New Order), need to update OBR-18(Placer Field 1) based on PV1-2 (Patient Class) value.
assumption is that the selection logic is that all prosthetics orders with OBR-18 field is always blank.
Description :
If PV1-2 is I, insert I in OBR-18
If PV1-2 is O, insert O in OBR-18
If PV1-2 is E, insert O in OBR-18
If PV1-2 is P, insert O in OBR-18
If PV1-2 is R, insert O in OBR-18
If PV1-2 is B, insert O in OBR-18