Stream: implementers
Topic: Code reuse across multiple FHIR versions
Łukasz Dywicki (Mar 22 2018 at 12:59):
Some time, not that far ago, I been working on processing logic. I have used Property type to traverse resources looking certain types (codes and such). Since I was working with STU3 all my code is now working perfectly fine with this version of spec, however logic I have implemented is rather universal as it is based on swapping some String values.
I wrote a message to HAPI mailing list, however this topic seems to be more accurate to FHIR build process itself: https://groups.google.com/forum/#!topic/hapi-fhir/XD3zlZNSaNg
Now, even if my "business" logic working with any FHIR resource and its fairly portable the "processing" logic, which rely on metadata is not. Are there any reasons why there is no lowest common denominator for Property type as there is support for that in other places?Code reuse across multiple FHIR versions
Grahame Grieve (Mar 22 2018 at 13:05):
i use .elementmodel for version independent processing.
Grahame Grieve (Mar 22 2018 at 13:07):
looks like it wouldn't be too much work to rationalise to a single version of Property - but would that achieve much?
Last updated: Apr 12 2022 at 19:14 UTC
