Added in API level 34

Summary: Constants | Methods | Inherited Methods

HealthConnectManager

Kotlin |Java

public class HealthConnectManager
extends Object

java.lang.Object
↳	android.health.connect.HealthConnectManager

This class provides APIs to interact with the centralized HealthConnect storage maintained by the system.

HealthConnect is an offline, on-device storage that unifies data from multiple devices and apps into an ecosystem featuring.

APIs to insert data of various types into the system.

The basic unit of data in HealthConnect is represented as a Record object, which is the base class for all the other data types such as StepsRecord.

Summary

Constants
`String`	`ACTION_MANAGE_HEALTH_PERMISSIONS` Activity action: Launch UI to manage (e.g. grant/revoke) health permissions.
`String`	`ACTION_REQUEST_EXERCISE_ROUTE` Activity action: Launch UI to share the route associated with an exercise session.
`String`	`CATEGORY_HEALTH_PERMISSIONS` Used in conjunction with `Intent.ACTION_VIEW_PERMISSION_USAGE` to launch UI to show an app\u2019s health permission rationale/data policy.
`String`	`EXTRA_EXERCISE_ROUTE` An exercise route requested via `ACTION_REQUEST_EXERCISE_ROUTE`.
`String`	`EXTRA_SESSION_ID` A string ID of a session to be used with `ACTION_REQUEST_EXERCISE_ROUTE`.

Public methods
`<T> void`	`aggregate(AggregateRecordsRequest<T> request, Executor executor, OutcomeReceiver<AggregateRecordsResponse<T>, HealthConnectException> callback)` Get aggregations corresponding to `request`.
`<T> void`	`aggregateGroupByDuration(AggregateRecordsRequest<T> request, Duration duration, Executor executor, OutcomeReceiver<List<AggregateRecordsGroupedByDurationResponse<T>>, HealthConnectException> callback)` Get aggregations corresponding to `request`.
`<T> void`	`aggregateGroupByPeriod(AggregateRecordsRequest<T> request, Period period, Executor executor, OutcomeReceiver<List<AggregateRecordsGroupedByPeriodResponse<T>>, HealthConnectException> callback)` Get aggregations corresponding to `request`.
`void`	`createMedicalDataSource(CreateMedicalDataSourceRequest request, Executor executor, OutcomeReceiver<MedicalDataSource, HealthConnectException> callback)` Creates a `MedicalDataSource` in HealthConnect based on the `CreateMedicalDataSourceRequest` request values.
`void`	`deleteMedicalDataSourceWithData(String id, Executor executor, OutcomeReceiver<Void, HealthConnectException> callback)` Deletes a `MedicalDataSource` and all data linked to it.
`void`	`deleteMedicalResources(List<MedicalResourceId> ids, Executor executor, OutcomeReceiver<Void, HealthConnectException> callback)` Deletes a list of `MedicalResource`s by the provided list of `MedicalResourceId`s.
`void`	`deleteMedicalResources(DeleteMedicalResourcesRequest request, Executor executor, OutcomeReceiver<Void, HealthConnectException> callback)` Deletes `MedicalResource`s based on given filters in `DeleteMedicalResourcesRequest`.
`void`	`deleteRecords(List<RecordIdFilter> recordIds, Executor executor, OutcomeReceiver<Void, HealthConnectException> callback)` Deletes records based on `RecordIdFilter`.
`void`	`deleteRecords(Class<? extends Record> recordType, TimeRangeFilter timeRangeFilter, Executor executor, OutcomeReceiver<Void, HealthConnectException> callback)` Deletes records based on the `TimeRangeFilter`.
`void`	`getChangeLogToken(ChangeLogTokenRequest request, Executor executor, OutcomeReceiver<ChangeLogTokenResponse, HealthConnectException> callback)` Get token for {HealthConnectManager#getChangeLogs}.
`void`	`getChangeLogs(ChangeLogsRequest changeLogsRequest, Executor executor, OutcomeReceiver<ChangeLogsResponse, HealthConnectException> callback)` Get change logs post the time when `token` was generated.
`void`	`getMedicalDataSources(List<String> ids, Executor executor, OutcomeReceiver<List<MedicalDataSource>, HealthConnectException> callback)` Returns `MedicalDataSource`s for the provided list of IDs.
`void`	`getMedicalDataSources(GetMedicalDataSourcesRequest request, Executor executor, OutcomeReceiver<List<MedicalDataSource>, HealthConnectException> callback)` Returns the requested `MedicalDataSource`s.
`void`	`insertRecords(List<Record> records, Executor executor, OutcomeReceiver<InsertRecordsResponse, HealthConnectException> callback)` Inserts `records` into the HealthConnect database.
`void`	`readMedicalResources(List<MedicalResourceId> ids, Executor executor, OutcomeReceiver<List<MedicalResource>, HealthConnectException> callback)` Reads `MedicalResource`s based on a list of `MedicalResourceId`s.
`void`	`readMedicalResources(ReadMedicalResourcesRequest request, Executor executor, OutcomeReceiver<ReadMedicalResourcesResponse, HealthConnectException> callback)` Reads `MedicalResource`s based on `ReadMedicalResourcesInitialRequest` or `ReadMedicalResourcesPageRequest`.
`<T extends Record> void`	`readRecords(ReadRecordsRequest<T> request, Executor executor, OutcomeReceiver<ReadRecordsResponse<T>, HealthConnectException> callback)` API to read records based on `ReadRecordsRequestUsingFilters` or `ReadRecordsRequestUsingIds` Number of records returned by this API will depend based on below factors: When an app with read permission allowed calls the API from background then it will be able to read only its own inserted records and will not get records inserted by other apps.
`void`	`updateRecords(List<Record> records, Executor executor, OutcomeReceiver<Void, HealthConnectException> callback)` Updates `records` into the HealthConnect database.
`void`	`upsertMedicalResources(List<UpsertMedicalResourceRequest> requests, Executor executor, OutcomeReceiver<List<MedicalResource>, HealthConnectException> callback)` Inserts or updates a list of `MedicalResource`s into the HealthConnect database using `UpsertMedicalResourceRequest`.

Inherited methods

From class


        
          java.lang.Object

`Object`	`clone()` Creates and returns a copy of this object.
`boolean`	`equals(Object obj)` Indicates whether some other object is "equal to" this one.
`void`	`finalize()` Called by the garbage collector on an object when garbage collection determines that there are no more references to the object.
`final Class<?>`	`getClass()` Returns the runtime class of this `Object`.
`int`	`hashCode()` Returns a hash code value for the object.
`final void`	`notify()` Wakes up a single thread that is waiting on this object's monitor.
`final void`	`notifyAll()` Wakes up all threads that are waiting on this object's monitor.
`String`	`toString()` Returns a string representation of the object.
`final void`	`wait(long timeoutMillis, int nanos)` Causes the current thread to wait until it is awakened, typically by being notified or interrupted, or until a certain amount of real time has elapsed.
`final void`	`wait(long timeoutMillis)` Causes the current thread to wait until it is awakened, typically by being notified or interrupted, or until a certain amount of real time has elapsed.
`final void`	`wait()` Causes the current thread to wait until it is awakened, typically by being notified or interrupted.

Constants

ACTION_MANAGE_HEALTH_PERMISSIONS

Added in API level 34

public static final String ACTION_MANAGE_HEALTH_PERMISSIONS

Activity action: Launch UI to manage (e.g. grant/revoke) health permissions.

Shows a list of apps which request at least one permission of the Health permission group.

Input: Intent.EXTRA_PACKAGE_NAME string extra with the name of the app requesting the action. Optional: Adding package name extras launches a UI to manager (e.g. grant/revoke) for this app.

Constant Value: "android.health.connect.action.MANAGE_HEALTH_PERMISSIONS"

ACTION_REQUEST_EXERCISE_ROUTE

Added in API level 34

public static final String ACTION_REQUEST_EXERCISE_ROUTE

Activity action: Launch UI to share the route associated with an exercise session.

Input: caller must provide `String` extra EXTRA_SESSION_ID

Result will be delivered via [Activity.onActivityResult] with `ExerciseRoute` EXTRA_EXERCISE_ROUTE.

Constant Value: "android.health.connect.action.REQUEST_EXERCISE_ROUTE"

CATEGORY_HEALTH_PERMISSIONS

Added in API level 34

public static final String CATEGORY_HEALTH_PERMISSIONS

Used in conjunction with Intent.ACTION_VIEW_PERMISSION_USAGE to launch UI to show an app\u2019s health permission rationale/data policy.

Note: Used by apps to define an intent filter in conjunction with Intent.ACTION_VIEW_PERMISSION_USAGE that the HC UI can link out to.

Constant Value: "android.intent.category.HEALTH_PERMISSIONS"

EXTRA_EXERCISE_ROUTE

Added in API level 34

public static final String EXTRA_EXERCISE_ROUTE

An exercise route requested via ACTION_REQUEST_EXERCISE_ROUTE.

This is returned for a successful request to access a route associated with an exercise session.

Constant Value: "android.health.connect.extra.EXERCISE_ROUTE"

EXTRA_SESSION_ID

Added in API level 34

public static final String EXTRA_SESSION_ID

A string ID of a session to be used with ACTION_REQUEST_EXERCISE_ROUTE.

This is used to specify route of which exercise session we want to request.

Constant Value: "android.health.connect.extra.SESSION_ID"

Public methods

aggregate

Added in API level 34

public void aggregate (AggregateRecordsRequest<T> request, 
                Executor executor, 
                OutcomeReceiver<AggregateRecordsResponse<T>, HealthConnectException> callback)

Get aggregations corresponding to request.

Parameters
`request`	`AggregateRecordsRequest`: request for different aggregation. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`. Callback and listener events are dispatched through this `Executor`, providing an easy way to control which thread is used. To dispatch events through the main thread of your application, you can use `Context.getMainExecutor()`. Otherwise, provide an `Executor` that dispatches to an appropriate thread.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

See also:

AggregateRecordsResponse.get(AggregationType)

aggregateGroupByDuration

Added in API level 34

public void aggregateGroupByDuration (AggregateRecordsRequest<T> request, 
                Duration duration, 
                Executor executor, 
                OutcomeReceiver<List<AggregateRecordsGroupedByDurationResponse<T>>, HealthConnectException> callback)

Get aggregations corresponding to request. Use this API if results are to be grouped by concrete intervals of time, for example 5 Hrs, 10 Hrs etc.

Parameters
`request`	`AggregateRecordsRequest`: request for different aggregation. This value cannot be `null`.
`duration`	`Duration`: Duration on which to group by results This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`. Callback and listener events are dispatched through this `Executor`, providing an easy way to control which thread is used. To dispatch events through the main thread of your application, you can use `Context.getMainExecutor()`. Otherwise, provide an `Executor` that dispatches to an appropriate thread.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

See also:

aggregateGroupByPeriod(AggregateRecordsRequest, Period, Executor, OutcomeReceiver)

aggregateGroupByPeriod

Added in API level 34

public void aggregateGroupByPeriod (AggregateRecordsRequest<T> request, 
                Period period, 
                Executor executor, 
                OutcomeReceiver<List<AggregateRecordsGroupedByPeriodResponse<T>>, HealthConnectException> callback)

Get aggregations corresponding to request. Use this API if results are to be grouped by number of days. This API handles changes in ZoneOffset when computing the data on a per-day basis.

Parameters
`request`	`AggregateRecordsRequest`: Request for different aggregation. This value cannot be `null`.
`period`	`Period`: Period on which to group by results This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`. Callback and listener events are dispatched through this `Executor`, providing an easy way to control which thread is used. To dispatch events through the main thread of your application, you can use `Context.getMainExecutor()`. Otherwise, provide an `Executor` that dispatches to an appropriate thread.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

See also:

createMedicalDataSource

Added in Android Baklava

public void createMedicalDataSource (CreateMedicalDataSourceRequest request, 
                Executor executor, 
                OutcomeReceiver<MedicalDataSource, HealthConnectException> callback)

Creates a MedicalDataSource in HealthConnect based on the CreateMedicalDataSourceRequest request values.

A MedicalDataSource needs to be created before any MedicalResources for that source can be inserted.

Medical data is represented using the Fast Healthcare Interoperability Resources (FHIR) standard.

The display name must be unique per app, and CreateMedicalDataSourceRequest.Builder.setFhirVersion FHIR version} must be a version supported by Health Connect, as documented on the FhirVersion.
Requires HealthPermissions.WRITE_MEDICAL_DATA

Parameters
`request`	`CreateMedicalDataSourceRequest`: Creation request. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`IllegalArgumentException`	if `request` contains a FHIR base URI or display name exceeding the character limits, or an unsupported FHIR version.

deleteMedicalDataSourceWithData

Added in Android Baklava

public void deleteMedicalDataSourceWithData (String id, 
                Executor executor, 
                OutcomeReceiver<Void, HealthConnectException> callback)

Deletes a MedicalDataSource and all data linked to it.

If the provided data source id is either invalid, or does not exist, or owned by another apps, the caller will receive an exception with code HealthConnectException.ERROR_INVALID_ARGUMENT via callback.onError().

Regarding permissions:

Only apps with the system permission can delete data written by apps other than themselves.
Deletes are permitted in the foreground or background.

Requires HealthPermissions.WRITE_MEDICAL_DATA or android.health.connect.HealthPermissions.MANAGE_HEALTH_DATA_PERMISSION

Parameters
`id`	`String`: The id of the data source to delete. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

deleteMedicalResources

Added in Android Baklava

public void deleteMedicalResources (List<MedicalResourceId> ids, 
                Executor executor, 
                OutcomeReceiver<Void, HealthConnectException> callback)

Deletes a list of MedicalResources by the provided list of MedicalResourceIds.

If any ID in ids is invalid, the API will throw an IllegalArgumentException, and nothing will be deleted.
If any ID in ids does not exist, that ID will be ignored, while deletion on other IDs will be performed.

Regarding permissions:

Only apps with the system permission can delete data written by apps other than themselves.
Deletes are permitted in the foreground or background.

Requires HealthPermissions.WRITE_MEDICAL_DATA or android.health.connect.HealthPermissions.MANAGE_HEALTH_DATA_PERMISSION

Parameters
`ids`	`List`: The ids to delete. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

deleteMedicalResources

Added in Android Baklava

public void deleteMedicalResources (DeleteMedicalResourcesRequest request, 
                Executor executor, 
                OutcomeReceiver<Void, HealthConnectException> callback)

Deletes MedicalResources based on given filters in DeleteMedicalResourcesRequest.

Regarding permissions:

Only apps with the system permission can delete data written by apps other than themselves.
Deletes are permitted in the foreground or background.

Requires HealthPermissions.WRITE_MEDICAL_DATA or android.health.connect.HealthPermissions.MANAGE_HEALTH_DATA_PERMISSION

Parameters
`request`	`DeleteMedicalResourcesRequest`: The delete request. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`IllegalArgumentException`	if `request` contains unsupported medical resource types or invalid `MedicalDataSource` IDs.

deleteRecords

Added in API level 34

public void deleteRecords (List<RecordIdFilter> recordIds, 
                Executor executor, 
                OutcomeReceiver<Void, HealthConnectException> callback)

Deletes records based on RecordIdFilter.

Deletions are performed in a transaction i.e. either all will be deleted or none

Parameters
`recordIds`	`List`: recordIds on which to perform delete operation. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`IllegalArgumentException`	if `recordIds is empty`

deleteRecords

Added in API level 34

public void deleteRecords (Class<? extends Record> recordType, 
                TimeRangeFilter timeRangeFilter, 
                Executor executor, 
                OutcomeReceiver<Void, HealthConnectException> callback)

Deletes records based on the TimeRangeFilter.

Deletions are performed in a transaction i.e. either all will be deleted or none

Parameters
`recordType`	`Class`: recordType to perform delete operation on. This value cannot be `null`.
`timeRangeFilter`	`TimeRangeFilter`: time filter based on which to delete the records. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

getChangeLogToken

Added in API level 34

public void getChangeLogToken (ChangeLogTokenRequest request, 
                Executor executor, 
                OutcomeReceiver<ChangeLogTokenResponse, HealthConnectException> callback)

Get token for {HealthConnectManager#getChangeLogs}. Changelogs requested corresponding to this token will be post the time this token was generated by the system all items that match the given filters.

Tokens from this request are to be passed to {HealthConnectManager#getChangeLogs}

Parameters
`request`	`ChangeLogTokenRequest`: A request to get changelog token This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

getChangeLogs

Added in API level 34

public void getChangeLogs (ChangeLogsRequest changeLogsRequest, 
                Executor executor, 
                OutcomeReceiver<ChangeLogsResponse, HealthConnectException> callback)

Get change logs post the time when token was generated.

Parameters
`changeLogsRequest`	`ChangeLogsRequest`: The token from `HealthConnectManager.getChangeLogToken`. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`. Callback and listener events are dispatched through this `Executor`, providing an easy way to control which thread is used. To dispatch events through the main thread of your application, you can use `Context.getMainExecutor()`. Otherwise, provide an `Executor` that dispatches to an appropriate thread.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

See also:

getChangeLogToken(ChangeLogTokenRequest, Executor, OutcomeReceiver)

getMedicalDataSources

Added in Android Baklava

public void getMedicalDataSources (List<String> ids, 
                Executor executor, 
                OutcomeReceiver<List<MedicalDataSource>, HealthConnectException> callback)

Returns MedicalDataSources for the provided list of IDs.

The number and order of medical data sources returned by this API is not guaranteed. The number will depend on the factors below:

If an empty list of ids is provided, an empty list will be returned.
If any ID in ids is invalid, the caller will receive an exception with code HealthConnectException.ERROR_INVALID_ARGUMENT via callback.onError().
If any ID in ids does not exist, no data source will be returned for that ID.
Callers will only get data sources they are permitted to get. See below.

There is no specific read permission for getting data sources. Instead, permission to read data sources is based on whether the caller has permission to read the data currently linked to that data source. Being permitted to get data sources is dependent on the following logic, in priority order, earlier statements take precedence.

A caller with the system permission can get any data source in the foreground or background.
A caller without any read or write permissions for health data will not be able to get any medical data sources and receive an exception with code HealthConnectException.ERROR_SECURITY via callback.onError(), even for data sources the caller has created.
Callers can get data sources they have created, whether this method is called in the foreground or background. Note this only applies if the caller has at least one read or write permission for health data.
For any given data source, a caller can get that data source in the foreground if the caller has permission to read any of the data linked to that data source. For clarity, the does not allow it to get an empty data source.
For any given data source, a caller can get that data source in the background if it has both permission to read any of the data linked to that data source, and HealthPermissions.READ_HEALTH_DATA_IN_BACKGROUND.
In all other cases the caller is not permitted to get the given data source and it will not be returned.

Parameters
`ids`	`List`: Identifiers for data sources to get. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

getMedicalDataSources

Added in Android Baklava

public void getMedicalDataSources (GetMedicalDataSourcesRequest request, 
                Executor executor, 
                OutcomeReceiver<List<MedicalDataSource>, HealthConnectException> callback)

Returns the requested MedicalDataSources.

Number of data sources returned by this API will depend based on below factors:

If an empty names is passed, all permitted data sources from all apps will be returned. See below.
If any package name in the of package names is invalid, the API will throw an IllegalArgumentException.
If a non-empty names is specified in the request, then only the permitted data sources created by those packages will be returned. See below.

There is no specific read permission for getting data sources. Instead permission to read data sources is based on whether the caller has permission to read the data currently linked to that data source. Being permitted to get data sources is dependent on the following logic, in priority order, earlier statements take precedence.

A caller with the system permission can get any data source in the foreground or background.
A caller without any read or write permissions for health data will not be able to get any medical data sources and receive an exception with code HealthConnectException.ERROR_SECURITY via callback.onError(), even for data sources the caller has created.
Callers can get data sources they have created, whether this method is called in the foreground or background. Note this only applies if the caller has at least one read or write permission for health data.
For any given data source, a caller can get that data source in the foreground if the caller has permission to read any of the data linked to that data source. For clarity, the does not allow it to get an empty data source.
For any given data source, a caller can get that data source in the background if it has both permission to read any of the data linked to that data source, and HealthPermissions.READ_HEALTH_DATA_IN_BACKGROUND.
In all other cases the caller is not permitted to get the given data source and it will not be returned.

Parameters
`request`	`GetMedicalDataSourcesRequest`: the request for which data sources to return. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`IllegalArgumentException`	if `request` contains invalid package names.

insertRecords

Added in API level 34

public void insertRecords (List<Record> records, 
                Executor executor, 
                OutcomeReceiver<InsertRecordsResponse, HealthConnectException> callback)

Inserts records into the HealthConnect database. The records returned in InsertRecordsResponse contains the unique IDs of the input records. The values are in same order as records. In case of an error or a permission failure the HealthConnect service, OutcomeReceiver.onError will be invoked with a HealthConnectException.

Parameters
`records`	`List`: list of records to be inserted. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`. Callback and listener events are dispatched through this `Executor`, providing an easy way to control which thread is used. To dispatch events through the main thread of your application, you can use `Context.getMainExecutor()`. Otherwise, provide an `Executor` that dispatches to an appropriate thread.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`RuntimeException`	for internal errors

readMedicalResources

Added in Android Baklava

public void readMedicalResources (List<MedicalResourceId> ids, 
                Executor executor, 
                OutcomeReceiver<List<MedicalResource>, HealthConnectException> callback)

Reads MedicalResources based on a list of MedicalResourceIds.

The number and order of medical resources returned by this API is not guaranteed. The number will depend on the factors below:

If an empty list of ids is provided, an empty list will be returned.
If the size of ids is more than 5000, the API will throw an IllegalArgumentException.
If any ID in ids is invalid, the API will throw an IllegalArgumentException.
If any ID in ids does not exist, no medical resource will be returned for that ID.
Callers will only get medical resources they are permitted to get. See below.

Being permitted to read medical resources is dependent on the following logic, in priority order, earlier statements take precedence.

A caller with the system permission can get any medical resources in the foreground or background.
A caller without any read or write permissions for health data will not be able to get any medical resources and receive an exception with code HealthConnectException.ERROR_SECURITY via callback.onError(), even for medical resources the caller has created.
Callers can get medical resources they have created, whether this method is called in the foreground or background. Note this only applies if the caller has at least one read or write permission for health data.
For any given medical resource, a caller can get that medical resource in the foreground if the caller has the corresponding read permission, or in the background if it also has HealthPermissions.READ_HEALTH_DATA_IN_BACKGROUND.
In all other cases the caller is not permitted to get the given medical resource and it will not be returned.

Each returned MedicalResource has passed the Health Connect FHIR validation checks at write time, but is not guaranteed to meet all requirements of the Fast Healthcare Interoperability Resources (FHIR) spec. If required, clients should perform their own checks on the data.

Parameters
`ids`	`List`: Identifiers on which to perform read operation. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`IllegalArgumentException`	if the size of `ids` is more than 5000 or if any id is invalid.

readMedicalResources

Added in Android Baklava

public void readMedicalResources (ReadMedicalResourcesRequest request, 
                Executor executor, 
                OutcomeReceiver<ReadMedicalResourcesResponse, HealthConnectException> callback)

Reads MedicalResources based on ReadMedicalResourcesInitialRequest or ReadMedicalResourcesPageRequest.

Being permitted to read medical resources is dependent on the following logic, in priority order, earlier statements take precedence.

A caller with the system permission can get any medical resources in the foreground or background.
A caller without any read or write permissions for health data will not be able to get any medical resources and receive an exception with code HealthConnectException.ERROR_SECURITY via callback.onError(), even for medical resources the caller has created.
Callers can get medical resources they have created, whether this method is called in the foreground or background. Note this only applies if the caller has at least one read or write permission for health data.
For any given medical resource, a caller can get that medical resource in the foreground if the caller has the corresponding read permission, or in the background if it also has HealthPermissions.READ_HEALTH_DATA_IN_BACKGROUND.
In all other cases the caller is not permitted to get the given medical resource and it will not be returned.

Parameters
`request`	`ReadMedicalResourcesRequest`: The read request `ReadMedicalResourcesInitialRequest` or `ReadMedicalResourcesPageRequest`. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`IllegalArgumentException`	if `request` has set page size to be less than 1 or more than 5000; or if contains unsupported medical resource type or invalid `MedicalDataSource` IDs when using `ReadMedicalResourcesInitialRequest`.

readRecords

Added in API level 34

public void readRecords (ReadRecordsRequest<T> request, 
                Executor executor, 
                OutcomeReceiver<ReadRecordsResponse<T>, HealthConnectException> callback)

API to read records based on ReadRecordsRequestUsingFilters or ReadRecordsRequestUsingIds

Number of records returned by this API will depend based on below factors:

When an app with read permission allowed calls the API from background then it will be able to read only its own inserted records and will not get records inserted by other apps. This may be less than the total records present for the record type.

When an app with read permission allowed calls the API from foreground then it will be able to read all records for the record type.

App with only write permission but no read permission allowed will be able to read only its own inserted records both when in foreground or background.

An app without both read and write permissions will not be able to read any record and the API will throw Security Exception.

Parameters
`request`	`ReadRecordsRequest`: Read request based on `ReadRecordsRequestUsingFilters` or `ReadRecordsRequestUsingIds` This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`IllegalArgumentException`	if request page size set is more than 5000 in `ReadRecordsRequestUsingFilters`
`SecurityException`	if app without read or write permission tries to read.

updateRecords

Added in API level 34

public void updateRecords (List<Record> records, 
                Executor executor, 
                OutcomeReceiver<Void, HealthConnectException> callback)

Updates records into the HealthConnect database. In case of an error or a permission failure the HealthConnect service, OutcomeReceiver.onError will be invoked with a HealthConnectException.

In case the input record to be updated does not exist in the database or the caller is not the owner of the record then HealthConnectException.ERROR_INVALID_ARGUMENT will be thrown.

Parameters
`records`	`List`: list of records to be updated. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`. Callback and listener events are dispatched through this `Executor`, providing an easy way to control which thread is used. To dispatch events through the main thread of your application, you can use `Context.getMainExecutor()`. Otherwise, provide an `Executor` that dispatches to an appropriate thread.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`IllegalArgumentException`	if at least one of the records is missing both ClientRecordID and UUID.

upsertMedicalResources

Added in Android Baklava

public void upsertMedicalResources (List<UpsertMedicalResourceRequest> requests, 
                Executor executor, 
                OutcomeReceiver<List<MedicalResource>, HealthConnectException> callback)

Inserts or updates a list of MedicalResources into the HealthConnect database using UpsertMedicalResourceRequest.

For each UpsertMedicalResourceRequest, one MedicalResource will be returned. The returned list of MedicalResources will be in the same order as the requests.

Medical data is represented using the Fast Healthcare Interoperability Resources (FHIR) standard. The FHIR resource provided in UpsertMedicalResourceRequest.getData() is expected to be valid FHIR in JSON representation for the specified UpsertMedicalResourceRequest.getFhirVersion() according to the FHIR spec. Structural validation checks such as resource structure, field types and presence of required fields are performed, but these checks may not cover all FHIR spec requirements and may change in future versions.

Each UpsertMedicalResourceRequest also has to meet the following requirements.

The FHIR resource contains an "id" and "resourceType" field.
The FHIR resource type is in our accepted list of resource types. See FhirResource for the accepted types.
The FHIR resource does not contain any "contained" resources.
The resource can be mapped to one of the READ_MEDICAL_DATA_ HealthPermissions categories.
The UpsertMedicalResourceRequest.getDataSourceId() is valid.
The UpsertMedicalResourceRequest.getFhirVersion() matches the FhirVersion of the MedicalDataSource.

If any request contains invalid MedicalDataSource IDs, the API will throw an IllegalArgumentException, and none of the requests will be upserted into the HealthConnect database.

If any request is deemed invalid for any other reasons, the caller will receive an exception with code HealthConnectException.ERROR_INVALID_ARGUMENT via callback.onError(), and none of the requests will be upserted into the HealthConnect database.

If data for any UpsertMedicalResourceRequest fails to be upserted, then no data from any requests will be upserted into the database.

The uniqueness of each request is calculated comparing the combination of data source id, FHIR resource type and FHIR resource ID extracted from the provided data. If the above combination does not match with an existing one in Health Connect, then a new MedicalResource is inserted, otherwise the existing one is updated.
Requires HealthPermissions.WRITE_MEDICAL_DATA

Parameters
`requests`	`List`: List of upsert requests. This value cannot be `null`.
`executor`	`Executor`: Executor on which to invoke the callback. This value cannot be `null`. Callback and listener events are dispatched through this `Executor`, providing an easy way to control which thread is used. To dispatch events through the main thread of your application, you can use `Context.getMainExecutor()`. Otherwise, provide an `Executor` that dispatches to an appropriate thread.
`callback`	`OutcomeReceiver`: Callback to receive result of performing this operation. This value cannot be `null`.

Throws
`IllegalArgumentException`	if any `requests` contains invalid `MedicalDataSource` IDs.