b.well SDK v0.15.0 Change Log

Production SDK Updates

b.well SDK version 0.15.0 includes the final round of fully integrated methods aligned with User Journey 4: User is able to retrieve Health Data.

Before referencing the method documentation, please take some time to read the Codings in Health Data Request Objects guide. It will be important to understand this concept as you begin to integrate the health data methods.

The following methods are now available:

Important Changes

Removed Mock Endpoints

The following mock endpoints were no longer in use and have been removed:

getMedication
getMedicationPricing
getMedicationList
getCommunications
getLabDetails

Known Issues and Future Enhancements

getEncounters

The getEncounters method does not currently support searching with code values as the code values needed are not returned from the getEncounterGroups method. This will be resolved quickly in an upcoming release.

getMedicationStatements

Searching using the getMedicationStatements is not currently supported with this release. Searching functionality will be enhanced in an upcoming release.
The following fields are included on MedicationStatement.

Field	Description
`id`	The id of the MedicationStatement
`status`	Status of the medication
`medication`	[CodeableConcept] representing the medication
`authoredOn`	Authored on date of the most recent medication request Known as prescribedDate in the mock SDK
`requester`	Requester of the most recent medication request Known as prescriber in the mock SDK
`effectiveDate`	Effective period of the medication statement Known as validityPeriod in the mock SDK
`dosageInstruction`	Details of how medication is/was taken or should be taken

Resolved Service Desk Tickets

SD-591 - reasonCode is now available in the SDK on Immunizations, but it is currently returning a null value. We are actively working to resolve this issue.

Test User with Health Data

The following test user JWT can be used for authenticating a user that has health data stored on the b.well FHIR server.

eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6ImJ3ZWxsLXRlc3QifQ.eyJndWlkIjoiYndlbGwtdGVzdF9QVlREcTRZMFg5bVl6UDBCbHBrNC9nPT0iLCJvdGlkIjpmYWxzZSwiZXhwIjoyNjk4MjM0MzcxLCJpYXQiOjE3MDY3MzQ5MzF9.CFND_f7azw7GV4cXnZ2JngzkUBqocoLZKmInPDO4_X31fUj0_p_ozAzLgtlnzp1jzNKchioxM-uA-tYP6iucsA

After authenticating, the health data methods can be used to retrieve data. In this case no specific demographics are needed for the user because we are not matching to an external data connection.

Note:

This user does not currently have labGroups or conditionGroups. We are actively working on populating this data.
It is a known issue that you may experience cases when the health data methods return null values where data exists in the FHIR server for the user. We are actively working to resolve this scenario.

❗️
When using this test user to test data retrieval, please DO NOT connect this user to any data connections.