Stream: hapi
Topic: HAPI FHIR 4.0.0
James Agnew (Aug 14 2019 at 18:21):
August 14, 2019 - HAPI FHIR 4.0.0 (Igloo) Released
The next release of HAPI has now been uploaded to the Maven repos and GitHub's releases section.
This release features a number of significant performance improvements, and has some notable changes:
- A new consent framework called ConsentInterceptor that can be used to apply local consent directives and policies, and potentially filter or mask data has been added.
- Initial support for draft FHIR R5 resources has been added.
- Support for GraphQL and the _filter search parameter has been added.
- The ability to perform cascading deletes has been added.
As always, see the for a full list of changes: http://hapifhir.io/changes-report.html
You can also watch the release webinar: https://youtu.be/0breejA_xe4
Thanks to everyone who contributed to this release!
John Grimes (Aug 15 2019 at 05:50):
@James Agnew Looks like something untoward may have happened to the API docs: http://hapifhir.io/apidocs-dstu3/index.html
James Agnew (Aug 15 2019 at 13:23):
HI @John Grimes - Ah nuts, thanks for pointing this out. We're now importing the structures from the org.hl7.fhir.core projects via Maven dependency instead of physically copying the classes into HAPI's repo. This is great for maintainability but it had the unintended consequence of breaking the javadocs on the website.
We're going to be rebuilding the website during this release cycle so I don't think it's worth fixing on the soon-to-be-replaced site, expect to see this fixed in a few weeks.
David Hay (Aug 19 2019 at 19:58):
Only a true geek could write this: "A BOM POM has been added to the HAPI FHIR distribution..."...
Patrick Werner (Aug 20 2019 at 10:01):
after Upgrading a HAPI Server Project with custom providers and some validation support to 4.0.0 i get:
ca.uhn.fhir.rest.server.exceptions.InternalErrorException: Failed to call access method: java.lang.NoSuchMethodError: org.hl7.fhir.r4.utils.FHIRPathEngine.evaluateToBoolean(Ljava/lang/Object;Lorg/hl7/fhir/r4/model/Base;Lorg/hl7/fhir/r4/model/Base;Lorg/hl7/fhir/r4/model/ExpressionNode;)Z ... Caused by: java.lang.NoSuchMethodError: org.hl7.fhir.r4.utils.FHIRPathEngine.evaluateToBoolean(Ljava/lang/Object;Lorg/hl7/fhir/r4/model/Base;Lorg/hl7/fhir/r4/model/Base;Lorg/hl7/fhir/r4/model/ExpressionNode;)Z at org.hl7.fhir.r4.validation.InstanceValidator.checkInvariant(InstanceValidator.java:3974)
Is this a bug or has ValidationSupport changed in R4?
Whole Stacktrace:
https://pastebin.com/YBZJaDZa
James Agnew (Aug 20 2019 at 12:19):
Any chance you have multiple versions of a HAPI FHIR JAR on your classpath? That would be the likeliest cause of that kind of issue.
Patrick Werner (Aug 20 2019 at 21:01):
had the validation module still in 3.8.0, thanks again James!
James Agnew (Aug 20 2019 at 21:07):
I've always wondered if there was a "standard solution" for detecting this kind of thing. I've done the same thing many times..
James Agnew (Aug 21 2019 at 14:12):
got curious... looks like the consensus online is to use JBoss Tattletale: https://tattletale.jboss.org/
I'm gonna investigate this sometime
Patrick Werner (Aug 21 2019 at 15:34):
didn't know it, but it sounds great.
Last updated: Apr 12 2022 at 19:14 UTC