In HAPI 2.0, under ca\uhn\hl7v2\model\v231\group .The java class files are incorrectly named.
One of the Java file is named as
ADR_A19_EVNPIDPD1NK1PV1PV2DB1OBXAL1DG1DRGPR1ROLGT1IN1IN2IN3ACCUB1UB2.java
This is actually by design. Group names were not an official part of the specification until 2.4, so HAPI compensated by creating these fake group names instead.
At this point, we could retroactively add them (which was accidentally done in one release long ago) but this would likely break lots of existing code.
I am in favour of releasing an alternate version of the 2.3.1 structure JARs which uses the group names. That's proably a good way of accomodating anyone who needs the "real" group names while not breaking anyone's existing code.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you James for looking into this issue. It's very kind of you to plan to release an alternate version of 2.3.1 structure jars.
However, our company came up with a workaround. We will not be needing the separate jar with correct group names anymore.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the 2.1 release there is a alternate structure jar for 2.3.1 but the content is the same as the normal 2.3.1 jar. Is this intended? At least it's somewhat confusing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is actually by design. Group names were not an official part of the specification until 2.4, so HAPI compensated by creating these fake group names instead.
At this point, we could retroactively add them (which was accidentally done in one release long ago) but this would likely break lots of existing code.
I am in favour of releasing an alternate version of the 2.3.1 structure JARs which uses the group names. That's proably a good way of accomodating anyone who needs the "real" group names while not breaking anyone's existing code.
Thank you James for looking into this issue. It's very kind of you to plan to release an alternate version of 2.3.1 structure jars.
However, our company came up with a workaround. We will not be needing the separate jar with correct group names anymore.
Thanks
In the 2.1 release there is a alternate structure jar for 2.3.1 but the content is the same as the normal 2.3.1 jar. Is this intended? At least it's somewhat confusing.