Craig,
This is the code we use when creating a hapi context. Note that we
typically lock in a structures version via the CanonicalModelClasFactory
System.setProperty("ca.uhn.hl7v2.model.varies.default_obx2_type",
"ST");
System.setProperty("ca.uhn.hl7v2.model.varies.invalid_obx2_ty
Christian,
Thanks for the info on PID3 lists when using the PreParser, I was wondering
what your thoughts on doing the following to get around the PID3 list.
I use the getFields() of preParser to get more PID 3 repeats than we could
possibly have. In our case, 250 was determined to be quite adequ
As part of fuzz testing it has been identified that strange combinations of
MSH-9 can cause some quite unexpected behaviour.
In this example a message defined as ADT^M02 was routed as an MFN^M02 due
to routing only checking MSH-9-2 and ended up being processed as a
V24.GenericMessage.
So my quest
Sounds like you should have a look at
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-create-api-app
What you then need to provide is HAPI wrapped in some REST-like API
Den 19. jul. 2017 20.44 skrev "David Lancaster via Hl7api-devel" <
hl7api-devel@lists.sourceforge.net>:
> Hello -
Hello -
Newcomer to this listserv, so this is my first post - please be gentle with me!
Has anyone embedded/encapsulated the HAPI V.2 and/or HAPI FHIR parsers within
Microsoft Azure Logic Apps? I'd like to know if Azure (.NET framework) has
any kind of issue calling a Java-based API.
Thanks
Thanks for the reply Mike.
Yes in this case my goal is to have generic-ish code that can handle multiple
v2 versions. So I’m “up-converting” to v26 using the
CanonicalModelClassFactory. So far this works well except in cases where items
have been withdrawn in v26 which fail validation.
I tried
6 matches
Mail list logo
