You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In S4S we're building some demo apps that connect to DSTU2 clinical data servers and an STU3 financial server from CMS. I tried loading two versions of the library at different paths, but
seems to clobber the namespaces. Has this come up before? I can think about ways to improve the module loading, but wanted to start with a quick sanity check.
The text was updated successfully, but these errors were encountered:
The problem has come up already, yes, but not a good solution. IIRC this was the only way we found so that imports from within client-py as well as from a higher level in Python 2 and Python 3 would work. If you have a solution you should push it!
Could you support the different versions as packages e.g. fhirclient.models.DSTU2, fhirclient.models.STU3 etc. Then allow instantiating FHIRClient to use the version you want.
In S4S we're building some demo apps that connect to DSTU2 clinical data servers and an STU3 financial server from CMS. I tried loading two versions of the library at different paths, but
https://github.com/smart-on-fhir/client-py/blob/master/fhirclient/__init__.py#L5
seems to clobber the namespaces. Has this come up before? I can think about ways to improve the module loading, but wanted to start with a quick sanity check.
The text was updated successfully, but these errors were encountered: