b.well SDK v0.16.0 Change Log

The following items and changes are included in this release.

The connection state diagram regarding data connection status with getMemberConnections can be found under the Diagrams section in Guides.

Change: performer: string has been updated to performer: [String].
Reason for Change: This modification allows for the representation of multiple performers for a procedure, acknowledging scenarios where more than one performer may be involved.

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:
    - id
    - dispenseInterval
    - expectedSupplyDuration
    - initialFill
    - numberOfRepeatsAllowed
    - performer
    - validityPeriod
    - quantity
- reasonCode
- source
These elements have been reintroduced to Medication Statements in the SDK.

Phone number validation when calling 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: 5138965698
updateProfile 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.