Stream: hapi
Topic: release plan / roadmap
Michael Lawley (Jun 09 2016 at 10:10):
Hi James, just wondering if there's a release plan / roadmap for HAPI?
James Agnew (Jun 09 2016 at 13:42):
Hi Michael, at this point we don't have a formally documented release plan or roadmap unfortunately. Because of the dependency we have on the FHIR specification itself, we haven't wanted to do much long term forecasting because changes to the specification have often required significant changes to the library and that has made it hard to predict where we'll need to focus our efforts.
It does seem like the rate of change to the core parts of FHIR is slowing down, and that rate will probably come down even more one STU3 is final, so it'll probably be time to look at a more predictable release schedule in the coming year.
Jim Steel (Jun 13 2016 at 04:03):
In the shorter term, is there an anticipated date/timeframe for 1.6?
James Agnew (Jun 13 2016 at 05:28):
definitely within 1-2 weeks at this point... we've reached the "basically just documentation left to complete" state for 1.6
Jim Steel (Jun 13 2016 at 05:32):
Cool
Mohammad Jafari (Jun 22 2016 at 19:57):
Thanks @James Agnew I'm wondering if there is a way I can update DSTU3 resources to the latest from the FHIR build to be able to test the latest versions of a resource (in our case Consent). We are trying to test some features as the resource evolves and I need to make sure I have a server that can accept such resources.
Is the content of hapi-fhir-structures-dstu3/src/main/java/org/hl7/fhir/dstu3/model machine-generated?
James Agnew (Jun 22 2016 at 20:02):
Hi Mohammad- The contents are machine generated (they come from the FHIR spec build itself). I sync them from time to time.. If you pull the latest 1.6 sources from our Git repo, you'll get a snapshot of the STU3 resources from about 2 weeks ago. I will probably sync them again within the next few days since we're about to release HAPI 1.6.
Grahame Grieve (Jun 22 2016 at 20:08):
Mohammad wants an even more recent version....
Grahame Grieve (Jun 22 2016 at 20:09):
like the one I'm going to commit in a few hours!
Mohammad Jafari (Jun 22 2016 at 20:14):
@Grahame Grieve is right :) I guess my question is whether the sync-ing is something that the developers could do themselves when needed.
James Agnew (Jun 22 2016 at 20:57):
oh definitely. I don't mind to do another sync tomorrow if you want, but there's also nothing wrong with you copying the files from the spec build into HAPI and compiling it locally. I don't make any changes to them as a part of the sync.
Mohammad Jafari (Jun 22 2016 at 21:49):
Thanks @James Agnew
David Hay (Jun 23 2016 at 03:42):
Hi @James Agnew - Is it possible to do the same thing and generate the CLI server?
James Agnew (Jun 23 2016 at 12:05):
Also possible, although you'd need to build the CLI by hand. E.g.
- Replace (for example)
Patient.javain the dstu3 project with a copy from the spec build - Run
mvn installon the entire hapi-fhir project - Grab
hapi-fhir-cli/hapi-fhir-cli-app/target/hapi-fhir-cli.jarand use it
Last updated: Apr 12 2022 at 19:14 UTC
