|
2 | 2 |
|
3 | 3 | The CommonHealth Client SDK provides an interface that allows applications to access health data stored in CommonHealth. |
4 | 4 |
|
5 | | -The CommonHealth Client SDK is in closed beta. If you would like to participate in our beta program, please reach out to info [at] commonhealth.org. |
| 5 | +The CommonHealth Client SDK is in closed beta. If you would like to participate in our beta program, please reach out to developers [at] commonhealth.org. |
6 | 6 |
|
7 | 7 | While we consider the SDK to be relatively stable, this is pre-release software, so the interfaces are subject to change based on evolving requirements and developer feedback. We're currently investigating ways to make it easier to remove configuration dependencies, so if you find anything particularly burdensome or confusing, please let us know by either emailing us or opening a Github issue. |
8 | 8 |
|
@@ -327,7 +327,7 @@ Upon receiving the NEW_DATA_AVAILABLE notification, you can invoke a method on t |
327 | 327 |
|
328 | 328 | ## Registering with CommonHealth |
329 | 329 |
|
330 | | -Registering with CommonHealth is not required to begin testing integrations with CommonHealth. However, if you have a client application that you would like to use in production environments, you'll need to register the application with CommonHealth. This is similar to registering an OAuth client, where you would specify information such as required scope, authorization redirect URI, etc. Please reach out to info [at] commonhealth.org for more information. |
| 330 | +Registering with CommonHealth is not required to begin testing integrations with CommonHealth. However, if you have a client application that you would like to use in production environments, you'll need to register the application with CommonHealth. This is similar to registering an OAuth client, where you would specify information such as required scope, authorization redirect URI, etc. Please reach out to developers [at] commonhealth.org for more information. |
331 | 331 |
|
332 | 332 | ## Upgrading from v0.4.4 to v0.4.8 |
333 | 333 | `v0.4.8` introduced a number of large changes and enhancements to the API: |
@@ -369,4 +369,4 @@ No functional changes to the API were introduced in `v0.4.0`. |
369 | 369 | - `CommonHealthStoreConfiguration.Builder` class has been removed. Applications should create instances of this class directly. |
370 | 370 | - Removed the `CommonHealthStoreProvider` interface and dependency on the custom Application implementation to adopt the interface. Implementers should instead initialize the `CommonHealthStore` singleton via the `CommonHealthStore.initialize` static method. The `CommonHealthStore.getSharedInstance` static method is provided for accessing the `CommonHealthStore` singleton. |
371 | 371 | - Removed the requirement for applications to include SDK specific `service`, `broadcastreciever`, and `activity` components in the application manifest. These have been moved to the SDK manifest file and will be merged in during the build process. We've added a requirement that applications define the `interappAuthRedirectScheme`, `interappAuthRedirectHost`, and `interappAuthRedirectPath` manifest placeholders in the app's `build.gradle` file. |
372 | | - - Replaced the `CommonHealthStore` `executeDataQuery` method with `readSampleQuery`. |
| 372 | + - Replaced the `CommonHealthStore` `executeDataQuery` method with `readSampleQuery`. |
0 commit comments