Hi everyone.

Is there a sensible approach to having a lookup table in Namespace A, and then accessing this from Namespaces B, C, D (etc)?

I'm trying to avoid creating a Global mapping of the lookup table global (^Ens.LookupTable) as I fear that it would then link all other lookups in that global and lead to some unexpected behaviour, but would be open to trying something in this realm if it's the best option.

0 4
0 65

Hi Team,

I am trying to use the inbuilt class: EnsLib.HL7.Service.FileService to pass through an HL7 ADT message as a part of an HL7 to FHIR transformation. We have a client requirement, where we are receiving an NTE segment as a part of the ADT message. However, the inbuilt schema structure of the HL7 ADT message does not support an NTE segment out of the box. We are getting an error message stating "Unrecognized segment".

Please advise, how do we bypass this error?

Thanks

Santosh

0 2
0 30