Stream: implementers
Topic: STU3 release for hapi-fhir
Mritunjay Dubey (Mar 20 2017 at 11:53):
Hey @Grahame Grieve / @James Agnew , Hey we were trying to upgrade from DSTU2-STU3. We are using the java hapi implementation. We were using last released version of hapi 2.2 from maven. Looks like the code is still not stable to validate the converted encounter-bundles. The renames are not reflected in code yet. E.g:- In STU3 Encounter resource the Encounter.patient is renamed to Encounter.subject but Encounter.javawas still talking about encounter.getPatient().
We thought of upgrading to 2.4-SNAPSHOT and we got few other errors. To proceed with our upgrade we wanted to know when we can get a stable build? Can you please let us know about your roadmap?
Brian Postlethwaite (Mar 20 2017 at 12:03):
The 3.0 spec hasn't officially released yet (its the next few days) so might want to wait a bit.
James Agnew (Mar 20 2017 at 12:30):
HAPI FHIR version 2.3 is a stable build and has the Encounter.subject change reflected in it.
Mritunjay Dubey (Mar 20 2017 at 12:35):
hey, @James Agnew , thanks for the reply. is it published to maven ? We checked maven-repo the latest is 2.2 on Dec 2016.
James Agnew (Mar 20 2017 at 12:41):
http://search.maven.org/#search%7Cga%7C1%7Chapi-fhir is showing the new release
Mritunjay Dubey (Mar 20 2017 at 13:00):
Hey thanks. We will check it, we just checked https://mvnrepository.com/artifact/ca.uhn.hapi.fhir/hapi-fhir-base, and found it is not there.
Jim Steel (Mar 21 2017 at 04:27):
Should the FHIR version still be 1.8.0?
Grahame Grieve (Mar 21 2017 at 04:30):
no
Grahame Grieve (Mar 21 2017 at 04:30):
it should be 3.0.0. James isn't completely up to date yet
Jim Steel (Mar 21 2017 at 04:37):
So will that be a quickfire 2.4?
Mritunjay Dubey (Mar 28 2017 at 06:04):
Hey @James Agnew/ @Grahame Grieve We tried upgrading hapi-fhir to 2.3. Now we are facing issues related to DiagnosticOrder. It is not there in v2.3, in release 2.2 there was a new resource DiagnosticRequest event that is not there in 2.3.
Mritunjay Dubey (Mar 28 2017 at 06:06):
We are not sure which resource is actually replacing diagnostic order.
Grahame Grieve (Mar 28 2017 at 06:13):
ProcedureRequest
Mritunjay Dubey (Mar 28 2017 at 06:18):
Thanks! just found while comparing the references. One clarification, the DiagnosticRequest was introduced newly and has been removed now. Correct me if I am worng.
Grahame Grieve (Mar 28 2017 at 07:42):
yes it was transient
Eric Haas (Mar 28 2017 at 20:14):
more precisely DiagnosticOrder --> renamed to DiagnosticRequest ---> merged with ProcedureRequest
David Cai (Apr 13 2017 at 00:08):
Can someone please point me to the mappings from DiagnosticRequest to ProcedureRequest, if there is one?
Eric Haas (Apr 13 2017 at 02:40):
Everything in DiagnosticRequest maps to ProcedureRequest elements 1:1. The big change was from DiagnosticOrder in DSTU2 to DiagnosticRequest in STU3 Ballot. I looked for my notes but can't find them. I'll try to find some time to outline a mapping.
David Cai (Apr 13 2017 at 03:11):
@Eric Haas I thought there is no DiagnosticRequest in STU3?
Eric Haas (Apr 13 2017 at 14:40):
DiagnosticRequest existed briefly in the pre-release before we merged it with ProcedureRequest. So.. you are right - it went from DiagnosticOrder to ProcedureRequest.
David Cai (Apr 19 2017 at 05:24):
Thanks for the clarification.
Last updated: Apr 12 2022 at 19:14 UTC
