I’m creating this post to discuss about this project.
This week I have gone through the FHIR Specification and HAPI FHIR library to do the HAPI FHIR library upgrade.
According to https://onfhir.hl7.org/2017/01/20/fhir-product-roadmap/, a new version of FHIR named R4 is coming during this year. HAPU FHIR library doing developments to support R4 structures according to http://hapifhir.io/apidocs-r4/index.html. R4 version of the FHIR specification schedule to release on October 2018. During my upgrade is it required to upgrade to R4 structures?
@eunice18 for the moment, it’s fine to upgrade the hapi fhir library to latest version. I think we need to wait official release of R4 to upgrade FHIR module to use those resources.
Also please create JIRA for issues for each task that you are working and contributing.
When I’m working on swagger code generator improvement. I noticed library provide two options. One option allow to generate client side SDK and other one provide functionality to generate server side stub. I think we should support both options. @harsha89 what do you think about this?
@eunice18 we should support both.
From my perspective, our REST API documentation would benefit greatly from two things:
A static build option. We shouldn’t make people wait for documentation of the core api to be generated every time it is consulted and we could use this feature to host an up to date version at api.openmrs.org.
A way to insert manual documentation amidst the auto-generated documentation. Ideally, we could write helpful text (introductory text, examples, etc) as markdown and have it woven into the final product. Auto-generated documentation is nice to have, but it can’t tell you the purpose of various resources or provide helpful tips on best practices, etc. I’m not sure if it’s better to maintain this text separately, but my gut feeling is that it would be best maintained within the code (e.g., markdown in javadocs).
@burke This project mainly aims to automatically generate the client side SDK out of our swagger definition using swagger codegen library. Which allow end users to generate a client in their preferred language without writing a client from the scratch. I believe something we can embed into our REST APIs as well. @eunice18 please add more details on this.
Hello @burke @harsha89
We are embedding https://github.com/swagger-api/swagger-codegen feature to the module. We can plug same implementation to REST Web Services Module. In real world, user will embed the generated SDK from preferred language without worrying about the API invocations. Swagger code generation library generates client side stubs for invoke the APIs.