Android Native Libraries Released - September 28, 2022
Android Full Library v1.14.4
Android Aggregator Library v1.14.4
Android LifeScan OneTouch Library v1.14.4
Android Native Changes
General
Bump
compileSdkVersion
andtargetSdkVersion
to Android 13 (33) for libraries and applicationsBump gradle to 7.5.1
Bump Android Gradle plugin to 7.2.2
Bluetooth
Bond with OS before connecting to peripherals
Fix updating time on Omron devices
VitalSnap
Remove
androidx.appCompat
dependencyFix crash when Vitalsnap fails to acquire camera on resume
ValidicOCRActivity
class is nowfinal
iOS Native Libraries Released - September 28, 2022
iOS Full Library v1.14.1
iOS Aggregator Library v1.14.1
iOS LifeScan OneTouch Library v1.14.1
iOS Native Changes
Common
Module libraries built with Xcode 14 and iOS 16 SDK and tested against an iPhone running iOS 16
The Validic iOS frameworks now support iOS 15 and up
Core
Disabled bitcode, which was deprecated by Apple in Xcode 14
HealthKit
Added support for workout types added in iOS 13 - 16
React Native Wrapper Libraries Released
React Native Aggregator Library v1.4.0
React Native Wrapper Changes
General
Bundled Android native SDK upgraded to v1.14.3
Bundled iOS native SDK upgraded to v1.14.0
Minimum supported version of react-native bumped to
0.62.3
Android Native Libraries Released - September 8, 2022
Android Full Library v1.14.3
Android Aggregator Library v1.14.3
Android LifeScan OneTouch Library v1.14.3
Android Native Changes
Bluetooth
Fixed issue where Passive Bluetooth would not automatically restart
See previous changes from Android v1.14.2 release
Cordova Wrappers Released - September 8, 2022
Cordova Full Library v1.14.0
Cordova Aggregator Library v1.14.0
Cordova Changes
General
Bundled native SDKs upgraded to Android v1.14.3 and iOS v1.14.0
Bluetooth
Removed
ACCESS_BACKGROUND_LOCATION
from being automatically added to the consumer manifestBluetoothPeripheral
properties returned fromgetPeripheral
are nowcamelCase
instead ofPascalCase
OCR
OCRPeripheral
properties returned fromgetPeripheral
are nowcamelCase
instead ofPascalCase
Samsung Health
Switched to using static ID for Android SHealth notification channel name to avoid multiple channels showing up in notification settings
Xamarin Android Wrapper Libraries Released
Xamarin Android Full Library v1.14.3
Xamarin Android Aggregator Library v1.14.3
Xamarin Android Wrapper Changes
General
Bundled Android native SDK upgraded to v1.14.3
Core
User credentials (validicUserID, organizationID, accessToken) must now be non-empty strings. If an empty string (or nil) is used for any of those properties,
Session.startSessionWithUser
will throw an exception. You must initialize the SDK with a valid user session in order for the following functions to work: Apple Health, Google Fit and Samsung Health reads; passive Bluetooth reads.Implemented user validation against the Validic API. User credentials are checked when
Session.startSessionWithUser
is called, and any user session started with invalid or unknown credentials will trigger a call toSessionConnectionListener.onSessionEnded(User, unsentRecords)
.Any 401 Unauthorized response from the Validic API will automatically trigger a call to
SessionConnectionListener.onSessionEnded(User, unsentRecords)
.Added a default user session. Accessible via
User.DEFAULT_USER
, this user session can be initialized to perform foreground Bluetooth and VitalSnap reads only while the app is offline. This feature is intended to be used with the Full SDK package when valid Validic user session credentials are unavailable/unknown.If your app always has access to a valid set of user credentials and always initializes the SDK with a valid set of user credentials, then no changes are needed.
The recommended SDK implementation is to always provision users on the Validic server then initialize the SDK with valid session credentials for the user. Therefore, use of the default user is not common and its use should be limited to instances where you are unable to retrieve valid session credentials and you need to perform a foreground operation (Bluetooth pair, Bluetooth foreground read, or VitalSnap read).
Some operations will not function with the default user. SDK operations that require a server-side user will not function while the SDK is initialized with the default user. You must initialize the SDK with a valid user session in order for the following functions to work: Apple Health, Google Fit, and Samsung Health reads and passive Bluetooth reads.
If you need assistance adjusting your implementation of the SDK to account for these changes, please reach out to the Validic support team at support@validic.com.
Bluetooth
Added generic support for pulse oximeters that follow the Bluetooth standard for Spot Check measurements.
Added support for ChoiceMMed pulse oximeter MD300CI218 (peripheral 45).
Added
InvalidUserException
as thecause
for aValidicBluetoothException
when attempting to execute an operation with anull
user or a user with credentials that cannot be used when performing an API request.Switched to using static ID for Android Bluetooth notification channel name to avoid multiple channels showing up in notification settings
Samsung Health
Switched to using static ID for Android SHealth notification channel name to avoid multiple channels showing up in notification settings
Android native public api update for Historical Fetch with
jni-signature
that includesjava.util.Calendar
params.
(Release to pre-production on 9/7/2022 & 9/21/2022. Release to production on 10/4/2022)
New Event Configuration: Combined Events
Combined Event configuration is now available within Admin - this allows the chaining together multiple events using AND or OR comparators and an evaluation window. Actions can be added to Combined Events to execute when the Event rule is offended.
Example Combined Event: Systolic Blood Pressure is less than 90 mmHg OR Systolic Blood Pressure is greater than 120 mmHg
Reading limit (threshold) type events are only supported
Admin
A new “Combined Event” button is available within Events/Actions configuration in a program.
Individual event conditions can be added to a Combined Event group and an AND (green) or OR (blue) comparator can be established to evaluate the conditions within. A look-back window is also established to determine an evaluation period for the conditions to occur.
The Combined Event can be saved, and an associated Action can be added to make the Combined Event/Action available within the program.
Clinician Dashboard and Enrollment
Enrollment and the Clinician Dashboard have been updated to display Combined Events/Actions
Individual condition reading limit (threshold) values can be edited during enrollment and from the Clinician Dashboard, the same as existing Reading Limit Events.
Please see below for more information on Combined Events: https://help.validic.com/space/VCS/3355705346/Configuring+a+Combined+Event
Additional Notes:
System Alert action type is not currently supported for Combined Events.
Once the Event/Action is live (user enrolled in program with the rule), the Combined Event cannot be edited.
Combined Events will be evaluated and will trigger immediately after the submission of an offending reading.
Additional New features and updates
Removed the ability to edit a live Event from Admin.
Removed the ability to edit the “method (type)” for a live Action from Admin.
Moved the ENROLL IN NEW PROGRAM button and implemented tabbing arrows on program tabs in Clinician Dashboard to prevent issues with cut off tabs and inaccessible enrollment button.
Resolved defects
Confirmation message (are you sure?) now shows when deleting an Event from Admin. Snack-bar message now shows to confirm delete of Event and Action.
Resolved issue preventing edits of certain Action criteria from saving in Admin.
Updated in basket pool recipient selection language in enrollment.
Updated participant search label in program view.
Resolved issue affecting the triggering of weight change events configured with a “less than” comparator.
EHR integrated customers
Resolved issue preventing the enrollment of prior users with newly added demographic information. Null demographic information (including DOB) from prior enrollments will now be added during enrollment, allowing the enrollment to continue.