-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support for FHIR R4B #110
Comments
Hi, @apollo13 thanks a lot for this issue! https://hl7.org/fhir/R4B/r4b-explanation.html But obviously, we will need more discussion, maybe we could await a bit more to see if more updates coming. Also, we need to think fhir.resources version policy for implementing R4B. like should it be 7.x.x or 6.5.x etc. We will work on it soon. |
Seems like R4B is pretty stable. My use case is considering 5.0 In any event, happy to help on this effort. Not quite ready to create a PR. Is the CONTRIBUTING.rst guide up to date? I wasn't sure of the steps necessary to create a new FHIR release. I'm a bit confused how directories are managed i.e. I had to manually move R4 code to a legacy directory, manually deploy examples to script/static, etc.
The
The
|
@nazrulworld Hi. Checking in to see if there was any interest on collaborating on a R4B and eventually a 5.0.0 version. Thanks very much |
++ Very interested in the R4B. The new Medication Definition Module has some resources I'd like to use (specifically ClinicalUseDefinition) |
I will look into it if I can manage some good times. |
Hello @nazrulworld, nice to see support for R4B! Thanks for the awesome library! |
R5 released 🥳 |
Description
It would be great if this package supported FHIR Release R4B https://hl7.org/fhir/R4B/version.info .
I guess this would mean moving the current implementation into an R4 subfolder and then generate it against R4B. I tried doing that locally to submit a PR but more or less failed (even when just regenerating the current version I had loads of diffs due to black and what not). Are there any documentations on how to prepare a PR for a new version?
The text was updated successfully, but these errors were encountered: