July 7, 2016 - HAPI FHIR 1.6 Released - The next release of HAPI has now been uploaded to the Maven repos and GitHub's releases section.
This release brings a number of bugfixes and also quite a few enhancements. As always, the changelog has the full list of changes in this version. Among the enhancements in this release are:
- Significant enhancements to FhirConetxt startup performance (especially on Android)
- Support for STU3 terminology services in the JPA module, including support for importing SNOMED CT and LOINC
- Update of the STU3 resources and validator to the latest snapshot
- Plenty of bug fixes
As always, thanks to everyone who contributed to this release, either though pull requests, bug reports, suggestions, and helping us test new features.
Also, a few quick community notes:
On DSTU3 naming: FMG has decided to rename the upcoming FHIR DSTU3 (draft standard
for trial use) release to STU3 (standard for trial use). In order to avoid breaking
existing software, we will NOT be renaming the hapi-fhir-structures-dstu3 module
of HAPI. We will be updating documentation on the site to reflect the new name wherever it won't be
confusing, but be aware that this is a potential source of confusion.
On the HAPI FHIR website: Regular visitors to our site will probably already have noticed that we recently moved the site to a new URL ( http://hapifhir.io ). This was done mostly to help make HAPI's URL a bit easier to remember.
On the future: For the next release, we are planning on moving away from the
javax.json (JSR 353) library in favour of using Google GSON. JSR 353 seemed like
a good choice when we started HAPI, but it has basically been abandoned and no longer seems like
a good choice (especially given the headaches it causes on Android). This hopefully means that
the next release will be able to do away with the "special" Android shade-jar releases and all of
the Gradle file gymnastics that are required in order to use them.
As always, we welcome new contributions and contributors! Please feel free to get in touch if you are interested in getting involved with HAPI but don't know where to start.