Important Points

1. Our open source FHIR SDK is NOT required to talk to the b.well platform. Our platform complies with the FHIR standard so you can use any FHIR client, build your own or just make REST API calls.
2. We’ve been building and using our open source FHIR SDK for four years now, so we use it in all our data operations internally. We found this SDK reduced much of the complexity in using FHIR for high volume resilient transfers, for mapping non-FHIR data to FHIR and for using FHIR for analytics.
3. Clients can choose to use it to accelerate their efforts but as mentioned above this is not required to exchange data with b.well. You should evaluate and decide what works best for you.
4. The open-source SDK is governed by the Apache 2 license (also included in each repo in github). We don’t assume any liability beyond the open-source license on the open-source code.
5. The code for open source is completely visible to you so you can feel free to decide whether to use each open-source SDK package after reviewing its code. You can also submit Pull Requests for enhancements per the open-source guidelines.
6. Our open-source SDK is built as Python packages, available on PyPi.org and you can choose to use only the packages you’re interested in using.
7. Regarding our AutoMapper, like any mapping tool, you should expect a training and onboarding period.
8. When using our Python SDK, we recommend pinning the versions, so you don’t get newer versions without being able to do your testing first. This way you are in control of upgrades.