handleNotifications was called in SDK version 1.1.0. This has been corrected in version 1.1.1.createConsent was called in SDK version 1.1.0. This has been corrected in version 1.1.1.
b.well SDK version 1.1.0 includes new features, a breaking change, and operational improvements that enhance the SDK's functionality in non-Production environments.
handleNotification, has been introduced. This allows SDK clients to inform us when a silent push notification is opened. This feature aims to improve user engagement tracking and the effectiveness of push notification campaigns.suspend fun handleNotification(data: String) : OperationOutcomedeleteConnection, has been introduced. This endpoint will allow a user to delete a connection, deleting the associated token and the user's data specific to the connection. This endpoint is not fully functional with this release. Currently it will set the connection status to DELETED, but will not delete the data. Full end to end functionality will be introduced in a following release.suspend fun deleteConnection(connectionId: String): OperationOutcomeA new enum, DELETED has been added to ConnectionStatus
enum ConnectionStatus {
CONNECTED,
DISCONNECTED,
ERROR,
EXPIRED,
DELETED
}Configuration Management Updates
initialize) of the SDK will now only be respected in non-Production environments. This allows for more flexible development and testing configurations without affecting live production setups.getTasks was corrected, which will allow the full list of a user's tasks to be retrieved using paging. Here is an example builder function:private fun getTasks() {
val taskRequest = TasksRequest.Builder()
.enrichContent(true)
.status(TaskStatus.READY)
.smartSort(true)
.page(0)
.pageSize(50)
.build()Enhanced Retry Policy Configuration
BwellConfig.Builder() includes an update to the retry policy configuration.New implementation example
.retryPolicy(
RetryPolicy.Builder()
.maxRetries(5)
.retryInterval(500) // in milliseconds
.build()
)Previous implementation example, for reference
.retryPolicy(RetryPolicy(maxRetries = 5, retryInterval = 500))The following changes are included in this release.
The following changes are included in this release.
lastUpdated date.
lastUpdated can be found here.getMemberConnections now returns a connection status of EXPIRED
disconnectConnection and one that has been disconnected due to an expired token.activity.detail.statusactivity.detail.scheduled[x]
scheduledTimingscheduledPeriodscheduledStringgetEncounters properly filters by groupCode.Import Statement Changes
import com.bwell.common.models.domain.healthdata.observation.Observationimport com.bwell.common.models.domain.healthdata.common.observation.Observationimport com.bwell.healthdata.lab.requests.LabGroupsRequestimport com.bwell.healthdata.healthsummary.requests.procedure.LabGroupsRequestSchema Changes
Schema changes have been made that have resulted in type name changes. These were included in a previous post for review prior to release.
| Description |
|---|
| Field 'AllergyIntoleranceResource.reaction' changed type from '[AllergyIntoleranceReaction]' to '[Reaction]' |
| Field 'CarePlanResource.activity' changed type from '[CarePlanActivity]' to '[Activity]' |
| Field 'ConditionResource.recorder' changed type from 'ConditionRecorder' to 'Recorder' |
| Field 'EncounterResource.participant' changed type from '[EncounterParticipant]' to '[Participant]' |
| Field 'ImmunizationResource.encounter' changed type from 'ImmunizationEncounter' to 'EncounterResource' |
| Field 'ImmunizationResource.reaction' changed type from '[ImmunizationReaction]' to '[Reaction]' |
| Field 'ImmunizationResource.protocolApplied' changed type from '[ImmunizationProtocolApplied]' to '[ProtocolApplied]' |
| Field 'ImmunizationResource.performer' changed type from '[ImmunizationPerformer]' to '[Performer]' |
| Field 'MedicationStatementResource.requester' changed type from 'PerformerActor' to 'Actor' |
| Field 'ObservationResource.value' changed type from 'ObservationValue' to 'Value' |
| Field 'ObservationResource.referenceRange' changed type from '[ObservationReferenceRange]' to '[ReferenceRange]' |
| Field 'ObservationResource.component' changed type from '[ObservationComponent]' to '[Component]' |
| Field 'ObservationResource.encounter' changed type from 'Encounter' to 'EncounterResource' |
| Field 'ObservationResource.performer' changed type from '[ObservationPerformer]' to '[Performer]' |
| Field 'ProcedureResource.performer' changed type from '[ProcedurePerformer]' to '[Performer]' |
| Field 'ProcedureResource.encounter' changed type from 'ProcedureEncounter' to 'EncounterResource' |
| Field 'LabGroup.value' changed type from 'ObservationValue' to 'Value' |
| Field 'LabGroup.referenceRange' changed type from '[ObservationReferenceRange]' to '[ReferenceRange]' |
| Field 'LabGroup.component' changed type from '[ObservationComponent]' to '[Component]' |
| Field 'VitalSignGroup.value' changed type from 'ObservationValue' to 'Value' |
| Field 'VitalSignGroup.referenceRange' changed type from '[ObservationReferenceRange]' to '[ReferenceRange]' |
| Field 'VitalSignGroup.component' changed type from '[ObservationComponent]' to '[Component]' |
The following items and changes are included in this release.
meta.lastUpdated no longer returns as nullrecordedDate is now returned by getAllergyIntoleranceGroups to support the client applications "Sort by Date View".lastSynced and statusUpdated are now nullable fields on getMemberConnections
lastSynced or statusUpdated returns as nullThe following items and changes are included in this release.
meta.tag (activityClass) no longer returns null on getTasks.We're continually improving the SDK to align with FHIR standards. Here's a summary of the recent changes:
id on Identifier.
system should now be used to identify Activities/Tasks.id to system.
distanceInMiles and parking.resourceType.id.id.id and extension.resourceType.__typename from models.PatientConditionRecorder class.organizationName, practitionerName, and patientName have been renamed to name.Photo to Attachment.Note The fields above were removed to adhere to FHIR standards. However, if the removal of any fields listed above cause issues with SDK integration, please let us know.
The b.well Sample App has been updated to include implementation for push notifications!
HomeFragment.kt: Implementation of registerDeviceBWellFirebaseMessagingService.kt: Implementation of token management and notification handling.The following items and changes are included in this release.
createConnectioncreateConnection Method: The createConnection method now returns BWellResult<Connection> instead of OperationOutcome, enhancing the method's output with more detailed information.
UNRECOGNIZED to ConnectionCategory and ConnectionType.
UNKNOWN to avoid confusion with valid cases in some FHIR enums.UNRECOGNIZED is intended as a fallback and should rarely be invoked.createConnection has been resolved as part of the modifications to createConnection mentioned above.The following items and changes are included in this release.
getMemberConnections can be found under the Diagrams section in Guides.performer: string has been updated to performer: [String].Change: period: Period has been revised to date: Datetime.
Reason for Change: Simplifying the data model, this change reflects the current requirement to capture only a single datetime for an encounter. The need for a start and end time is currently not essential for our use case.
Change: participant: [EncounterParticipant] is now participant: String.
Reason for Change: This update replaces the reference to Practitioner resources with a simple string detailing the Practitioner's name and credentials.
New Additions:
dispenseRequest
dispenseRequest is comprised of data class MedicationDispenseRequest and includes:
iddispenseIntervalexpectedSupplyDuration initialFillnumberOfRepeatsAllowedperformervalidityPeriodquantityreasonCodesourceThese elements have been reintroduced to Medication Statements in the SDK.
updateProfile has been relaxed. The phone number is no longer required to be a valid US phone number. The phone number is only required to be 10 digits in length. Example: 5138965698updateProfile will now successfully update the user's profile information if empty string values are passed for a given attribute.searchProviders and searchConnections paging parameters are now 0-based.These update does not require the new version of the SDK and is currently deployed to the client-sandbox environment.